--- title: Azure MCP Server 3.0 stable release: More tools. More... description: Azure MCP Server 3.0 is now stable, adding new toolsets for Azure Backup, Resilience Management, SRE Agent, Terraform, Advisor, Monitor, Cosmos DB, IoT Hub,... canonical: https://daily.dev/posts/azure-mcp-server-3-0-stable-release-more-tools-more-possibilities-ih8uo1vpt twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Azure MCP Server 3.0 stable release: More tools. More possibilities | daily.dev og:description: Azure MCP Server 3.0 is now stable, adding new toolsets for Azure Backup, Resilience Management, SRE Agent, Terraform, Advisor, Monitor, Cosmos DB, IoT Hub,... og:url: https://daily.dev/posts/azure-mcp-server-3-0-stable-release-more-tools-more-possibilities-ih8uo1vpt og:image: https://api.daily.dev/og/posts/Ih8Uo1VpT.png og:image:alt: Azure MCP Server 3.0 stable release: More tools. More possibilities og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Azure MCP Server 3.0 stable release: More tools. More possibilities **[DevBlogs](https://daily.dev/sources/devblogs)** · 10 min read · 1 upvotes · 0 comments ## Summary Azure MCP Server 3.0 is now stable, adding new toolsets for Azure Backup, Resilience Management, SRE Agent, Terraform, Advisor, Monitor, Cosmos DB, IoT Hub, and more, letting AI agents inspect and act on Azure operational context. The release also introduces security-focused defaults for new resources (disabled shared keys, disabled public networking on new Recovery Services vaults, RootSquash on NFS shares), clearer tool contracts with structured output modes, improved error codes, and startup performance gains of about 39% for targeted CLI invocations. Upgrading from 2.0 or 3.0 previews requires reviewing a detailed changelog covering renamed commands, changed response payload shapes, removed SQL-verb filtering, configuration namespace changes, and new protocol header requirements. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What breaking changes do I need to handle when upgrading to Azure MCP Server 3.0 from 2.0? Upgrading to Azure MCP Server 3.0 requires removing obsolete parameters from saved calls and scripts, renaming azmcp resilience to azmcp resiliency, replacing monitor healthmodels entity get with monitor healthmodels list or get, moving configuration settings to the MicrosoftMcp section, and updating code namespaces from Azure.Mcp.Core.* to Microsoft.Mcp.Core.*. VM creation now requires an explicit --image parameter since the Win2019Datacenter and Ubuntu2004 aliases were removed. _daily.dev helps engineers track breaking changes like these before they hit a shared deployment._ ### What is the default VM size when creating virtual machines with Azure MCP Server 3.0? The default size is Standard_D2s_v5, and an explicit --image parameter is now required for VM and VM Scale Set creation since the Win2019Datacenter and Ubuntu2004 image aliases were removed. Teams should revisit image, sizing, and cost assumptions when upgrading alongside the new resource-creation security defaults. _Engineers planning infrastructure-as-code changes can follow Azure tooling updates like this on daily.dev._ ### What security defaults does Azure MCP Server 3.0 apply when creating new Azure resources? New Storage accounts disable Shared Key authentication while keeping HTTPS, TLS 1.2, and disabled anonymous blob access; new Event Hubs namespaces disable local authentication; new Recovery Services vaults disable public networking; and new NFS file shares use RootSquash with encryption in transit. These defaults apply only to newly created resources and do not reconfigure existing ones on upgrade. _daily.dev keeps cloud teams current on secure-by-default changes like these across Azure services._ ## Similar posts on daily.dev - [Microsoft Announces Azure MCP Server 2.0 Stable Release for Enterprise AI Automation](https://daily.dev/posts/microsoft-announces-azure-mcp-server-2-0-stable-release-for-enterprise-ai-automation-eg7vnxmzx) · C\# Corner · 0 upvotes · 0 comments - [Azure MCP Server Now Built-In with Visual Studio 2026: A New Era for Agentic Workflows](https://daily.dev/posts/azure-mcp-server-now-built-in-with-visual-studio-2026-a-new-era-for-agentic-workflows-kudgkymaq) · Visual Studio Blog · 3 upvotes · 0 comments - [Power Azure SRE Agent with the tools it needs](https://daily.dev/posts/power-azure-sre-agent-with-the-tools-it-needs-srh0kteyn) · DevBlogs · 0 upvotes · 0 comments --- Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#github](https://daily.dev/tags/github), [#azure](https://daily.dev/tags/azure), [#mcp](https://daily.dev/tags/mcp), [#terraform](https://daily.dev/tags/terraform) [View this post on daily.dev](https://daily.dev/posts/azure-mcp-server-3-0-stable-release-more-tools-more-possibilities-ih8uo1vpt) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Azure MCP Server 3.0 stable release: More tools. More possibilities","url":"https://daily.dev/posts/azure-mcp-server-3-0-stable-release-more-tools-more-possibilities-ih8uo1vpt","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/azure-mcp-server-3-0-stable-release-more-tools-more-possibilities-ih8uo1vpt"},"datePublished":"2026-10-14T20:40:21.680Z","dateModified":"2026-10-14T20:40:47.223Z","description":"Azure MCP Server 3.0 is now stable, adding new toolsets for Azure Backup, Resilience Management, SRE Agent, Terraform, Advisor, Monitor, Cosmos DB, IoT Hub,...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/1cfa67c76fc9c7cf8311bda373002f4d?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/1cfa67c76fc9c7cf8311bda373002f4d?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"DevBlogs","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"DevBlogs","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/8f68b453325f482ebeb73fb780092713","url":"https://daily.dev/sources/devblogs"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/azure-mcp-server-3-0-stable-release-more-tools-more-possibilities-ih8uo1vpt","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-agents,github,azure,mcp,terraform","timeRequired":"PT10M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"DevBlogs","item":"https://daily.dev/sources/devblogs"},{"@type":"ListItem","position":3,"name":"Azure MCP Server 3.0 stable release: More tools. More possibilities"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/azure-mcp-server-3-0-stable-release-more-tools-more-possibilities-ih8uo1vpt#faq","mainEntity":[{"@type":"Question","name":"What breaking changes do I need to handle when upgrading to Azure MCP Server 3.0 from 2.0?","acceptedAnswer":{"@type":"Answer","text":"Upgrading to Azure MCP Server 3.0 requires removing obsolete parameters from saved calls and scripts, renaming azmcp resilience to azmcp resiliency, replacing monitor healthmodels entity get with monitor healthmodels list or get, moving configuration settings to the MicrosoftMcp section, and updating code namespaces from Azure.Mcp.Core.* to Microsoft.Mcp.Core.*. VM creation now requires an explicit --image parameter since the Win2019Datacenter and Ubuntu2004 aliases were removed. daily.dev helps engineers track breaking changes like these before they hit a shared deployment."}},{"@type":"Question","name":"What is the default VM size when creating virtual machines with Azure MCP Server 3.0?","acceptedAnswer":{"@type":"Answer","text":"The default size is Standard_D2s_v5, and an explicit --image parameter is now required for VM and VM Scale Set creation since the Win2019Datacenter and Ubuntu2004 image aliases were removed. Teams should revisit image, sizing, and cost assumptions when upgrading alongside the new resource-creation security defaults. Engineers planning infrastructure-as-code changes can follow Azure tooling updates like this on daily.dev."}},{"@type":"Question","name":"What security defaults does Azure MCP Server 3.0 apply when creating new Azure resources?","acceptedAnswer":{"@type":"Answer","text":"New Storage accounts disable Shared Key authentication while keeping HTTPS, TLS 1.2, and disabled anonymous blob access; new Event Hubs namespaces disable local authentication; new Recovery Services vaults disable public networking; and new NFS file shares use RootSquash with encryption in transit. These defaults apply only to newly created resources and do not reconfigure existing ones on upgrade. daily.dev keeps cloud teams current on secure-by-default changes like these across Azure services."}}]} ```