Single sign-on (SSO) lets users sign in to several applications with one identity. This applies to the applications that are assigned to them and configured for SSO. Each application is set up and tested individually.
Choose the protocol per application
Microsoft Entra supports federated SSO with SAML and OpenID Connect, among others, as well as other patterns for specific applications. OAuth 2.0 is an authorisation framework; OpenID Connect adds authentication to it. Check which protocols and claims each application actually supports. The Entra gallery contains thousands of pre-integrated apps, but configuration and testing are still required.
Keep SSO and the user lifecycle separate
SSO handles authentication. Provisioning and deprovisioning must be set up separately, for example through SCIM or app-specific connectors. Disabling the identity account does not necessarily end existing application sessions immediately. Plan token and session policies as well as controlled sign-in logs with suitable licensing and retention.
Pilot critical apps with test accounts and check role assignment, emergency access and offboarding through to the actual block in the target system.
Sources: SSO in Entra ID · Entra application gallery · Plan Application Proxy

