The token lands in your hand. You need to prove who you are. MSA OpenID Connect (OIDC) makes that exchange clean, fast, and verifiable.
Microsoft Account (MSA) OpenID Connect is the modern standard for integrating Microsoft identity into your apps. Built on OAuth 2.0, OIDC adds a strong identity layer. It does more than delegate permissions — it verifies the user's identity directly from Microsoft’s trusted servers. This cuts out guesswork and reduces attack surface.
When you implement MSA OIDC, you start with the discovery document at https://login.microsoftonline.com/common/v2.0/.well-known/openid-configuration. This URL gives your application the endpoints, supported scopes, and keys it needs. From there, your app redirects the user to the Microsoft login, requesting scopes like openid, email, or profile.
After the user signs in, your app gets an ID token, usually in JWT format. This token contains claims about the user — their unique ID (sub), display name, email, and more. Verify the signature against Microsoft’s public keys. Validate the aud claim to ensure the token was meant for your app. Check expiration (exp) to prevent reuse.
Access tokens are separate from ID tokens. Use access tokens when calling Microsoft Graph or other protected APIs. OIDC keeps authentication and authorization clear, so your code handles each flow with precision.