Microsoft (admin consent)
Connect Entra ID, Intune and Defender in one step by having a Microsoft administrator approve Navigator’s app. There is no app registration to create and no client secret to store or rotate.
Beta. This way of connecting is new. It is built to Microsoft’s documentation and works as described below; tell us at [email protected] if anything behaves differently in your tenant.
At a glance
| Data provided | Devices, Users, Vulnerabilities, Software (from Entra ID, Intune and Defender, whichever you choose) |
|---|---|
| Authentication | Admin consent to Navigator’s Microsoft app. No client secret. |
| Where to configure | Connectors → Add a Connector → Microsoft |
| Who can connect | A Navigator administrator or credential manager (signed in with multi-factor authentication), working with a Microsoft Global Administrator or Privileged Role Administrator |
Before you start
You need two things:
- In Navigator: an account with the administrator or credential manager role, signed in with multi-factor authentication.
- In Microsoft: a Global Administrator or Privileged Role Administrator of your Microsoft tenant to approve the app. Microsoft only lets those two roles approve Microsoft Graph application permissions. Cloud Application Administrator and Application Administrator cannot.
The Microsoft administrator is the person who clicks Connect and signs in, so if you are not one yourself, ask them to do the steps below.
If you manage a customer’s tenant as a partner (for example through delegated admin access), your technician’s role does not count here. Use the Entra ID, Intune or Defender connector with an app registration instead.
Permissions requested
All of these are application permissions that only read data. Navigator cannot change anything in your Microsoft tenant. The same list is shown to the administrator in Navigator before they connect.
| API | Permission | Used for |
|---|---|---|
| Microsoft Graph | User.Read.All | Read users |
| Microsoft Graph | Device.Read.All | Read Entra devices |
| Microsoft Graph | DeviceManagementManagedDevices.Read.All | Read Intune devices |
| Microsoft Graph | DeviceManagementConfiguration.Read.All | Read Intune configuration and policies |
| Microsoft Graph | Directory.Read.All | Read directory data |
| Microsoft Graph | GroupMember.Read.All | Read group memberships |
| Microsoft Graph | Policy.Read.All | Read Conditional Access and other policies |
| Microsoft Graph | RoleManagement.Read.Directory | Read directory role assignments |
| Microsoft Graph | AuditLog.Read.All | Read sign-in activity and audit logs |
| Defender for Endpoint | Machine.Read.All | Read machines |
| Defender for Endpoint | Software.Read.All | Read software inventory |
| Defender for Endpoint | User.Read.All | Read machine users |
| Defender for Endpoint | Vulnerability.Read.All | Read vulnerability data |
Microsoft approves the whole list at once. The services you tick in Navigator decide which ones sync, not which permissions are approved. The Defender permissions need Microsoft Defender for Endpoint in your tenant.
Setup
- In Navigator, go to Connectors → Add a Connector and choose Microsoft, then Connect.
- Review the permissions listed on the page.
- Enter a Connection Name. The default is
microsoft. If an Entra, Intune or Defender connection already has that name, Navigator does not replace it; choose another name, or delete the old connection first. - Tick the services to sync: Entra, Intune, Defender. Leave Defender unticked if your organization does not use Microsoft Defender for Endpoint.
- Click Connect with Microsoft.
- Sign in with your Microsoft administrator account. Use the same account for the whole process.
- On Microsoft’s approval page, review the permissions and approve them.
- You return to Navigator. The connection shows as waiting while Navigator confirms with Microsoft that approval exists and that the person who approved it holds one of the two required roles. This is usually quick.
- Once verified, the first sync starts. Nothing syncs before verification passes.
If the connection does not verify
The connection card and its View details page say what state it is in.
| State | What it means | What to do |
|---|---|---|
| Waiting or verifying | Navigator is still checking with Microsoft. | Click Check again after a minute. |
| Approval missing or incomplete | Consent was not granted, or some permissions are missing. | Click Connect again and approve every permission. |
| Not an administrator | The person who approved is not a Global Administrator or Privileged Role Administrator. | Have one of those administrators connect again. |
| Tenant already connected | This Microsoft tenant is already connected to another Navigator organization. | Contact [email protected] if that is unexpected. |
If a permission is added to Navigator’s app later, every connected tenant is asked to approve again, and a sync that is missing a permission reports that you need to reconnect.
After connecting
- One connection, three services. Entra ID, Intune and Defender each get their own card, sync history and details page once the connection is verified. The cards carry an Admin consent tag. Connections made with an app registration carry a Client secret tag.
- Sync options. On the connection’s details page, choose which Entra device trust types to import, whether to include registered users, and which Defender onboarding statuses to include. These are the same options the secret-based connectors have. Nothing is filtered until you untick a box.
- Deactivate and reactivate. Deactivating pauses the whole connection. It stops syncing and stops counting toward coverage, and imported records are kept. Reactivating starts a sync right away.
- Exposure categories. Assign these on the Entra ID, Intune and Defender cards, as with any connector.
Removing the connection
Delete on the connection’s details page stops syncing for good and removes the saved settings, including the Microsoft tenant it was connected to. A deleted connection cannot be resumed, and its name cannot be reused. Imported records are kept and age out.
Deleting in Navigator does not remove Microsoft’s approval. To revoke it, a Microsoft administrator removes the Navigator application under Enterprise applications in Microsoft Entra. Do this as well if you are offboarding.
Moving from an app registration to admin consent
An existing Entra, Intune or Defender connection that uses a client secret keeps working, and it takes priority over consent for the same connection name. Moving is not automatic:
- Connect with admin consent under a new connection name.
- Check that it verifies and the first sync completes.
- Delete the old secret-based connections.
The records are filed under the connector and connection name, so a new name means a fresh set of records for the new connection.
Choosing between the two ways to connect
| Admin consent | App registration (client secret) | |
|---|---|---|
| Setup | One approval by a Microsoft administrator | Create an app, add permissions, create a secret, copy IDs |
| Secret to rotate | None | Yes, for each connector |
| Who can set it up | Global Administrator or Privileged Role Administrator | Anyone who can create app registrations and grant consent |
| Azure connector | Not included | Not applicable; Azure always uses its own app registration |
The Azure connector is not part of admin consent, because it needs an Azure role assignment on your subscriptions.
Vendor documentation
Microsoft’s own pages: Grant tenant-wide admin consent to an application and the Microsoft Graph permissions reference.
Related connectors
Entra ID, Intune and Defender are the services this connection feeds. See the Connectors overview for how the Microsoft connectors fit together.