Zero Trust Assessment permissions and roles

To run the Zero Trust Assessment, arrange API permissions, administrator consent, directory roles, workload roles, and Azure resource access. Treat these as separate requirements. Grant access only to the services and resources you intend to assess.

These requirements describe the development source. Published packages can differ. Activate eligible roles through Microsoft Entra Privileged Identity Management before connecting, and reconnect after changing access.

Interactive user access

Use a highly privileged administrator for initial setup only, not for every assessment merely because that account granted consent.

For data loss prevention (DLP) checks, verify workload authorization as well as directory roles.

Service or task Required access and scope
Initial Microsoft Graph consent For delegated permission grants, Cloud Application Administrator, Application Administrator, or another authorized consent role. Privileged Role Administrator can grant consent for any API, including Graph Application permissions; Global Administrator can also perform this setup. Consent doesn't assign runtime roles to the assessment user.
Microsoft Graph assessment context All Graph permissions below and an active Global Reader or Global Administrator role. The module validates these roles for delegated authentication. Prefer Global Reader for the assessment account.
Custom security attributes Attribute Assignment Reader, or Attribute Assignment Administrator, in addition to CustomSecAttributeAssignment.Read.All. Global Reader or Global Administrator alone doesn't grant access to attribute values.
Azure Reader at the subscription/resource scopes to assess, or equivalent read permissions for the relevant resource providers. Azure access is separate from Microsoft Entra ID directory roles. Resource Graph only returns resources the caller can read; check coverage across every intended subscription.
Exchange Online and Defender protection policies Global Reader plus Security Reader for protection-policy checks. With customized workload roles, verify access to Get-AntiPhishPolicy, Get-HostedContentFilterPolicy, Get-MalwareFilterPolicy, Get-SafeAttachmentPolicy, Get-SafeLinksPolicy, Get-AtpPolicyForO365, and Get-TeamsProtectionPolicy.
Security & Compliance (Microsoft Purview) Global Reader provides the standard read-only role mapping, including Sensitivity Label Reader and View-Only DLP Compliance Management. Verify effective access to Get-Label, Get-LabelPolicy, Get-DlpCompliancePolicy, Get-DlpComplianceRule, Get-DlpEdmSchema, and Get-DlpSensitiveInformationType. Customized role groups can change access.
SharePoint Online SharePoint Administrator for tenant administration commands, including Get-SPOTenant. Global Reader alone isn't sufficient for these PowerShell commands.
Azure Information Protection (AIP) Azure Information Protection Administrator, Compliance Administrator, Compliance Data Administrator, or Global Administrator; alternatively, delegated AIP administrative access configured with Add-AipServiceRoleBasedAdministrator. Don't enable the AIP super-user feature or add yourself as a super user just to read its configuration.
Defender advanced hunting ThreatHunting.Read.All plus access to the relevant Defender data through the user's effective security roles and data scope. Graph consent alone doesn't remove workload or licensing restrictions.

These requirements don't guarantee that every check runs. Service configuration, licenses, scoped permissions, and supported authentication modes also affect coverage. Investigate permission errors rather than treating them as tenant security failures or granting broad administrator access without review.

For service-specific authorization details, see:

Microsoft Graph permissions

The development source requests these delegated permissions. For app-only authentication, configure the Application permission with the same name and grant administrator consent. A delegated grant doesn't authorize an application token.

  • Application.Read.All.
  • AttackSimulation.Read.All.
  • AuditLog.Read.All.
  • CopilotPackages.Read.All.
  • CrossTenantInformation.ReadBasic.All.
  • CustomSecAttributeAssignment.Read.All.
  • DeviceManagementApps.Read.All.
  • DeviceManagementConfiguration.Read.All.
  • DeviceManagementManagedDevices.Read.All.
  • DeviceManagementRBAC.Read.All.
  • DeviceManagementServiceConfig.Read.All.
  • Directory.Read.All.
  • DirectoryRecommendations.Read.All.
  • EntitlementManagement.Read.All.
  • IdentityRiskEvent.Read.All.
  • IdentityRiskyServicePrincipal.Read.All.
  • IdentityRiskyUser.Read.All.
  • LifecycleWorkflows-Workflow.Read.All.
  • NetworkAccess.Read.All.
  • Policy.Read.All.
  • Policy.Read.ConditionalAccess.
  • Policy.Read.PermissionGrant.
  • PrivilegedAccess.Read.AzureAD.
  • PrivilegedAssignmentSchedule.Read.AzureADGroup.
  • PrivilegedEligibilitySchedule.Read.AzureADGroup.
  • Reports.Read.All.
  • RoleManagement.Read.All.
  • SecurityAlert.Read.All.
  • SecurityEvents.Read.All.
  • SecurityIdentitiesHealth.Read.All.
  • SecurityIdentitiesSensors.Read.All.
  • SecurityIncident.Read.All.
  • ThreatHunting.Read.All.
  • UserAuthenticationMethod.Read.All.

To list the requirements for your installed version, import the module and query its scope helper:

Import-Module ZeroTrustAssessment
Get-ZtGraphScope

The list comes from Get-ZtGraphScope. For permission definitions and supported types, see the Microsoft Graph permissions reference.

App-only permissions and roles

Certificate authentication uses an application identity, not the signed-in user's roles. Configure the app registration, enterprise application/service principal, and resource assignments separately.

Graph Application permission consent requires Privileged Role Administrator, Global Administrator, or a suitable custom consent role. Application Administrator alone isn't sufficient. Azure resource-role assignment also requires administrative authority at the target scope.

Service Application permissions and authorization
Microsoft Graph The Application permissions in the Graph list, with administrator consent. The module checks the complete list even for a single pillar. The delegated user's Global Reader role isn't the app-only Graph context check.
Azure Reader, or equivalent resource-read permissions, assigned to the service principal on each intended subscription/resource scope. Graph permissions don't grant Azure access.
Exchange Online Office 365 Exchange Online > Exchange.ManageAsApp, with consent, plus supported directory roles or Exchange role-group assignments to the service principal. Global Reader and Security Reader are supported read-oriented directory roles; verify access to the protection cmdlets listed above.
Security & Compliance Microsoft Exchange Online Protection > Exchange.ManageAsApp, with consent, plus supported directory roles or Purview role-group assignments to the service principal. Follow the Exchange/Purview app-only setup and configure authorization for both services if using both.
SharePoint Online SharePoint > Sites.FullControl.All Application permission, with administrator consent, for tenant administration APIs. This is a broad permission, not a read-only scope or the Graph permission with the same name. See SharePoint admin API authorization.
Azure Information Protection The current connector expects Azure Rights Management Services > Application.Read.All, with consent. This is separate from Graph Application.Read.All. The pinned AipService 3.1.0.0 exposes certificate service-principal parameter sets even though published cmdlet help doesn't list them. Verify effective access to Get-AipServiceSuperUser and Get-AipServiceSuperUserFeature in your environment.

Caution

A read-only assessment doesn't mean every service offers read-only connection permissions. Review the SharePoint full-control grant with your tenant administrator. Don't add content-decryption or write permissions merely to suppress an error.

Exchange and Purview support built-in directory roles and custom workload role groups. Their role groups don't automatically share membership. Use the app-only role-assignment procedure to scope commands.

Some service cmdlets don't support app-only authentication. A successful connection isn't proof of complete coverage; review connection outcomes and test diagnostics.