On November 16, 2026, Microsoft announced that agents using the Azure Resource Manager (ARM) MCP server could create, manage, and update Azure resources through Azure’s control plane. Each call uses the signed-in user’s Azure authorization, and an ARM template preview does not cover every direct resource operation.
What can Azure ARM MCP agents do?
ARM MCP gives compatible agents an interface to Azure Resource Manager, the control plane for Azure resources. Microsoft announced that agents could use it to create, manage, and update resources. The documented tools also cover resource discovery, deployment previews and deployments, direct resource actions, schemas, and cost information. Microsoft Learn’s ARM MCP overview describes the server and its tool categories.
That means an agent’s role can extend beyond looking up infrastructure: it may make changes, provided the signed-in identity has permission for the requested operation and the applicable Azure controls allow it.
Which permissions govern an agent’s actions?
An ARM MCP call runs in the Azure authorization context of the user signed in through the agent or its client. Azure role-based access control (RBAC), the scope of the assignment, Azure Policy, and resource-provider authorization determine what that call can do. Approving a request in the client does not grant Azure permissions. Microsoft Learn’s governance guidance recommends granting only the permissions a task needs, at the narrowest practical scope.
For example, access to inspect resource inventory does not by itself authorize deployments or billing access. Keep those permissions separate when setting up an agent’s identity.
The client must also support ARM MCP’s connection and authentication requirements. MCP compatibility alone does not guarantee that a client can complete the required sign-in flow; some clients may need an Entra app registration. Microsoft’s overview describes those client requirements.
What do deployment previews and Azure Policy cover?
For an ARM template deployment, Microsoft recommends running whatif_deployment before create_deployment and reviewing the proposed resources, names, locations, and parameters. A template what-if preview does not preview every direct resource operation, so review the inputs to direct create-or-update calls separately. If a deployment is cancelled, inspect the resulting resource state rather than assuming it has returned to its previous state. Microsoft’s governance documentation explains these distinct review steps.
Azure Policy assignments continue to apply to ARM requests, including rules that require tags or restrict regions and SKUs. Administrators can also target deployment requests made through ARM MCP, but a policy aimed at deployments does not automatically block every MCP tool or direct resource operation. Treat deployment policy as one control within its scope, alongside the permissions assigned to the user.
Check the permission boundary and review path for each operation; a template preview is not a blanket safety check.
How do Bicep MCP and ARM MCP differ?
Bicep MCP and ARM MCP handle different stages of a template workflow. Bicep MCP authors and validates Bicep code, then builds an ARM template. ARM MCP can preview and deploy that template.
| Server | Role in the workflow | Output or action |
| Bicep MCP | Authors and validates Bicep code | Builds an ARM template |
| ARM MCP | Works with Azure Resource Manager | Previews and deploys the template |