Check ID:
Provider: Azure
Service:
Severity: HIGH
Categories:
Resource type:
entra_policy_user_consent_for_verified_appsProvider: Azure
Service:
entraSeverity: HIGH
Categories:
identity-access, e3Resource type:
NotDefinedWhat this check verifies
Microsoft Entra authorization policy for the default user role is assessed for assignment of the user-consent policymicrosoft-user-default-legacy. Its presence means users can self-consent to app permissions; its absence indicates consent is restricted (e.g., only verified publishers or low-impact scopes).
Risk
Broad self-consent enables OAuth consent phishing and rogue apps to gain tokens to tenant data (confidentiality), request write scopes to change resources (integrity), and persist via refresh tokens after password changes. Mis-scoped grants can drive lateral movement and privilege escalation.Recommendation
Enforce least privilege for app consent:- Remove
microsoft-user-default-legacy - Allow consent only for verified publishers and low-impact permissions (e.g.,
microsoft-user-default-low) - Require admin approval for higher-risk scopes via the admin consent workflow
- Periodically review and revoke unused consent grants
Remediation
- CLI
- Terraform
- Dashboard steps
References
- https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-privileged-access#pa-1-separate-and-limit-highly-privilegedadministrative-users
- https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/configure-user-consent?pivots=portal#configure-user-consent-to-applications
Where this check fires
This check runs on every scheduled scan against your Azure account. Findings appear at Cloud Security → Findings filterable byCheck ID = entra_policy_user_consent_for_verified_apps. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to Azure checks