Treat user-consented application grants as persistent access, not as a one-time sign-in event. Review high-privilege scopes, remove stale consented apps, and monitor for unusual API activity that remains valid after password resets. The key control is lifecycle oversight of delegated access, not just authentication hardening.
What makes OAuth consent different from a normal sign-in?
OAuth consent is an authorisation event that can outlive the login session that created it. In Microsoft 365, a user-approved grant can let an app keep calling APIs until the permission is removed or expires, so security teams should treat consent as standing delegated access. That matters because authentication controls alone do not revoke a valid grant.
For the protocol basis, RFC 6749: The OAuth 2.0 Authorization Framework defines OAuth as delegated authorisation, which is why a consented app can remain active after the user signs out or changes a password.
Which Microsoft 365 consents create the most risk?
High-privilege scopes are the main concern, especially anything that can read mail, files, directory data, or offline access tokens. The risk increases when the app is third-party, poorly governed, or rarely reviewed, because consented access can become persistent and difficult to spot in normal account hygiene checks.
A practical starting point is the app-governance view in SaaS-to-SaaS and OAuth App Governance Guide, which focuses on consent, scopes, token risk and revocation workflows for connected apps.
How should teams detect and clean up risky consent grants?
Review consented applications as part of an access lifecycle process, not only during incident response. Prioritise apps with broad scopes, stale ownership, unusual publishers, or low business justification, then revoke or replace them where the access path no longer has a current need. Monitor for API activity that persists after password resets, because that is a sign the grant itself, not the password, is the live access mechanism.
Microsoft 365 Security Guide is useful here because it ties app consent review to Microsoft 365 audit logging, Entra controls and hardening of the surrounding tenant configuration.
Risk and Threat Considerations
OAuth consent creates a durable trust relationship that attackers can abuse after the original phish, prompt, or lure has faded. If a malicious app gains a consent grant, it may retain access even when the password is reset, the user is reauthenticated, or the mailbox password changes, which makes consent abuse a common persistence path in Microsoft 365.
Failure mechanism: The organisation treats consent as a one-time login event and fails to track the granted scopes, so the app keeps acting with delegated authority until someone explicitly removes the grant or disables the application.
Impact: Attackers can continue reading mail, pulling data, or abusing API access without needing the victim's password again, which increases dwell time and makes mailbox or data exposure harder to contain.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10 addresses the attack and risk surface, while NIST SP 800-53 Rev 5 sets the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-2 — Account Management | Consent grants need lifecycle inventory and removal when access is no longer needed. |
| AC-3 — Access Enforcement | Scopes and grants must be enforced so apps only retain approved Microsoft 365 access. | |
| AU-6 — Audit Review, Analysis, and Reporting | Unusual API activity after resets requires log review and correlation. | |
| Recommendation — Track app grants as accounts or access paths and remove stale delegated access promptly. Enforce least-privilege scopes and block unnecessary delegated access to Microsoft 365 data. Review audit logs for persistent app activity and investigate API use that outlives password resets. | ||
| OWASP Non-Human Identity Top 10 | NHI-01 — Improper Offboarding | Stale consented apps are an offboarding and revocation problem for non-human access. |
| NHI-05 — Overprivileged NHI | High-privilege OAuth scopes create excessive delegated access risk. | |
| NHI-07 — Long-Lived Secrets | Persistent OAuth grants can remain valid long after the original user session. | |
| Recommendation — Revoke unused app grants and remove access paths when the integration is no longer needed. Reduce granted scopes to the minimum needed and reapprove any high-privilege consent. Shorten the lifetime of delegated access where possible and remove grants that no longer need persistence. | ||
Practitioner Guidance
What to prioritise: Start with apps that can read email, files, or directory data, then sort by offline access and by whether the app has a clear business owner. If ownership is unclear, treat the grant as a governance problem first, not a tuning problem.
What to verify: Confirm whether the tenant allows user consent, whether admin consent is required for sensitive scopes, and whether you can inventory all consented apps and their effective permissions. The control is only real if you can prove which grants exist and who approved them.
Decision rule: If an app still has a valid reason to access Microsoft 365 data, keep it under review and scope it narrowly; if the business need is unclear or expired, revoke the grant and rotate any dependent credentials or sessions that were issued around that integration.
Practitioner takeaway: Consent risk is a delegated-access problem, so the winning control is not just stronger sign-in policy, it is disciplined review of who or what is still authorised to act after sign-in ends.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 2, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org