Skip to main content

Azure

The Azure integration is a single connection - one app registration (service principal) in your Microsoft tenant - that reads across several separate Microsoft APIs:

APIWhat it reads
Azure Resource Manager (management.azure.com)Subscriptions and every cloud resource assessed under Cloud Exposure
Microsoft Graph (graph.microsoft.com)Entra ID inventory, sign-in, provisioning, directory audit and risk detection logs, security alerts, and Intune audit events
Microsoft Defender for Endpoint (api.securitycenter.microsoft.com)Devices, vulnerabilities, software inventory and security recommendations
Office 365 Management (manage.office.com)Microsoft 365 audit activity (Exchange, SharePoint, general)
Power Platform (api.bap.microsoft.com and related)Environments, DLP policies, apps, connectors and flows

It is read-only. Every call is a GET. Nothing is deployed into your tenant and nothing is changed.

Because the one connection spans several APIs, its permissions are not one grant but many, and each sync type needs its own. A missing permission fails only the sync types that depend on it and leaves the rest working - which is why the integration can show Entra ID data while Defender returns 403, or collect resources while Intune returns 403. When a sync type reports credential authenticated but is not authorised for this API, the credential is fine; the permission behind that one sync type is missing or was never consented.

Application permissions do nothing until a Global Administrator (or Privileged Role Administrator) grants tenant-wide admin consent for them in the Entra admin center, under the app registration's API permissions blade. Adding a permission is not the same as consenting to it. A permission that is listed but shows "Not granted" is the most common cause of Authorization_RequestDenied and credential authenticated but is not authorised for this API.

After adding or consenting to any permission below, re-run the affected sync from Active Integrations.

Permissions by sync type​

All of these are application permissions (the app acts as itself, not as a signed-in user), and all need admin consent.

Azure Resource Manager - cloud resources​

SyncGrant
Cloud resource inventory and postureReader role at the subscription or, better, the management-group scope

This is a role assignment in Azure, not an Entra API permission. See Cloud Exposure for connecting at the highest scope you can.

Microsoft Graph - Entra ID, logs and Intune​

Sync typeMicrosoft Graph application permission
Entra ID usersUser.Read.All
Entra ID users - multi-factor registration stateUserAuthenticationMethod.Read.All (with AuditLog.Read.All)
Entra ID groupsGroup.Read.All
Entra ID app registrationsApplication.Read.All
Entra ID service principalsApplication.Read.All
Entra ID conditional access policiesPolicy.Read.All
Entra ID directory rolesRoleManagement.Read.Directory
Entra ID role assignmentsRoleManagement.Read.Directory
Sign-in, provisioning and directory audit logsAuditLog.Read.All
Identity risk detectionsIdentityRiskEvent.Read.All
Microsoft 365 security alertsSecurityAlert.Read.All
Intune audit logsDeviceManagementApps.Read.All

RoleManagement.Read.Directory covers both directory roles and role assignments. Directory.Read.All also satisfies the directory role reads, but the least-privilege grant above is preferred.

Microsoft Defender for Endpoint​

These are permissions on the WindowsDefenderATP API, not Graph. It is not in the "Commonly used Microsoft APIs" or "More Microsoft APIs" lists, because it is the Defender for Endpoint service in your own tenant rather than a public API. In the Request API permissions dialog, open the APIs my organization uses tab and search for WindowsDefenderATP (application ID fc780465-2017-40d4-a0c5-307022471b92).

If it does not appear even on that tab, the tenant has no Defender for Endpoint service principal yet - that is the licensing and onboarding gap below, not a search problem.

These permissions also depend on a Defender for Endpoint license - see Defender needs a license, not just a permission below.

Sync typeWindowsDefenderATP application permission
Defender devicesMachine.Read.All
Defender vulnerabilitiesVulnerability.Read.All
Defender software inventorySoftware.Read.All
Defender security recommendationsSecurityRecommendation.Read.All

Office 365 Management - Microsoft 365 audit activity​

Sync typeOffice 365 Management APIs application permission
Microsoft 365 activity subscriptions (Exchange, SharePoint, general)ActivityFeed.Read

An empty permission set in the error (The permission set () ... does not include the expected permission) means the app has no Office 365 Management role at all, not a narrower one. Add ActivityFeed.Read and consent.

Power Platform​

Power Platform is the one Azure sync type that needs no Entra API permission and does need a one-time admin-level registration with PowerShell. It is documented on its own page: Power Platform.

Defender needs a license, not just a permission​

Two of the Defender and Microsoft 365 errors are not fixed by granting a permission:

Error textWhat it actually means
No active license found (Defender devices, vulnerabilities, software, recommendations)The tenant has no Microsoft Defender for Endpoint Plan 2 license (standalone or via Microsoft 365 E5 / E5 Security), or onboarding to Defender for Endpoint is not complete
Account is not provisioned (Microsoft 365 security alerts)The tenant is not provisioned for Microsoft 365 Defender / Defender for Endpoint

Grant the WindowsDefenderATP permissions first. If these errors persist with the permissions in place, it is a licensing or onboarding gap in the Microsoft tenant, not an integration setting - confirm the Defender for Endpoint Plan 2 license and that devices are onboarded before expecting these syncs to return data.

Troubleshooting​

Match the message a sync type reports under Active Integrations to its fix:

ErrorCauseFix
Authorization_RequestDenied: Insufficient privileges to complete the operationThe Graph permission for that sync type is not granted or not consentedAdd the permission from the Graph table and grant admin consent
AccessDenied: ... required scopes are missing in the token (conditional access)Policy.Read.All is missingAdd Policy.Read.All and consent
Forbidden: ... Application must have one of the following scopes: DeviceManagementApps.Read.AllThe Intune audit permission is missingAdd DeviceManagementApps.Read.All and consent
AF10001: The permission set () ... does not include the expected permissionThe app has no Office 365 Management roleAdd ActivityFeed.Read and consent
Unauthorized request - No active license found (Defender)Missing WindowsDefenderATP permissions, or no Defender for Endpoint Plan 2 license / not onboardedAdd the Defender permissions; if still failing, check the license and onboarding
Unauthorized request - Account is not provisioned (M365 security alerts)Missing SecurityAlert.Read.All, or the tenant is not provisioned for Microsoft 365 DefenderAdd SecurityAlert.Read.All; if still failing, check the Defender provisioning
Forbidden: The service principal ... does not have permission to access the path ... BusinessAppPlatformThe app is not registered as a Power Platform management applicationRun the one-time registration in Power Platform

A permission narrowed or removed on the Microsoft side later reproduces exactly these errors for the affected sync types while the rest keep working, so an integration that was healthy and now returns 403 on part of itself is a permission change, not a credential expiry.

Microsoft references​

Next​