Microsoft Intune

Integrating Microsoft Intune with Hudu allows you to automatically sync device information from Intune into your Hudu documentation portal.

Before setting up the Microsoft Intune integration, we recommend reviewing our Understanding Integrations article for foundational concepts and helpful tips.

What You'll Need

To set up the Microsoft Intune integration, ensure you have:

Admin or Super Admin access in Hudu.
Global Administrator or Privileged Role Administrator access in Microsoft Entra ID. One of these roles is required to grant admin consent for the integration's permission.
An active Microsoft Intune license and a configured tenant.
Access to the client’s Microsoft Intune tenant.

Integration Features

This integration automatically pulls key device metadata from Microsoft Intune into Hudu, helping you centralize IT documentation and streamline support. The synced information includes:

Model
Manufacturer
Device Ownership
Operating System
Registration Date
Last Sign In Date

Hudu syncs devices that are enrolled and managed in Microsoft Intune, including Windows, macOS, iOS, and Android devices. Devices that are only registered in Microsoft Entra ID and not managed by Intune are not synced.

You can use Connected Fields to map information from this integration into Hudu custom fields. This allows data to appear in list views and be fully searchable across your account. Learn more →

What Hudu needs from Microsoft Intune

Application (client) ID.
Directory (tenant) ID.
Client Secret Value.

Guides

The Microsoft Intune integration is currently only available to be pulled in for a single tenant at a time.

Enabling the Integration

The Microsoft Intune integration can be enabled at any point during your Hudu environment testing and/or during production. Integrations can be merged into your existing documentation based on set rules; providing the ability to start with integration setup, or easily connect them at a later date.

Obtaining the Microsoft Intune Information

Step 1: Register an Application in Azure

Go to the Azure Portal and sign in.
Navigate to Azure Active Directory → App registrations → New registration.
Fill out the form:
Name: Give your app a meaningful name.
Supported account types: Choose Accounts in this organizational directory only.
Leave the Redirect URI empty.
Click Register.
Save the Application (client) ID and Directory (tenant) ID for later.

Step 2: Assign API Permissions

After registering, go to the app’s API permissions section.
Click Add a permission → Microsoft Graph → Application permissions.
Add the following permission:
- DeviceManagementManagedDevices.Read.All (shown in Azure as Read Microsoft Intune devices)
Click Grant admin consent and confirm. The permission's Status column should show Granted. This step requires a Global Administrator or Privileged Role Administrator.

Already using this integration? Add DeviceManagementManagedDevices.Read.All to your existing app registration and grant admin consent. If the same app registration is also used by the Microsoft 365 integration, don't remove the permissions that integration needs.

Step 3: Create a Client Secret

Go to Certificates & secrets → New client secret.
Add a description (e.g., Hudu API Key ) and choose an expiration period.
Click Add.
Copy the value immediately — it will not be shown again.

Setting up the Integration in Hudu

Navigate to Admin → Integrations in Hudu.
Select Microsoft Intune.
Choose a company
Enter your:
- Application ID
- Tenant ID
- Secret Key
Choose a default asset layout for your Intune devices.
Click Save Settings.
Click Test Connection.

Make sure to test the integration for a successful connection before continuing. Do not continue until you see a "Connection Successful" message.
Initiate a sync to import device data.

If you don't see/have not created any asset layouts yet, you’ll need to create these. Visit Asset Layouts for additional information!

Once you have started a sync, you should make sure that company is properly matched (you can always unmatch cards that were matched incorrectly) before proceeding to other companies.

FAQ

Common Error: Test connection unsuccessful

Answer: If you receive the above error, or receive an error when clicking "Test Connection", this either means:

- One (or multiple) of your credentials is incorrect. Verify that you correctly copied the Application ID, Directory ID, and Client Secret Value.
- The required permission is missing or hasn't been granted admin consent. Verify that DeviceManagementManagedDevices.Read.All is added to your app and that its status shows Granted.
- Save your settings again, click refresh, and test for a successful connection again.

Warning: the app registration needs the DeviceManagementManagedDevices.Read.All permission

Answer: This warning appears on the integration's settings and cards pages when the app registration doesn't have the DeviceManagementManagedDevices.Read.All application permission, or when admin consent hasn't been granted for it. The integration can't sync until the permission is added and consented. Creating a new client secret won't clear this warning.

To resolve it:

Open your app registration in Azure and go to API permissions.
Add Microsoft Graph → Application permissions → DeviceManagementManagedDevices.Read.All, as described in Step 2 above.
Click Grant admin consent and confirm the status shows Granted.
Wait a few minutes for the change to take effect in Microsoft, then run a sync in Hudu.

The warning clears after the next successful sync.

Warning: the credentials may be invalid or expired

Answer: This warning means Hudu couldn't authenticate with the credentials entered, usually because the client secret has expired or one of the values was copied incorrectly. Create a new client secret (Step 3 above), enter it in the integration settings in Hudu, save, and run a sync. The warning clears after the next successful sync.

I set up this integration before Hudu 2.48. What changed?

Answer: Starting in Hudu 2.48, the integration reads devices directly from Microsoft Intune instead of Microsoft Entra ID. This fixes managed devices, such as macOS devices, that weren't syncing before. It also means:

Your app registration needs the DeviceManagementManagedDevices.Read.All permission. Add it and grant admin consent as described in Step 2. If you keep the same app registration and client secret, you don't need to change anything in Hudu.
The Only sync managed devices option has been removed. Only Intune-managed devices are synced.
Existing device cards are re-linked on the first successful sync, so duplicates aren't created.
Cards for devices that were only registered in Entra ID and aren't managed by Intune remain in Hudu but will no longer update.