Entra ID Users With OnPremises Provisioning Errors
The question it answers: Which users did Entra Connect fail to sync, according to their on-premises provisioning errors?
At a glance
Section titled “At a glance”| Where in the app | Entra ID › Users › OnPrem Provisioning Errors |
| Workload | Entra ID |
| Kind | Table |
| Data | Built from the tenant data IntensiveReports keeps in memory and refreshes in the background, so it opens at once. |
| Licence | No extra licence needed. |
| Report id (API and MCP) | entra.users.on-premises-provisioning-errors |
Columns
Section titled “Columns”| Column | Key | Type |
|---|---|---|
| Display Name | DisplayName | Text |
| User Principal Name | UserPrincipalName | Text |
| Account Enabled | AccountEnabled | YesNo |
| Usage Location | UsageLocation | Text |
What it needs
Section titled “What it needs”Licence: No extra licence needed.
Application permissions on the IntensiveReports app registration (all permissions):
| Permission | API | What it allows | Note |
|---|---|---|---|
User.Read.All | Microsoft Graph | Read all users’ full profiles | |
User-LifeCycleInfo.Read.All | Microsoft Graph | Read all users’ lifecycle information |
Data sources it reads
GET /v1.0/users ($select=onPremisesProvisioningErrors,...)
Through the API and MCP
Section titled “Through the API and MCP”GET /ir-api/v1/reports/entra.users.on-premises-provisioning-errors?size=100An AI assistant reads it with the MCP tool get_report and the id entra.users.on-premises-provisioning-errors. The client needs the Read grant for Entra ID. See Using the API.