By Azure MCP Server 3.0 went stable on October 12. After 50 beta iterations, Microsoft shipped a release that adds nine new toolsets — including a 55-command SRE Agent integration — and locks in security-hardened defaults for new resources. It also brought breaking changes that will quietly break your saved agent prompts, scripts, and configuration if you just bump the version tag. Read before you upgrade.
What Actually Breaks
This is the part that matters most. Version 3.0 ships a cluster of renames and removals that are easy to miss until something stops working in production.
The namespace changes will hit anyone with custom code: Azure.Mcp.Core.* becomes Microsoft.Mcp.Core.* everywhere — including your logging configuration. The command-line rename of azmcp resilience to azmcp resiliency is a one-character difference that will silently break any script or saved prompt using the old name. Your appsettings.json configuration section moves from AzureMcp to MicrosoftMcp.
The response shape changes are the sneakiest. Monitor log queries and Azure AI Search index queries now return results inside a results wrapper property. If you’re parsing those responses directly — in agent code, in scripts, anywhere — you’ll get empty output with no error. Azure Advisor listing now returns ARM-style properties instead of the old flat format. VM creation no longer accepts the Win2019Datacenter and Ubuntu2004 shorthand aliases; you’ll need a full image URN.
Several parameters have been removed outright: --retry-policy options (the SDK now handles retries by default), the --force flag on sql server delete, and a handful of top-level options (--tenant, --auth-method, --user, --sender-name) across various commands. Scan your saved prompts and automation scripts before upgrading anything shared.
Upgrade Checklist
- Run
npm install @azure/mcp@latestordotnet tool update Azure.Mcp - Rename the config section:
AzureMcp→MicrosoftMcpinappsettings.json - Update code namespaces:
Azure.Mcp.Core.*→Microsoft.Mcp.Core.* - Rename all commands:
azmcp resilience→azmcp resiliency(and update tool-name filters) - Remove obsolete parameters from saved calls and scripts
- Update response parsing for Monitor and AI Search to unwrap the new
resultsproperty - Update Advisor response parsing to use ARM-style properties
- Replace VM image shorthand aliases with explicit image URNs
- Test against a dev environment before updating shared deployments
The SRE Agent Toolset Is the Real Story
Once you’ve handled the migration, the most compelling addition in 3.0 is the Azure SRE Agent integration — 55 commands that let AI agents manage the full investigation and incident lifecycle from any MCP-compatible client. Investigations, incidents, connectors, safety hooks, remediation plans, scheduled tasks: all accessible from VS Code, Cursor, or Claude Desktop without leaving your editor.
The toolset includes integrations with PagerDuty and ServiceNow, a Kusto query interface for log analysis during investigations, and a yolo operation that lets agents execute remediation without additional confirmation gates. That last one deserves a read of the documentation before you enable it in production. The toolset requires the Microsoft.App/SREAgentPreview resource provider.
Nine New Toolsets, Briefly
Beyond the SRE Agent, 3.0 lands eight more new or expanded toolsets. Azure Backup covers the full lifecycle: vault inspection, policy management, CMK encryption, cross-region restore, and private endpoint support. Terraform tools let agents pull provider documentation, browse Azure Verified Modules, export existing resources with aztfexport, and validate plans with conftest — useful when you want an AI to help bring manually-created infrastructure into IaC.
Azure Advisor now ranks cost recommendations by impact and estimated annual savings, compares VM options with utilization projections, and returns remediation artifacts. Notably, Advisor tools return instructions for infrastructure-as-code changes rather than applying changes to live resources — a sensible guardrail. Cosmos DB gains schema inference and vector search on items. IoT Hub and Azure IoT Operations add device twin inspection and IoT Operations instance discovery.
Security Defaults and a 39% Startup Boost
New resources created through version 3.0 get hardened defaults: shared keys disabled on storage accounts, public networking disabled on Recovery Services vaults, and RootSquash on NFS shares. These only apply to new resource creation — existing infrastructure is unchanged.
Microsoft also reports a 39% improvement in startup time for targeted CLI invocations. Not the headline feature, but if you run agent workflows that call azmcp frequently, the accumulated latency reduction is meaningful.
The full 3.x changelog on GitHub is the authoritative reference before any upgrade. The official announcement covers the complete toolset additions. Install or update with npm install @azure/mcp@latest.
