Azure Resource Management

microsoft

Microsoft Azure resource lifecycle, monitoring, cost, and data-plane operations via the official Azure MCP server.

Installs: 3.3k
Namespace: azure
Version: >=3.0.0 <4.0.0
Last attach: reviewed1 months ago
Reliability: 100% uptime (30d)· validated 2026-06-27

Add to your mcp.json

{
  "mcpServers": {
    "azure": {
      "command": "npx",
      "args": [
        "-y",
        "@azure/mcp",
        "server",
        "start"
      ]
    }
  }
}

Open in VS CodeDon't have it? Install FrootAI for VS Code

Attach in a FrootAI play (fai-manifest)

mcp_scope:
  attached:
    - azure

Authentication

az-loginmanaged-identityservice-principal

managed identity / `az login` preferred for local dev; service-principal env vars (AZURE_TENANT_ID + AZURE_CLIENT_ID + AZURE_CLIENT_SECRET) for CI.

No credentials required.

Environment variables

Variable	Required	Auth mode	Description
AZURE_TENANT_ID	no	service-principal	Entra tenant (directory) ID. Required only for the service-principal auth path; omit when using `az login`.
AZURE_CLIENT_ID	no	service-principal	App registration (service principal) client ID. Required only for the service-principal auth path.
AZURE_CLIENT_SECRET	no	service-principal	Service-principal client secret. Required only for the service-principal auth path; pass via env, never inline in args (doctrine #6).
AZURE_SUBSCRIPTION_ID	no	any	Default subscription scope. Optional; tools accept an explicit subscription argument when unset.

Sample tools

azure.subscription
List and inspect Azure subscriptions in scope.
azure.group
List and manage resource groups.
azure.monitor
Query Azure Monitor logs and metrics.
azure.storage
Inspect storage accounts, blobs, and queues.
azure.keyvault
List Key Vault secrets, keys, and certificates (metadata).

Used in recipes

FAI cookbook recipes that attach azure.

Destructive-action audit

2 destructive tools — confirm per call

Each runs only when the trust policy allows it; under allowDestructive: false they prompt per call.

azure.resource_delete
azure.group_delete

Destructive-action audit (X2.18): resource/group deletion tools are flagged in `destructive_tools` and are blocked when the trust policy sets `allowDestructive: false`.

Known limitations

Requires an authenticated Azure context (`az login` or service-principal env vars); without it tools return an auth error rather than an empty list.
Tool surface is large and subscription-scoped — many tools require an explicit subscription or resource-group argument.

Spec contributors

Maintainers who landed commits onmcp-specs/azure.json.

pspsbali

Freshness

When this spec was last reviewed by a maintainer and last machine-validated against the live server.

Spec last reviewed: 1 months ago(2026-06-25)
Auto-validated: never