Developer Tools · Integration
Azure
Add Azure to your product for your customers, and give your AI agents governed access to it.
Azure access starts in Entra ID: the customer registers or consents to an application, then assigns it a role at a scope, and that scope is where the subtlety lives. Consent at the directory level is not access to anything, because a role assignment is made against a subscription, a resource group or a single resource, and one directory often holds many subscriptions with different owners. Resource ids reflect that hierarchy, carrying the subscription and resource group in the path. Management plane and data plane calls also authenticate against different audiences. Storage-heavy work belongs to the Blob Storage connector instead. fastn keeps each tenant's service principal, its assigned scopes and Microsoft's API churn on its side.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Have each customer consent to your application in their own directory, then assign it a role only where you need one.
Work across several subscriptions under one directory, since a role assignment covers a scope and not everything.
Read resource ids as the hierarchy they are, so your product knows which resource group an item belongs to.
Route storage-heavy features to the Blob Storage connector rather than stretching account-level access to cover them.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports what one customer's subscription contains, limited to the scopes their role assignment covers.
An agent makes an approved resource change, and the subscription and resource group it targeted are recorded.
An agent explains that a call failed because no role was assigned at the scope it needed.
Example prompt
List the resource groups in this subscription and tell me which ones our service principal can write to.
Set up Azure in 4 steps
- 01Enable the Azure connector from your fastn dashboard.
- 02Have each customer authorise their own Azure account, so calls run under their credentials rather than a shared key.
- 03Decide which subscriptions, resource groups, roles and resources your product needs, then assign the service principal a role at the narrowest scope that works.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Azure integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Azure integration without building it. Your customers connect their own Azure account inside your product and work their services, builds and deployments there, with no per-customer code on your side.
- Handle the part that actually costs time: these systems emit a lot of webhooks, and replay after downtime has to be handled. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Azure update is not your on-call problem.
- One integration serves your product and your agents. The same governed Azure connection powers in-product features and gives AI agents scoped, audited access, so you connect engineering activity to the rest of the business without wiring it twice.
Used by these teams
Compare with
AWS
Google CloudWorks well with
Microsoft Entra IDOften used alongside
Tools the same teams tend to run next to Azure, across other categories.
Slack
Snowflake
Airtable
PostgreSQLAzure integration FAQ
How do I add an Azure integration to my product?
Enable the Azure connector in your fastn dashboard, then let each customer authenticate their own Azure account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Azure client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Azure account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Azure account and only ever sees their own services, builds and deployments. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Azure integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reports what one customer's subscription contains, limited to the scopes their role assignment covers.
Who maintains the Azure integration?
fastn does. When Azure changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can I react to Azure events in real time?
Yes, through event triggers. Events are delivered per tenant and can be replayed after an outage, so a webhook missed during downtime is not silently lost.
Can an agent open or update items in Azure?
Yes, within scoped permissions, and every action is audited so an agent's changes are attributable.
What can I build with the Azure integration?
A common starting point: have each customer consent to your application in their own directory, then assign it a role only where you need one. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Azure integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Azure does not change your per-connector cost. You can start free with 3 connected accounts.
Add Azure to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.