> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/guides/integrations/integrations-mdm/intune-integration.md).
# Connect Microsoft Intune
Connect Microsoft Intune to Siit to sync managed computers and mobile devices into the equipment inventory, see device health and link devices to requests
**About the Integration**
Enhance your organization’s device management capabilities with Siit’s seamless integration with Microsoft Intune. Synchronize mobile and computer devices managed by Intune directly into Siit’s equipment inventory, providing your team with comprehensive visibility and control.
With this integration, IT and asset managers can centralize monitoring, access valuable insights, and improve troubleshooting by associating devices directly with tickets.
**What benefits does the integration offer?**
**Centralized Device Monitoring**
Siit serves as a single hub for asset managers, syncing all devices from Intune. This ensures your IT team has a complete view of the entire device fleet.
**Valuable Insights**
Siit provides detailed information about each device’s health and status, empowering your team to stay on top of performance, issues, and compliance.
**Enhanced Visibility**
Devices associated with employees and their tickets are visible directly in Siit. This accelerates troubleshooting and improves end-user support.
**Efficient Filtering**
Quickly search and filter devices in Siit by type, health status, or user association, making it easy to find the right information fast.
**How to set up Intune integration?**
The process of connecting Siit with Microsoft Intune is straightforward. Follow these steps:
1. Log in to your Siit Admin Dashboard: [https://app.siit.io](https://app.siit.io/)
2. Click the **Settings** (⚙️) icon in the top-right corner.
3. Go to **Integrations → Integrations library**
4. Locate the Intune integration and click **Connect now**
5. Review and confirm the permissions.
**⚠️ Required permissions for the integration to work:**
In your ActiveDirectory, the user who set up the integration needs at least one of the following roles :
* Global Administrator
* Intune Service Administrator
For reference, here is one of the Intune documentation to see which role can have a Read/Write access to the Intune data -> [Role-based access with Intune](https://learn.microsoft.com/en-us/intune/intune-service/fundamentals/role-based-access-control).
You're all set!
**What you'll see synced automatically**
* **Office location**: Siit maps office location from Intune automatically through the equipment field mapping.
* **Status follows the owner:** assigning an owner to a spare device moves its status to "In service" automatically, unless you changed the status in the same edit.
**Can I run Intune actions in a workflow?**
Yes, **Reset passcode** runs in workflows, on mobile devices only. It doesn't return a passcode, so nothing is sent to the requester. The recovery key can't run in a workflow, because it needs your own Microsoft session: send it from the request or the device page. See [Run device actions from a workflow](/guides/workflows/run-device-actions-from-a-workflow.md).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.siit.io/guides/integrations/integrations-mdm/intune-integration.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
