Azure Resource Manager MCP connector
Connect Azure Resource Manager to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot or any MCP client can read activity logs and manage alerts, action groups and processing rules inside each person's own Azure access, with every call logged.
- Connects over OAuth
- Free 14-day trial
- No credit card
Which action groups have no email receivers in production?
Working in Azure Resource Manager with Elaichi
-
Get single Azure Resource Manager action group by ID
-
Azure Resource Manager action groups get test notifications
-
Action groups get test notifications resource group
How to connect Azure Resource Manager to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Azure Resource Manager MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Azure Resource Manager MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Azure Resource Manager MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Azure Resource Manager MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Azure Resource Manager MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Azure Resource Manager to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Azure Resource Manager through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Azure Resource Manager is logged.
-
Platform engineering
Find out what changed before an outage
Ask what happened in the activity log for a subscription over the last hour and get the deployments, deletions and role changes listed in order, with the account behind each one.
-
Site reliability
Create an alert rule in plain words
Describe the condition, such as any virtual machine deleted in production, and the activity log alert is created and pointed at the right action group.
-
On-call
Keep on-call receiving the right alerts
When the rota changes, update the email and SMS receivers in an action group and send a test notification to confirm it actually lands.
-
Security
Trace who made a change and when
Pull activity log entries for a resource group filtered to administrative events and see which account changed what, ready to paste into an incident write-up.
-
IT operations
Quiet alerts during a maintenance window
Set an alert processing rule that suppresses notifications for a resource group for the length of the window, then remove it once the work is done.
-
Compliance
Review alert coverage across subscriptions
List every activity log alert and action group, spot resource groups that nobody is watching, and ask which event categories are available to alert on.
Try asking
- “Which action groups have no email receivers in production?”
- “List activity log alerts that fire on resource deletions.”
- “What changed in the prod resource group in the last hour?”
What connecting Azure Resource Manager gets you
6 screens from Elaichi, each doing one job for your Azure Resource Manager account.
Ask Elaichi to work across your apps.
Which action groups have no email receivers in production?
List activity log alerts that fire on resource deletions.
What changed in the prod resource group in the last hour?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask what changed in Azure Resource Manager.
Three starter prompts pull live activity logs and alert rules into a plain answer.
Copy the endpoint
AI apps
One endpoint for Azure Resource Manager, every client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.
Tool catalog
521 Azure Resource Manager tools, no code needed.
Activity logs, alerts, action groups and processing rules, ready to use without custom code.
Toolboxes
Every team gets its own toolbox.
Scope Azure Resource Manager alerts and action groups to the team that owns them.
Shared connections
Share the connection, never the credential.
One person connects Azure Resource Manager and teammates work through it without seeing a secret.
Audit log
Every Azure Resource Manager call has a name.
When, who, what happened, type and resource, in an append-only log you can search.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Azure Resource Manager digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch action groups
Azure Resource Manager
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Azure Resource Manager
Queued
Workflows
A schedule starts the work, a person approves.
Logs are fetched, grouped, drafted into a digest, approved, then posted to Azure Resource Manager.
Azure Resource Manager health
Refreshed 4 minutes ago · every 15 minutes · from the action groups collection
Action groups
1,284 ↓ 12%
Activity log alerts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Action groups created
Last 14 days
By team
Share of activity
Production 34%
Staging 27%
Platform 21%
Security 18%
Collections and dashboards
Azure Resource Manager health, computed without a model.
Four metrics, 14 days of alerts created and a team breakdown, refreshed on a schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Azure Resource Manager
All three can connect Azure Resource Manager to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Azure Resource Manager tools | Allow or restrict single Azure Resource Manager tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Azure Resource Manager call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Azure Resource Manager tools for your AI agents
521 tools are ready to call through Elaichi's MCP endpoint the moment you connect Azure Resource Manager, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Showing 169 of 521 Azure Resource Manager tools here. Connect Azure Resource Manager and call search_tools or tools/list over the MCP endpoint for the complete set.
Questions, answered
How do I connect Azure Resource Manager to Claude?
In Elaichi, choose Azure Resource Manager and sign in with your Microsoft account over OAuth. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in to Elaichi and Azure Resource Manager is ready to use.
Does Azure Resource Manager work with ChatGPT and Cursor as well as Claude?
Yes. Once Azure Resource Manager is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect Azure Resource Manager once and every client you use gets it.
What can an AI agent actually do with my Azure Resource Manager data?
An agent connected to Azure Resource Manager can read activity logs to tell you what changed in a subscription or resource group and who changed it. It can create, update and remove activity log alerts, action groups and alert processing rules, add or fix receivers, and send a test notification to check an action group works. Short, concrete asks such as the name of a resource group and a time window work better than long sentences.
Does connecting Azure Resource Manager give the AI everything in my subscriptions?
No. Every call to Azure Resource Manager runs as the person who signed in, so the agent sees only the subscriptions, resource groups and alerts that person's Azure role already allows. Elaichi can narrow that access further with roles and restrictions, and it can never widen it beyond what Azure Resource Manager already grants.
Can I stop an agent from deleting or changing things in Azure Resource Manager?
Yes. Restrictions in Elaichi work per action, so you can allow reading activity logs while restricting deleting an action group or changing an alert, set on a role or on one person. A restricted tool still appears in Elaichi's tool search flagged as restricted, but no client can run it against Azure Resource Manager, whatever the prompt says.
What happens to an Azure Resource Manager connection when someone leaves?
Offboarding that person in Elaichi ends their access to Azure Resource Manager at once, in every client they had connected. A connection they shared keeps working for everyone else on the team. If you ever want Azure Resource Manager gone entirely, disconnecting it once in Elaichi removes it from every client.
Does the Azure Resource Manager MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Azure Resource Manager is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Azure Resource Manager?
Yes. Both let Claude, ChatGPT or Cursor use Azure Resource Manager. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Azure Resource Manager call.
How is Elaichi different from Composio for Azure Resource Manager?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Azure Resource Manager: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Azure Resource Manager in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot