What it covers
The Azure MCP Server puts “all Azure MCP tools in a single server”, as the README says. Its tools span more than 45 Azure service areas: Storage, Cosmos DB, Azure SQL and PostgreSQL, Key Vault, AKS, App Service, Functions, Monitor and Log Analytics (KQL queries), Resource Graph, RBAC, Policy, Retail Pricing, Bicep and Terraform guidance, and more. Typical prompts are “List my storage accounts”, “Run this KQL query against Log Analytics” or “What does this VM size cost in West Europe?”.
Microsoft lists these hosts in its docs: VS Code, Visual Studio (built in from Visual Studio 2022 17.14.30 with the Azure development workload), IntelliJ, Eclipse, Cursor, Windsurf, Cline, Google Antigravity, GitHub Copilot CLI, the Copilot SDK and the Copilot cloud agent. Claude Code gets it through the Azure plugin in Anthropic’s official plugin marketplace.
How sign-in and rights work
The server does not hold its own credentials. It uses the Azure Identity library and Entra ID, so it acts as you (or as a managed identity when hosted). Microsoft’s overview puts it plainly: “Tool availability reflects your Azure subscription permissions.”
That makes Azure RBAC the real control. The README’s section on permissions and risk warns that “autonomous or misconfigured clients may perform destructive actions” and advises least-privilege roles, adding that safeguards against destructive operations “are not standardized in the MCP specification and may not be supported by all clients”.
Setting it up for a team
- Choose the host most people already use. For a Copilot shop, the VS Code extension is the shortest path. For Claude Code users, install the Azure plugin.
- Decide the server mode. The VS Code extension has
azureMcp.serverMode:namespace(the default, one tool per service),single(one tool) orall(every tool). Fewer tools means less context spent on tool descriptions. - Limit services with
azureMcp.enabledServices, for example onlystorageandmonitorfor people who mainly investigate. - Turn on read-only (
azureMcp.readOnly) for everyone who does not need the agent to change resources. - Give people a role that fits the agent, not their full admin role. If a developer is Owner on a subscription, their agent is too.
- Decide on telemetry. It is on by default;
AZURE_MCP_COLLECT_TELEMETRY=falseturns it off, and you can send your own copy to Application Insights.
The common misunderstanding
Many people read “Azure MCP Server” as a hosted Microsoft endpoint, like some other vendors offer. By default it is not: it runs as a local process on the developer’s machine (through the extension, npx, uvx, dnx or Docker) and talks to Azure with that person’s login. Microsoft documents self-hosted remote deployments for Microsoft Foundry and Copilot Studio, but then your organization runs it. And Microsoft states that “the local MCP server is intended strictly for developer use within your organization”, not for external apps. For the trade-offs, see local vs remote MCP server.
What this means for a team
Everyone’s agent gets the same reach into Azure, through the same audited identities. What it does not get is your team’s operational knowledge: which resource group is safe to experiment in, which alerts are known noise, why a firewall rule exists, which naming convention the platform team agreed on. That lives in wikis, tickets and heads, and each person’s agent starts without it. The wider risks of connecting agents to production systems are covered in is MCP safe to use in a company, and the general idea in what is an MCP server.
Where Bombos fits
The Azure MCP Server gives each agent hands in Azure; Bombos gives all of them the same memory of how your team runs it. It is a plugin underneath Copilot, Claude Code, Codex, Cursor and the other AI tools your team uses that learns how your team works, draws on your docs and repos, and shows with every answer what it rests on. Your agents act in Azure; Bombos remembers. It runs in the cloud in Europe or standalone on your own server, and one engineer can try it first with their own agents.
Related questions
How do I install the Azure MCP Server?
In VS Code, install the GitHub Copilot Chat extension and the Azure MCP Server extension, then sign in with Azure: Sign In. Elsewhere you can run it with npx (@azure/mcp), uvx (msmcp-azure), dnx (Azure.Mcp) or Docker. In Claude Code, the Azure plugin bundles it: /plugin install azure@claude-plugins-official.
Can I stop the agent from changing resources?
Yes. The server has a read-only mode (azureMcp.readOnly in the VS Code extension) that prevents write operations. Combine it with a least-privilege RBAC role, because Microsoft warns that misconfigured clients may perform destructive actions.
Does the Azure MCP Server send telemetry?
Yes, telemetry is on by default. Set the environment variable AZURE_MCP_COLLECT_TELEMETRY to false to turn all of it off.
Can we host it centrally for the whole team?
Microsoft documents self-hosted deployments for Microsoft Foundry and Copilot Studio. Note that Microsoft says the local server is intended strictly for developer use within your organization, not for external applications.
