The Microsoft Intune connector is available in every edition, and is currently in beta.
What the catalog looks like
If the app is missing a permission, the tables that need it are left out of the catalog instead of failing every question, and the connection test names the exact permission to grant.
Before you start
1
Register an app in Microsoft Entra ID
In the Entra admin center, create an app registration and a client secret for it.
2
Grant read-only Graph application permissions
Add these Microsoft Graph application permissions and grant admin consent:
DeviceManagementManagedDevices.Read.All, DeviceManagementConfiguration.Read.All, DeviceManagementApps.Read.All and DeviceManagementServiceConfig.Read.All.3
Paste the IDs and test
Enter the tenant ID, client ID and client secret in the connect form and click Test connection.
Fields
Authentication
Entra ID App (Service Principal) —service_principal (system scope, the only mode)
Intune data is tenant-wide inventory, so the connection uses one app identity for everyone — there is no per-user sign-in.
Troubleshooting
A table is missing from the catalog
A table is missing from the catalog
The app lacks the Graph permission for that table (see the table above), or admin consent wasn’t granted. Add the permission, grant consent, and re-index the connection.
Queries are slow or retried
Queries are slow or retried
Graph throttles large tenants. BOW waits and retries automatically when Graph asks it to.
Related
- Microsoft Configuration Manager — on-premises device inventory and patch compliance.
- CrowdStrike Falcon — endpoint detections and vulnerabilities.
- Authentication and access — how connection credentials are stored and scoped.
