Data & Storage · Integration
Microsoft Graph
Add Microsoft Graph to your product for your customers, and give your AI agents governed access to it.
Embed a Microsoft Graph integration so your customers can grant your product one governed connection to their Microsoft 365 tenant instead of you wiring each service separately. Graph is the single API surface over users, groups, OneDrive and SharePoint files, mail, calendars and Teams, and the hard parts are consent scoping, throttling and change notifications rather than the endpoints themselves. fastn handles per-tenant OAuth and admin consent, token refresh, paging and retry on throttle, and delivers Graph change notifications as replayable events so an update is not lost while your product is unreachable.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own Microsoft 365 tenant once, then read users, groups, files, mail and calendar events through a single governed connection.
Request only the Graph scopes each feature needs, so an admin approves a narrow consent rather than a blanket one.
Subscribe to change notifications so your product reacts when a file, message or event changes in the customer's tenant.
Let fastn absorb Graph paging and throttling, so a large first read backs off correctly instead of failing your onboarding.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent looks up a user, their group memberships and their recent files before it acts.
An agent creates or updates an item in the customer's tenant within scoped permissions, with the call audited.
An agent reacts to a Graph change notification and continues a workflow from there.
Example prompt
Find the files this user edited in the last week and the meetings they attended about the same project.
Set up Microsoft Graph in 4 steps
- 01Open the Microsoft Graph connector from your fastn dashboard.
- 02Have each customer authorise their own Microsoft 365 tenant, with admin consent where a scope requires it.
- 03Select the resources and scopes your product uses, then enable actions and change notifications.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Microsoft Graph integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Microsoft Graph integration without building it. Your customers connect their own Microsoft Graph account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Microsoft Graph update is not your on-call problem.
- One integration serves your product and your agents. The same governed Microsoft Graph connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Works well with
Microsoft Office 365 Management APIOften used alongside
Tools the same teams tend to run next to Microsoft Graph, across other categories.
Anthropic Claude
OpenAI
Hugging FaceMicrosoft Graph integration FAQ
How do I add a Microsoft Graph integration to my product?
Enable the Microsoft Graph connector in your fastn dashboard, then let each customer authenticate their own Microsoft Graph account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Microsoft Graph 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 Graph account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Microsoft Graph account and only ever sees their own records, datasets and fields. 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 Graph 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 looks up a user, their group memberships and their recent files before it acts.
Who maintains the Microsoft Graph integration?
fastn does. When Microsoft Graph 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.
Does the Microsoft Graph integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large Microsoft Graph reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the Microsoft Graph integration?
A common starting point: connect their own Microsoft 365 tenant once, then read users, groups, files, mail and calendar events through a single governed connection. 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 Graph integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Microsoft Graph does not change your per-connector cost. You can start free with 3 connected accounts.
Add Microsoft Graph to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.