Clarify support policy for Microsoft Fabric MCP Server

[JoshGer]

CSS is receiving support tickets for Fabric MCP server issues. Updated feedback and support section for clarity.

What does this PR do?

[Provide a clear, concise description of the changes]

[Any additional context, screenshots, or information that helps reviewers]

GitHub issue number?

[Link to the GitHub issue this PR addresses]

Pre-merge Checklist

• Required for All PRs
  • Read contribution guidelines
  • PR title clearly describes the change
  • Commit history is clean with descriptive messages (cleanup guide)
  • Added comprehensive tests for new/modified functionality
  • Updated servers/Azure.Mcp.Server/CHANGELOG.md and/or servers/Fabric.Mcp.Server/CHANGELOG.md for product changes (features, bug fixes, UI/UX, updated dependencies)
• For MCP tool changes:
  • One tool per PR: This PR adds or modifies only one MCP tool for faster review cycles
  • Updated servers/Azure.Mcp.Server/README.md and/or servers/Fabric.Mcp.Server/README.md documentation
  • Validate README.md changes using script at eng/scripts/Process-PackageReadMe.ps1. See Package README
  • Updated command list in /servers/Azure.Mcp.Server/docs/azmcp-commands.md and/or /docs/fabric-commands.md
  • Run .\eng\scripts\Update-AzCommandsMetadata.ps1 to update tool metadata in azmcp-commands.md (required for CI)
  • For new or modified tool descriptions, ran ToolDescriptionEvaluator and obtained a score of 0.4 or more and a top 3 ranking for all related test prompts
  • For tools with new names, including new tools or renamed tools, update consolidated-tools.json
  • For new tools associated with Azure services or publicly available tools/APIs/products, add URL to documentation in the PR description
• Extra steps for Azure MCP Server tool changes:
  • Updated test prompts in /servers/Azure.Mcp.Server/docs/e2eTestPrompts.md
  • 👉 For Community (non-Microsoft team member) PRs:
    • Security review: Reviewed code for security vulnerabilities, malicious code, or suspicious activities before running tests (crypto mining, spam, data exfiltration, etc.)
    • Manual tests run: added comment /azp run mcp - pullrequest - live to run Live Test Pipeline

[github-actions]

Thank you for your contribution @JoshGer! We will review the pull request and get back to you soon.

[Copilot]

Pull request overview

Updates the Fabric MCP Server README to clarify the project’s support expectations and direct users to the formal support policy, aiming to reduce support ticket misrouting.

Changes:

• Added a new “Feedback and Support” bullet in servers/Fabric.Mcp.Server/README.md pointing readers to the Support Policy section in SUPPORT.md.

[Copilot]

This bullet says support is only provided through community channels and GitHub, but SUPPORT.md’s “Microsoft Support Policy” section also describes “Enterprise Support (Limited)” for customers with support agreements. Please reword to match the policy (e.g., community support is primary for the MCP server implementation, with limited enterprise support for general Fabric/platform topics), or adjust SUPPORT.md if the intent is truly community-only.

Suggested change

- The Microsoft Fabric MCP Server is an **open-source project in Public Preview**. Support is only provided through community channels and GitHub repositories. Review the [Microsoft Support Policy](https://github.com/microsoft/mcp/blob/main/servers/Fabric.Mcp.Server/SUPPORT.md#microsoft-support-policy) section of this project for more details.

- The Microsoft Fabric MCP Server is an **open-source project in Public Preview**. Support for this server implementation is primarily provided through community channels and GitHub repositories. Customers with qualifying Microsoft enterprise support agreements may have access to limited support for broader Microsoft Fabric and platform scenarios; review the [Microsoft Support Policy](https://github.com/microsoft/mcp/blob/main/servers/Fabric.Mcp.Server/SUPPORT.md#microsoft-support-policy) section of this project for more details.