
The Azure MCP Server is a server from Microsoft that implements the Model Context Protocol (MCP) so that AI agents and MCP clients can work with Azure resources through natural language. It authenticates with Microsoft Entra ID through the Azure Identity library and limits actions to the caller's Azure role-based access control (RBAC) permissions.
Microsoft's documentation states that the server "enables AI agents and clients to interact with Azure resources using natural language commands" and "implements a set of tools per the Model Context Protocol." Documented examples include listing storage accounts, running KQL queries, querying Log Analytics, running resource health diagnostics and deploying to App Service with the Azure Developer CLI (azd).
The Model Context Protocol is described by its maintainers as "an open-source standard for connecting AI applications to external systems." Microsoft's overview distinguishes hosts (applications that use MCP clients), clients (components of hosts that manage connections to servers) and servers (programs that provide resources, tools and prompts). The Azure MCP Server is a server in this sense.
Microsoft announced the Azure MCP Server in public preview on April 17, 2025, in a post on the Azure SDK blog. The initial release covered Azure Cosmos DB, Azure Storage, Azure Monitor (Log Analytics), Azure App Configuration, resource groups, the Azure CLI and the Azure Developer CLI, and was started with the command npx -y @azure/mcp@latest server start.
The code was first developed in the Azure/azure-mcp repository on GitHub. That repository's README states that it "is archived as of August 25, 2025" and that "the Azure MCP team is using https://github.com/microsoft/mcp to develop the code and issues" formerly held there. GitHub's archive banner on the same repository shows a later archive date of February 6, 2026. Development continues in microsoft/mcp under servers/Azure.Mcp.Server, whose README states that "Azure MCP Server 2.0 is now generally available."
Official documentation describes two configurations.
Local server. The server runs on a developer's machine, started by an editor extension or a package manager. It is distributed on NuGet (Azure.Mcp), npm (@azure/mcp) and PyPI (msmcp-azure), and as a Docker container. Microsoft states that the local server "is intended strictly for developer use within your organization."
Self-hosted remote server. The README describes hosting the server "as a remote endpoint when your client requires HTTP-based MCP servers." Microsoft Learn includes guides for deploying it to Azure Container Apps as "a self-hosted remote server over HTTPS" for use with Microsoft Foundry and Copilot Studio.
Tool exposure is configurable. The tools reference lists server modes namespace (the default), consolidated, all and single, an option to expose only selected namespaces such as storage or keyvault, and a read-only option under which "no write operations are allowed."
According to Microsoft, the server "uses Entra ID through the Azure Identity library" and "uses your Azure user credentials or managed identity to ensure authorized access." Access is governed by Azure RBAC, so the tools available to a caller reflect that caller's subscription permissions. For Docker, the README describes supplying AZURE_TENANT_ID, AZURE_CLIENT_ID and AZURE_CLIENT_SECRET in an environment file. Microsoft's security guidance treats the server as an OAuth 2.1 resource server and states that clients must use PKCE in authorization code flows.
Microsoft's get started page lists Cline, Cursor, Google Antigravity, IntelliJ, Visual Studio, Visual Studio Code and Windsurf as code editors, along with GitHub Copilot CLI, the GitHub Copilot SDK and GitHub Copilot cloud agent. The overview also names Eclipse, GitHub Copilot agent mode, the OpenAI Agents SDK and Semantic Kernel.
Visual Studio Code. Microsoft's "Azure MCP Server" extension provides MCP integration for Azure and is used from GitHub Copilot in agent mode.
Visual Studio. In Visual Studio 2022 version 17.14.30 or later, Azure MCP tools are included with the Azure development workload, with no separate extension.
Claude Code and Claude Desktop. The GitHub README documents a Claude Code plugin that "packages the Azure MCP Server along with Azure-related agents and skills," and MCPB bundles that can be installed into Claude Desktop.
Tools are grouped into namespaces, one or more per Azure service. Namespaces listed in Microsoft's tools reference include storage (Azure Storage), keyvault (Azure Key Vault), cosmos (Azure Cosmos DB), sql (Azure SQL), postgres and mysql, redis, aks (Azure Kubernetes Service), appservice, functionapp, monitor (Azure Monitor), kusto (Azure Data Explorer), servicebus, eventhubs, role (Azure RBAC), policy, pricing, foundry (Microsoft Foundry) and extension, which covers the Azure CLI, Azure Developer CLI and Azure Quick Review CLI.
Azure MCP Server: covers Azure resources and services. Runs locally (editor, npm, NuGet, PyPI, Docker) or as a self-hosted remote server over HTTPS. Authenticates with Microsoft Entra ID through Azure Identity and Azure RBAC. Version 2.0 is generally available.
Azure DevOps MCP Server (local): covers Azure DevOps work items, repositories, pipelines, wikis and test plans. Runs locally over stdio via the @azure-devops/mcp npm package, with browser sign-in or Azure CLI authentication. Supported, with new investment focused on the remote server.
Azure DevOps Remote MCP Server: the same core scenarios as the local server, hosted by Azure DevOps at https://mcp.dev.azure.com/{organization} using streamable HTTP. Uses Microsoft Entra and works only with Entra-backed organizations. Announced in public preview on March 17, 2026.
MCP reference servers: demonstrations such as Everything, Fetch, Filesystem, Git, Memory, Sequential Thinking and Time. Run locally; authentication varies by server. Educational examples, not production-ready.
The main distinction is ownership of the hosting. The Azure DevOps remote server is operated by the Azure DevOps service, while a remote Azure MCP Server is deployed and operated by the customer. Client support for the Azure DevOps remote server has changed since launch. The March 2026 announcement listed only Visual Studio and Visual Studio Code with GitHub Copilot as supported and other clients as "Coming Soon." Current Microsoft Learn documentation also lists Microsoft Foundry, Copilot Studio, GitHub Copilot CLI, and Cursor or Claude Code with a custom Microsoft Entra app registration, and states that Claude Desktop and Codex are not currently supported.
A local Azure MCP Server suits individual development work under the developer's own Azure identity.
A self-hosted remote Azure MCP Server suits agents in Microsoft Foundry or Copilot Studio, or clients that require HTTP-based servers. Microsoft's security guidance suggests placing it behind Azure API Management, which can validate Entra ID tokens, limit request rates and log requests for audit.
Work centered on Azure Boards, Repos or Pipelines is covered by the Azure DevOps MCP Server rather than the Azure MCP Server.
The MCP reference servers are intended for learning how to build servers, not for managing cloud resources.
Microsoft's overview states that "Azure MCP Server tools are disabled by default in supported hosts," and the GitHub README warns that "Autonomous or misconfigured clients may perform destructive actions." Its security guidance recommends least-privilege RBAC roles, enabling only the tools each caller needs, managed or workload identities instead of long-lived secrets, and avoiding the confused-deputy pattern. For local use it advises not exposing the local endpoint to untrusted networks and not using a local server with production data or credentials. It also recommends treating tool descriptions and responses as untrusted input.
Microsoft maintains a catalog of its MCP servers in the microsoft/mcp repository. Third-party directories such as bestmcptools.org list the Azure MCP Server alongside other MCP servers, including the Azure DevOps MCP Server.
Yes. The Azure MCP Server is Microsoft's MCP server for Azure services and authenticates with Microsoft Entra ID.
Microsoft publishes several. The microsoft/mcp repository describes itself as a "catalog of official Microsoft MCP (Model Context Protocol) server implementations," and builds the Azure MCP Server and the Microsoft Fabric MCP Server. The Azure DevOps MCP Server is maintained in a separate repository.
MCP is the protocol for connecting AI applications to external systems. An MCP server is a program that implements the server side of that protocol and provides tools, resources or prompts to clients.
Yes. Microsoft documents running it locally and deploying it as a self-hosted remote server on Azure Container Apps.
The source is in github.com/microsoft/mcp under servers/Azure.Mcp.Server. The earlier github.com/Azure/azure-mcp repository is archived and read-only.
The project README documents a Claude Code plugin that packages the Azure MCP Server with Azure-related agents and skills, and lists Claude Code configuration file locations.
Security considerations for Azure MCP Server (Microsoft Learn)
Deploy remote MCP Server with Microsoft Foundry (Microsoft Learn)
Azure DevOps Remote MCP Server public preview (Azure DevOps Blog)
What is the Model Context Protocol? (modelcontextprotocol.io)
Ethan Halfhide builds software products with AI tools and runs BestMCPTools, a directory of Model Context Protocol servers.
HandWiki Curated Articles — Sharing Knowledge, Advancing Discovery.

Ads help maintain this website.
Ads are shown when you're not logged in.