Prepare 2.0.0 release

[vcolin7]

What does this PR do?

Updated changelogs and version ahead of release.

GitHub issue number?

N/A

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
  • Created a changelog entry if the change falls among the following: new feature, bug fix, UI/UX update, breaking change, or updated dependencies. Follow the changelog entry guide
• 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 running the script ./eng/scripts/Process-PackageReadMe.ps1. See Package README
  • 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 renamed tools, follow the Tool Rename Checklist and tag the PR with the breaking-change label
  • 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 command list in servers/Azure.Mcp.Server/docs/azmcp-commands.md
  • Ran ./eng/scripts/Update-AzCommandsMetadata.ps1 to update tool metadata in azmcp-commands.md (required for CI)
  • 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

[Copilot]

Pull request overview

Prepares the Azure MCP Server for the 2.0.0 release by updating the server package version and adding consolidated 2.0.0 release notes to the relevant changelogs.

Changes:

• Bumped Azure.Mcp.Server package version to 2.0.0.
• Added a new 2.0.0 release section to the server changelog, including high-level highlights and a “since 1.0.0” summary.
• Added a new 2.0.0 release section to the VS Code changelog with installation/documentation links.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
servers/Azure.Mcp.Server/vscode/CHANGELOG.md	Adds top-level 2.0.0 release notes for the VS Code-facing changelog.
servers/Azure.Mcp.Server/src/Azure.Mcp.Server.csproj	Updates the server/package version to 2.0.0.
servers/Azure.Mcp.Server/CHANGELOG.md	Adds top-level 2.0.0 release notes and a consolidated “since 1.0.0” section.

[jongio]

Two items not yet flagged: (1) the Azure AI Foundry branding joshfree caught in the main CHANGELOG also appears in the VS Code CHANGELOG (lines 19, 21) and needs the same fix, (2) the VS Code CHANGELOG is missing the breaking changes summary that the main CHANGELOG includes - users upgrading from 1.x won't have a consolidated view of what changed. Also a nit: over 40 beta iterations in both changelogs - there are exactly 40 (beta.1 through beta.40).

[jongio]

Nit: the breaking changes section mixes regular hyphens and en-dash characters as separators between the Removed and use descriptions. Cosmos DB and Key Vault lines use the hyphen, while the other 9 lines use the en-dash character. Same in both changelogs. Not blocking - just a consistency thing if you are doing another pass.

[jongio]

Minor: this line and the following service entries use the en-dash character as a separator, but the Cosmos DB entry above and Key Vault entries below use a regular hyphen. Consider picking one for consistency across the section.