Security & Identity · Integration
Microsoft Entra ID
Add Microsoft Entra ID to your product for your customers, and give your AI agents governed access to it.
Embed a Microsoft Entra ID integration so your customers can manage users, groups, and role assignments from inside your product, with access scoped per tenant and every call recorded. fastn requests only the scopes needed for the actions you enable, which matters because the blast radius of an identity change is large.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read users and group membership from their own directory.
Create, disable, or update users from your product.
Manage group and role assignments so access changes happen where admins work.
Trigger your product when a user is created, disabled, or changes group.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent checks a user's groups and roles before answering an access question.
An agent disables an account within governed permissions during offboarding.
An agent reacts to a new joiner and provisions the right group membership.
Example prompt
List accounts that have not signed in for 90 days and the groups each still belongs to.
Set up Microsoft Entra ID in 4 steps
- 01Open the Microsoft Entra ID connector from your fastn dashboard.
- 02Have each customer consent to the application with least-privilege scopes.
- 03Map the user attributes and groups your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Microsoft Entra ID integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Microsoft Entra ID integration without building it. Your customers connect their own Microsoft Entra ID account inside your product and work their users, groups and roles there, with no per-customer code on your side.
- Handle the part that actually costs time: the blast radius of an error is large, so least-privilege and auditability are non-negotiable. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Microsoft Entra ID update is not your on-call problem.
- One integration serves your product and your agents. The same governed Microsoft Entra ID connection powers in-product features and gives AI agents scoped, audited access, so you keep access and identity in step across a customer's estate without wiring it twice.
Used by these teams
Compare with
Okta
Amazon Cognito
Auth0Often used alongside
Tools the same teams tend to run next to Microsoft Entra ID, across other categories.
ServiceNow
Datadog
PagerDutyMicrosoft Entra ID integration FAQ
How do I add a Microsoft Entra ID integration to my product?
Enable the Microsoft Entra ID connector in your fastn dashboard, then let each customer authenticate their own Microsoft Entra ID account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Microsoft Entra ID client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Microsoft Entra ID account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Microsoft Entra ID account and only ever sees their own users, groups and roles. 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 Microsoft Entra ID 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 checks a user's groups and roles before answering an access question.
Who maintains the Microsoft Entra ID integration?
fastn does. When Microsoft Entra ID 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.
What permissions does the Microsoft Entra ID integration need?
Only the scopes required for the actions you enable. Each customer grants access to their own Microsoft Entra ID tenant, permissions are scoped per tenant, and every call is recorded so an access change can be traced to its source.
Can access changes be automated safely?
Yes. Provisioning and deprovisioning can be driven from your product or an agent within governed permissions, with every action audited, which is what makes automated access changes reviewable after the fact.
What can I build with the Microsoft Entra ID integration?
A common starting point: read users and group membership from their own directory. 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 Microsoft Entra ID integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Microsoft Entra ID does not change your per-connector cost. You can start free with 3 connected accounts.
Add Microsoft Entra ID to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.