2.3.3. Single Sign-On (SSO)
💡 First Principle: Single Sign-On lets a user authenticate once to their identity provider and then access multiple applications without re-entering credentials. The identity provider issues a token; applications trust that token instead of asking the user to log in again. SSO reduces friction, reduces password fatigue, and centralizes authentication control.
Without SSO, every application has its own login. Users manage 10-20 separate passwords, forget them, reuse them across services (a major security risk), and waste time on authentication. With SSO, users sign in once to Entra ID and get seamless access to all connected apps.
How it works technically:
SSO in Microsoft 365 uses two main protocols:
- SAML 2.0: XML-based, widely used for enterprise apps (Salesforce, ServiceNow, older SaaS)
- OpenID Connect (OIDC): JSON/REST-based, modern standard used by most new cloud apps
Silent sign-in on managed devices: on Windows 10/11 devices that are Entra joined, hybrid joined or registered, SSO comes from the device's Primary Refresh Token (PRT), obtained at Windows sign-in and used to get tokens for browser and Office apps without prompts. Seamless SSO does the same for domain-joined PCs on the corporate network using Kerberos (mainly older Windows versions; it is free and works with password hash sync or pass-through authentication). Both are opportunistic: if the PRT or Seamless SSO isn't working on the device, the user falls back to typing a password. In the browser, the Entra session (kept across restarts by "Stay signed in") is what lets one sign-in cover the next app.
💡 Key Point: SSO doesn't just improve user experience — it improves security. When all authentications flow through Entra ID, Conditional Access policies apply universally, MFA is enforced centrally, and every sign-in is logged in one place. Fragmented authentication means fragmented security.
Containing a compromised account or session: because every connected app trusts tokens from Entra ID, containment happens once in Entra ID, not app by app. Revoke sessions on the user (Entra admin center, or Revoke-MgUserSignInSession in Microsoft Graph PowerShell) invalidates the user's refresh tokens and browser session cookies, so no connected app can obtain new tokens without a fresh sign-in; also disable the account or reset its Entra password if the credentials themselves are compromised. Access tokens already issued stay valid until they expire (about an hour by default) unless the app supports Continuous Access Evaluation.
⚠️ Exam Trap: SSO does not mean users have only one password. Some users may still have separate local passwords for non-SSO applications. SSO means one authentication session — users authenticate once to Entra ID and get tokens for SSO-enabled apps. Non-SSO apps require separate login.
Reflection Question: After implementing SSO for all cloud apps, a user reports they still have to log in to one legacy web application every day. What is the most likely explanation?