Microsoft Entra ID (formerly Azure AD)
Connector maturity: GA. See Connector maturity.
Description
The Entra ID connector uses the Microsoft Graph API to discover user accounts, groups, and directory role assignments in a Microsoft Entra ID tenant (Microsoft's rebrand of Azure Active Directory, effective 2023). It is the cloud counterpart to the on-premises Active Directory connector and provides identity data for organisations that use Entra ID as their primary identity provider.
This connector replaces the earlier separate "Microsoft 365" connector, which scanned the same tenant's users and groups but had no visibility into real Entra directory roles — it approximated privilege by checking whether a group's name contained "Admin", "Global", or "Privileged". Entra ID's role-based detection is a strict superset of what Microsoft 365 discovered, so the two were consolidated into this single connector.
System Type Classification
| Field | Value |
|---|---|
| System Type | Directory Service |
| Default Scan Priority | 10 (scanned first) |
Version Support
| OrbisID Edition | Supported |
|---|---|
| Community | No |
| Pro | Yes |
| Enterprise | Yes |
Entra ID scanning requires a Pro or Enterprise licence.
Supported Protocol
| Protocol | Port | Notes |
|---|---|---|
| Microsoft Graph API (HTTPS) | 443 TCP | OAuth 2.0 client credentials flow |
What OrbisID Discovers
| Data | Source |
|---|---|
| User accounts | GET /users |
| User status (enabled/disabled) | accountEnabled property |
| Group memberships | GET /groups/{id}/members |
| Directory roles | GET /directoryRoles |
| Privileged role members | Global Administrator, Privileged Role Administrator, Security Administrator, Exchange Administrator, SharePoint Administrator, User Administrator, Helpdesk Administrator, Compliance Administrator, Application Administrator, Cloud Application Administrator |
| On-premises synced accounts | onPremisesSyncEnabled property (optional filter) |
Service principals (app registrations, enterprise apps, managed identities) — optional, see azureIncludeServicePrincipals below | GET /servicePrincipals, classified as NHI Subtype Managed Identity, Certificate, or Application based on servicePrincipalType/keyCredentials/passwordCredentials |
Connection Requirements
Entra ID App Registration
OrbisID authenticates using an App Registration (service principal) with the client credentials flow. No user interaction is required.
- In the Azure Portal, navigate to Microsoft Entra ID → App registrations → New registration
- Give the app a name (e.g.,
OrbisID Scanner) and register it - Note the Application (client) ID and Directory (tenant) ID
- Navigate to Certificates & secrets → New client secret — note the secret value immediately
- Navigate to API permissions → Add a permission → Microsoft Graph → Application permissions, and add:
| Permission | Purpose |
|---|---|
User.Read.All | Read all user accounts and their properties |
Group.Read.All | Read group memberships |
Directory.Read.All | Read directory roles and privileged role members |
Application.Read.All (optional) | Only needed if azureIncludeServicePrincipals is enabled — read service principals for NHI subtype classification. Without it, service principal enumeration is skipped with a scan warning rather than failing the scan |
- Click Grant admin consent for the permissions
Credential Mapping
| OrbisID Field | Entra ID Value |
|---|---|
credential.username | Application (client) ID |
credential.password | Client secret value |
credential.domain | Directory (tenant) ID |
System Attributes
| Attribute | Required | Description |
|---|---|---|
azureTenantId | Fallback | Tenant ID if not stored in credential.domain |
azureOnPremSyncedOnly | No | Set to true to scan only on-premises synced accounts |
azureIncludeServicePrincipals | No | Set to true to also discover service principals (app registrations, enterprise apps, managed identities) as NHI accounts. Requires the Application.Read.All Graph permission — off by default so upgrading systems aren't affected until the extra permission is granted |
azureCollectUsage | No | Set to true to read when each discovered service principal last signed in (see When Access Was Last Used). Needs azureIncludeServicePrincipals, the AuditLog.Read.All Graph permission and an Entra ID P1/P2 licence |
Owners of Service Principals
With Include Service Principals on, each scan also reads the owners of each service principal ($expand=owners, using the same Application.Read.All permission) and records the mail address and user principal name of each user owner. OrbisID uses them to suggest an owner identity for the account (see Owners of Non-Human Accounts). Owners that are not users are skipped. If the owners cannot be read, the scan continues with a warning and the accounts simply have no suggestions.
Secrets and Certificates
With Include Service Principals on, each scan also reads the client secrets and certificates of the discovered applications: their ID, name, start date and end date. They come from the app registrations (/applications) and from the service principals themselves, matched by application ID, and use the same Application.Read.All permission. Microsoft never returns a secret value after it is created, so none is read. An expired secret or certificate is shown as inactive. Entra does not report when a secret was last used, so that date is shown as not reported. If the application list cannot be read, the scan continues with a warning and credentials already recorded are kept.
When Access Was Last Used
- Users: every scan reads each user's last successful sign-in (Graph
signInActivity) when the tenant allows it, and shows it as the Last Used date. This needs theAuditLog.Read.AllGraph permission and an Entra ID P1 or P2 licence; without them users simply have no date. - App registrations and managed identities: with Read When App Registrations Last Signed In (
azureCollectUsage) on, and service principals discovered, each scan also reads Graph's service principal sign-in report (/reports/servicePrincipalSignInActivities) and shows the latest sign-in of any kind (the app signing in as itself, or on behalf of users) as the Last Used date. This needsAuditLog.Read.Alland Entra ID P1/P2 too. If the permission or licence is missing the scan continues and logs a warning. - Sign-in dates say that an identity was used, not which directory roles or groups it used, so roles and groups show no usage date. No date means Entra reported none, not that the identity was never used.
Network Requirements
The OrbisID server (or On-Premise Agent) must have outbound HTTPS access to:
login.microsoftonline.com— OAuth 2.0 token endpointgraph.microsoft.com— Microsoft Graph API
This connector can be routed through an On-Premise Agent like any other cloud/REST connector — useful when the OrbisID server itself doesn't have outbound internet access. Assign a Scan Agent Group to the system as usual; both Test Connection and scanning will run from the agent instead of the OrbisID server.
Configuration Steps
- Complete the Entra ID App Registration steps above
- Create a Credential in OrbisID:
- Username: Application (client) ID
- Password: Client secret value
- Domain: Directory (tenant) ID
- Navigate to Systems → Add System
- Fill in the fields:
| Field | Value |
|---|---|
| Name | Descriptive name (e.g., Entra ID – contoso.com) |
| Hostname / IP Address | graph.microsoft.com — pre-filled and locked; Microsoft Graph is a fixed global endpoint, not something you configure per system |
| OS Type | Microsoft Entra ID |
| System Type | Directory Service |
| Credential | The App Registration credential created above |
- Click Test Connection to verify the app registration credentials
- Click Save
Detected Applications
Turn on Detect Applications (in the system's settings, under Detected Applications) to bring in the enterprise applications your users and groups are assigned to in Entra ID.
- Each enterprise application (the apps listed under Enterprise applications in the Entra admin center) is added as a child system named
<this system> - <application>, for example Entra ID - Salesforce. - Each app role that is assigned becomes an access entitlement on that child system (assignments without a role appear as Default access). App roles whose name contains admin are marked privileged.
- Users assigned directly are members of the role; members of an assigned group get it through that group, which is shown as the path.
Detected applications are maintained by the Entra ID system's scans: refreshed on every scan, archived when an application is removed (restored if it returns), and archived when Detect Applications is turned off. If the app registration lacks Application.Read.All, the scan carries on and previously detected applications are left unchanged.
Link a detected application to the system that scans the same application directly, then use Reconcile access to compare the two - see Detected Applications.
Real-Time Account & Entitlement Events
Beyond periodic full scans, OrbisID can poll Microsoft Graph's auditLogs/directoryAudits on a short interval to detect account and group-membership changes near-real-time — requires the AuditLog.Read.All Graph permission in addition to what a normal scan needs. Opt-in Graph Change Notifications are also supported, though OrbisID does not create or renew the subscription itself — you create it via the Graph API and point it at OrbisID's webhook URL. See Real-Time Events — Pro/Enterprise only.
Troubleshooting
| Symptom | Likely Cause | Resolution |
|---|---|---|
401 Unauthorized on test connection | Invalid client ID or secret | Verify the client ID and secret; ensure the secret has not expired |
403 Forbidden | Missing or unapproved API permissions | Ensure all three permissions are granted with admin consent |
AADSTS700016 token error | Incorrect tenant ID | Verify the Directory (tenant) ID in credential.domain |
| Scan fails reading groups or directory roles | Directory.Read.All not granted | Grant and consent to Directory.Read.All in the app registration. The scan fails rather than reporting users without their roles |
| Scan completes with zero accounts | Tenant ID mismatch | Confirm the tenant ID matches the tenant where the app is registered |
| System was migrated from an old "Microsoft 365" connector | The old connector was consolidated into this one | No action needed — the migration renamed the system's OS Type in place and preserved its credential and tenant ID; existing scan history is unaffected |
| Test Connection shows only "Authentication failed. Verify the credential and connector configuration." | This generic message is shown for every connector regardless of cause — it does not itself indicate a token vs. permissions vs. tenant ID problem | Check the OrbisID server (or agent) application log for the corresponding warning, which includes the real Microsoft Graph/Entra ID error (HTTP status and AADSTS error code/body) |
| Scan fails with a Microsoft Graph error or throttling message | Microsoft Graph returned an error (a 5xx, a permission change, throttling or a network problem) while reading users, groups, directory roles or their members | The scan is marked failed and nothing is archived or deactivated, so a Graph outage cannot make accounts or memberships disappear. Fix the cause shown in the scan's log (Scanning → History) and scan again; a throttled scan is retried later. A group deleted while the scan runs is skipped with a warning instead |