What it changes
An internal agent can answer from the systems the team actually runs on — what deployed, what is failing, what a row says — instead of from a wiki nobody updated.
What people ask once it is connected
How to connect it
- 1
Paste your oauth token
This provider issues short-lived tokens through an OAuth flow. Paste a valid token; when it expires you replace it, so treat this one as more hands-on than a plain key.
Stored as
AZURE_TOKEN - 2
The agent is briefed automatically
Connecting it hands the agent a short description of what Azure provides and how to call it. You write no routing rules and no prompts.
Azure. GET/POST resource endpoints with Bearer OAuth token. - 3
Ask it something that needs live data
The agent decides a request is needed, makes it, and answers with what came back. If the call fails it says so rather than filling the gap with a guess.
The technical details
- Base URL
- https://management.azure.com
- Authentication
- OAuth token
- Secret name
- AZURE_TOKEN
- Category
- Cloud & Dev
Your key or ours. On your own key, calls run against your account and spend no credits. Where we offer a managed key for a connector you can use ours instead and pay per request in credits — priced per connector, refunded when a request fails.
Questions
What can my AI agent do with Azure?
Microsoft Azure services. Infrastructure, repositories, deployments, databases and records. The agent calls it during a conversation, when the answer needs live data rather than a stored one.
Do I need my own Azure key?
Either. Paste your own AZURE_TOKEN and calls run on your account with no credits spent. Where we offer a managed key for a connector, you can use ours instead and pay per request in credits.
Where is my key stored?
Sealed, write-only. It is encrypted before it is written, never returned to any browser — including yours — and only ever sent to the provider it belongs to. You can replace or remove it at any time.
How does the agent know when to use it?
Connecting it adds a short brief to the agent describing what Azure provides and how to request it. The agent reads that and calls it when a question needs it — you do not write any routing rules.
What if Azure is down or the key is wrong?
The agent says so and carries on with what it does know, rather than inventing an answer. A failed managed request is refunded.
Why is this one more work?
Azure authenticates with OAuth, so the token is short-lived by design. This provider issues short-lived tokens through an OAuth flow. Paste a valid token; when it expires you replace it, so treat this one as more hands-on than a plain key.
Give your agent live data
Describe what you do in a sentence, then connect Azure in the agent’s Connectors tab. It starts using it in the next message.
Build your agent free