Azure Resource Manager MCP Server Adds Write Tools at Ignite; Agents Inherit User's Full Permissions
Reported by Visual Studio Magazine and Tech Times2 sources ↓
Microsoft expanded the Azure Resource Manager MCP server with tools for agents to create, update and act on Azure resources. Calls use the signed-in user's Azure permissions; Microsoft has not said how many resource types support writes.
Key points
- New tools let agents create or update individual resources and manage resource groups
- Agents can run resource actions such as starting or restarting, and retrieve keys or validate resources
- Deployment tools support previewing with a what-if check, starting, checking status and canceling
- Microsoft documentation and the Azure repository still describe the server as preview
- The server supports read access across more than 3,500 resource types; Microsoft gives no count for writes
Sources
Details
A Nov. 13 Microsoft Tech Community post described the added tools, which use Azure Resource Manager operations to create or update individual resources, manage resource groups and run actions supported by specific resources. Examples include starting or restarting resources, retrieving keys and validation. Deployment tools can preview a deployment with a what-if check, start it, check its status and cancel it.
The server runs calls under the Azure permissions of the signed-in user behind the agent. Azure role-based access control and Azure Policy apply to these changes; Microsoft documentation says ARM authorizes each request.
Microsoft documentation and the Azure repository continue to label the server as preview, and its tool reference warns that schemas may change. The more than 3,500 resource types cited by Microsoft refer to read access, not write support; Microsoft has not published a count of resource types that accept writes.
Written from coverage as of
Images
- Tech Times
Stocks in this story
Change since open: 20 Nov to 21 Nov 2026
Last refresh