Security & Identity · Integration
Microsoft Intune
Add Microsoft Intune to your product for your customers, and give your AI agents governed access to it.
Embed a Microsoft Intune integration so your customers can see and act on their own managed device estate from inside your product. Intune decides which devices and apps are allowed to reach corporate data, so the integration governs access rather than just reporting on it, and least privilege matters: you request only the scopes for the actions you enable, per tenant. fastn handles per-customer authentication, token refresh and API upkeep, and every read and device action is logged so an access change can be traced back to what triggered it.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own Intune tenant so your product reads managed devices, ownership, OS version and compliance state.
Show which configuration and compliance policies apply to a device, so a support flow in your product explains why access was blocked.
Assign or remove an app for a user or group from your product, within the scopes the customer granted.
Trigger your product when a device falls out of compliance or leaves management, and drive the follow-up steps.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent checks a device's compliance state and applied policies before it recommends a fix.
An agent runs a scoped device action such as sync or retire within governed permissions, with the action audited.
An agent reacts to a non-compliant device event and opens the right remediation task.
Example prompt
List devices for this user, show which are non-compliant and explain which policy each one fails.
Set up Microsoft Intune in 4 steps
- 01Open the Microsoft Intune connector from your fastn dashboard.
- 02Have each customer authorise their own tenant with the device management scopes your product needs.
- 03Map the device properties, policies and app assignments you use, 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 Intune integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Microsoft Intune integration without building it. Your customers connect their own Microsoft Intune 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 Intune update is not your on-call problem.
- One integration serves your product and your agents. The same governed Microsoft Intune 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
Jamf
Microsoft Entra ID
OktaOften used alongside
Tools the same teams tend to run next to Microsoft Intune, across other categories.
ServiceNow
Datadog
PagerDuty
AWS CloudWatchMicrosoft Intune integration FAQ
How do I add a Microsoft Intune integration to my product?
Enable the Microsoft Intune connector in your fastn dashboard, then let each customer authenticate their own Microsoft Intune account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Microsoft Intune 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 Intune account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Microsoft Intune 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 Intune 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 device's compliance state and applied policies before it recommends a fix.
Who maintains the Microsoft Intune integration?
fastn does. When Microsoft Intune 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 Intune integration need?
Only the scopes required for the actions you enable. Each customer grants access to their own Microsoft Intune 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 Intune integration?
A common starting point: connect their own Intune tenant so your product reads managed devices, ownership, OS version and compliance state. 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 Intune integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Microsoft Intune does not change your per-connector cost. You can start free with 3 connected accounts.
Add Microsoft Intune to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.