> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/dokumentation/automation/connectors/microsoft-intune.md).

# Microsoft Intune

Microsoft Intune connector: retrieve managed devices from Intune and set the device owner – connection, actions and examples for device assignment.

**Path:** "Automation" → "Workflows" → flow designer → module **"Microsoft Intune"**

The **Microsoft Intune connector** connects equipme in [workflows](https://hub.equipme.io/dokumentation/automation/workflows.md) with your device management in Intune. It reads the managed devices (laptops, smartphones, tablets) and sets the device owner. This lets you reconcile the device inventory in Intune with the assets in equipme and keep the device ↔ employee assignment up to date in both systems.

## What for?

* **Device assignment:** a device is handed over to an employee in equipme → set the device owner in Intune.
* **Inventory reconciliation:** read all Intune devices regularly and compare them with the assets in equipme (e.g. via the serial number).
* **Enrich device data:** store the operating system, version or last contact from Intune as metadata on the asset in equipme.
* **Offboarding:** before the return, check which devices in Intune are still assigned to the leaving employee.

## Prerequisites

* The enabled [automation module](https://hub.equipme.io/dokumentation/automation.md)
* A Microsoft tenant with a **Microsoft Intune** license
* A Microsoft account with the role "Intune Administrator" (or a role with read and write permissions on managed devices)
* Consent to the permission for managed devices in the tenant (usually **admin consent**)
* For examples using equipme data, a connection of the [equipme connector](https://hub.equipme.io/dokumentation/automation/connectors/equipme.md) as well

## Setting up the connection

1. In the flow designer, drag a component of the "Microsoft Intune" module onto the canvas (e.g. *ListDevices*).
2. Click **Connect account**.
3. Sign in with the tenant account in the Microsoft sign-in window and accept the requested permissions.
4. The connection appears with the name of the Microsoft account under **"Accounts"**.

{% hint style="info" %}
"Microsoft Intune", ["Microsoft Entra ID"](https://hub.equipme.io/dokumentation/automation/connectors/microsoft-entra-id.md) and ["Microsoft Dynamics 365 Business Central"](https://hub.equipme.io/dokumentation/automation/connectors/microsoft-business-central.md) use the same Microsoft sign-in. All actions run with the permissions of the signed-in account.
{% endhint %}

## Triggers

The connector has **no triggers of its own**. Flows start via other triggers – e.g. a trigger of the [equipme connector](https://hub.equipme.io/dokumentation/automation/connectors/equipme.md) (*New Employee*, *New Fulfillment Order*), a schedule (Scheduler) or a webhook.

## Actions

| Component      | Purpose                                                                                                  | Important options                                                                   |
| -------------- | -------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- |
| ListDevices    | Read all managed devices – with device name, operating system, serial number, user and compliance status | none; returns the devices as one list                                               |
| GetDevice      | Read one managed device                                                                                  | Device ID (Intune device ID)                                                        |
| SetDeviceOwner | Set the device owner of a managed device                                                                 | Device ID, User principal name (UPN of the employee, e.g. `max.muster@company.com`) |

{% hint style="info" %}
*ListDevices* has no "Output Type" setting. To process the devices one by one, add a component that splits lists after it.
{% endhint %}

## Examples

### Set the device owner on handover

1. **Equipme › New Fulfillment Order** – trigger on a new device delivery.
2. **Equipme › Get Service Instance** – read the asset with serial number and assigned employee.
3. **Microsoft Intune › ListDevices** – read the devices and use a **filter** to select the device with the same serial number.
4. **Microsoft Intune › SetDeviceOwner** – Device ID from step 3, user principal name of the employee.

### Weekly inventory reconciliation

1. **Scheduler** – weekly.
2. **Microsoft Intune › ListDevices** – all managed devices.
3. **Equipme › List Service Instances** – assets of the device category.
4. Compare both lists via the serial number; report devices that exist only in Intune to IT via **Email › Send Email**.
5. Optional: **Equipme › Set Service Instance Metadata** – store the operating system and last contact from Intune on the asset.

## Notes and limitations

* The connector works with the devices **managed in Intune**. Devices that are only registered in Entra ID can be read with the [Entra ID connector](https://hub.equipme.io/dokumentation/automation/connectors/microsoft-entra-id.md) (*ListDevices*, *ListUserDevices*).
* The device ID in Intune is not the same as the device ID in Entra ID. For Intune actions, always use the ID from *ListDevices* or *GetDevice* of this module.
* After the first reconciliation, store the Intune device ID as metadata on the asset in equipme. Later flows can then use *GetDevice* directly.

## Troubleshooting

| Problem                                              | Cause / solution                                                                                                         |
| ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| Sign-in at "Connect account" asks for admin approval | A Global Administrator must consent to the permission for managed devices in the tenant.                                 |
| Error "Forbidden"                                    | The signed-in account lacks an Intune role, or the tenant has no Intune license.                                         |
| *GetDevice* does not find the device                 | The Entra ID device ID was passed instead of the Intune device ID.                                                       |
| *SetDeviceOwner* fails                               | Check the UPN (typo, account blocked or deleted).                                                                        |
| *ListDevices* returns an empty list                  | No devices are enrolled in Intune in the tenant, or the account only sees some devices because of restricted scope tags. |

You can find the logs of every run under **"Insights"**. For help, contact [support](https://hub.equipme.io/dokumentation/help/support.md).

## Frequently asked questions

**Can the connector wipe or lock devices?**

No. It reads devices and sets the device owner. Use Intune directly for remote actions such as locking or wiping.

**Which identifier links an Intune device to an asset in equipme?**

The serial number is the most reliable. After the first reconciliation, store the Intune device ID as metadata on the asset.


---

# 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://hub.equipme.io/dokumentation/automation/connectors/microsoft-intune.md?ask=<question>&goal=<user_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.
