Azure Active Directory Seamless Single Sign-On
What is Azure Active Directory Seamless Single Sign-On?
Azure Active Directory Seamless Single Sign-On (Azure AD Seamless SSO) automatically signs users in when they are on their corporate devices connected to your corporate network. When enabled, users don't need to type in their passwords to sign in to Azure AD, and usually, even type in their usernames. This feature provides your users easy access to your cloud-based applications without needing any additional on-premises components.
Seamless SSO can be combined with either the Password Hash Synchronization or Pass-through Authentication sign-in methods. Seamless SSO is not applicable to Active Directory Federation Services (ADFS).
Seamless SSO needs the user's device to be domain-joined, but doesn't need for the device to be Azure AD Joined.
- Great user experience
- Users are automatically signed into both on-premises and cloud-based applications.
- Users don't have to enter their passwords repeatedly.
- Easy to deploy & administer
- No additional components needed on-premises to make this work.
- Works with any method of cloud authentication - Password Hash Synchronization or Pass-through Authentication.
- Can be rolled out to some or all your users using Group Policy.
- Register non-Windows 10 devices with Azure AD without the need for any AD FS infrastructure. This capability needs you to use version 2.1 or later of the workplace-join client.
- Sign-in username can be either the on-premises default username (
userPrincipalName) or another attribute configured in Azure AD Connect (
Alternate ID). Both use cases work because Seamless SSO uses the
securityIdentifierclaim in the Kerberos ticket to look up the corresponding user object in Azure AD.
- Seamless SSO is an opportunistic feature. If it fails for any reason, the user sign-in experience goes back to its regular behavior - i.e, the user needs to enter their password on the sign-in page.
- If an application (for example, https://myapps.microsoft.com/contoso.com) forwards a
domain_hint(OpenID Connect) or
whr(SAML) parameter - identifying your tenant, or
login_hintparameter - identifying the user, in its Azure AD sign-in request, users are automatically signed in without them entering usernames or passwords.
- Users also get a silent sign-on experience if an application (for example, https://contoso.sharepoint.com) sends sign-in requests to Azure AD's tenanted endpoints - that is, https://login.microsoftonline.com/contoso.com/<..> or https://login.microsoftonline.com/<tenant_ID>/<..> - instead of Azure AD's common endpoint - that is, https://login.microsoftonline.com/common/<...>.
- Sign out is supported. This allows users to choose another Azure AD account to sign in with, instead of being automatically signed in using Seamless SSO automatically.
- Office 365 Win32 clients (Outlook, Word, Excel, and others) with versions 16.0.8730.xxxx and above are supported using a non-interactive flow. For OneDrive, you will have to activate the OneDrive silent config feature for a silent sign-on experience.
- It can be enabled via Azure AD Connect.
- It is a free feature, and you don't need any paid editions of Azure AD to use it.
- It is supported on web browser-based clients and Office clients that support modern authentication on platforms and browsers capable of Kerberos authentication:
|OS\Browser||Internet Explorer||Edge||Google Chrome||Mozilla Firefox||Safari|
|Mac OS X||N/A||N/A||Yes*||Yes*||Yes*|
*Requires additional configuration
For Windows 10, the recommendation is to use Azure AD Join for the optimal single sign-on experience with Azure AD.
- Quick Start - Get up and running Azure AD Seamless SSO.
- Deployment Plan - Step-by-step deployment plan.
- Technical Deep Dive - Understand how this feature works.
- Frequently Asked Questions - Answers to frequently asked questions.
- Troubleshoot - Learn how to resolve common issues with the feature.
- UserVoice - For filing new feature requests.