Join our Newsletter — 33% off our NHI Course
Authentication, Authorisation & Trust

Microsoft OAuth

← Back to Glossary
By NHI Mgmt Group Updated November 16, 2026 Domain: Authentication, Authorisation & Trust

Microsoft OAuth is Microsoft's implementation of the OAuth 2.0 authorisation framework for allowing an application to obtain delegated access to resources on a user's behalf. It uses access tokens and consented scopes, and is commonly paired with OpenID Connect when the application also needs user sign-in and identity claims.

What Microsoft OAuth Is Used For

Microsoft OAuth is the delegated access layer that lets an app act on a user’s behalf without collecting the user’s password. In Microsoft ecosystems, that usually means the app requests consented scopes, receives access tokens, and then calls protected Microsoft resources within the boundaries the user or administrator approved.

That separation matters because OAuth is about authorisation, not the user’s sign-in step itself. When Microsoft OAuth is paired with OpenID Connect, the same session can support both delegated resource access and identity sign-in, but those are still distinct security functions with different tokens, claims, and validation rules.

How Microsoft OAuth Works in Practice

A Microsoft OAuth flow usually starts with an application registered in Microsoft identity services and a request for specific permissions. The user, or sometimes an administrator, grants consent, and Microsoft issues tokens that represent what the app may do, for which resource, and for how long. The exact flow varies by client type, but the security model stays the same: permissions are scoped, delegated, and mediated by the identity platform.

The important practical detail is that the application is not “logged in” as the user in a password sense. It receives a token that stands in for authorised access. That design reduces password sharing, but it also means token handling, redirect handling, and consent boundaries become central to security.

Microsoft OAuth security depends on three linked concepts: access tokens, scopes, and consent. Access tokens prove that a request has been authorised for a particular resource and time window. Scopes limit what the token can be used for. Consent is the policy checkpoint that determines whether the requested permissions are acceptable for the app and the tenant.

Because scopes can be broad or narrow, the practical security question is not just whether OAuth is enabled, but whether the requested permissions are proportionate to the task. Overbroad delegated permissions can turn a normal integration into a high-value access path, especially when the app can read mail, files, or directory data.

Microsoft OAuth in Identity and Application Security

Microsoft OAuth sits at the intersection of application security, identity governance, and third-party access. It is part of why modern apps can avoid storing user passwords, but it also creates a trust relationship that has to be reviewed like any other access path. That is why OAuth-based integrations are often assessed alongside application consent, token lifetime, session handling, and privileged resource access.

When an application uses Microsoft OAuth to access sensitive resources, the security model also depends on the surrounding identity controls. That includes who can grant consent, whether the app is verified or internal, and whether the requested permissions are appropriate for the business function. For broader context on OAuth flows and security mistakes to avoid, see the OAuth 2.0 and OpenID Connect Guide for Identity Teams.

Risk and Threat Considerations

Microsoft OAuth is attractive to attackers because a successful consent grant or token theft can produce durable, delegated access without knowing the user’s password. The main danger is not just initial compromise, but abuse of a legitimate trust relationship, which can make malicious access look like normal application activity.

Failure mechanism: Attackers commonly exploit consent phishing, malicious apps, weak permission review, or stolen tokens to gain access that survives ordinary password resets and can continue until tokens are revoked or permissions are removed.

Impact: A compromised OAuth grant can expose mailboxes, files, directory data, and downstream business systems, and it may require both access revocation and a post-incident review of what the app could reach.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

OWASP ASVS and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
OWASP ASVSV10 — OAuth and OIDCCovers OAuth and OpenID Connect authorization and sign-in flows.
Recommendation — Verify OAuth and OIDC integrations for correct scope handling, redirect hygiene, and token validation.
NIST SP 800-53 Rev 5IA-5 — Authenticator ManagementApplies to lifecycle handling of OAuth tokens and related secret material.
AC-3 — Access EnforcementOAuth scopes enforce what delegated access an app may exercise.
AC-6 — Least PrivilegeOAuth consent should grant only the minimum delegated permissions needed.
Recommendation — Manage token issuance, storage, rotation, and revocation as controlled authenticators. Enforce least-privilege permissions for delegated access paths and block overbroad scopes. Limit app consent to the minimum scopes required for the business task.

Practitioner Guidance

Governance implication: Treat Microsoft OAuth app consent as an access-control decision, not a one-time setup step. Review who may approve permissions, which scopes are allowed, and whether third-party applications should be restricted by default.

What to watch for: Pay attention to unusually broad consent requests, unfamiliar enterprise apps, and token-enabled access to high-value resources. If an integration only needs a narrow capability, it should not be granted broad delegated permissions by convenience.

For deeper defensive guidance on token handling, client authentication, and sender-constrained OAuth deployments, the underlying standards are the RFC 6749: The OAuth 2.0 Authorization Framework and the RFC 9700: Best Current Practice for OAuth 2.0 Security.

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.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org