It isn't required for direct user sign-ins. This prerequisite is applicable only when you enable the Seamless SSO feature. If URL-based proxy exceptions aren't possible in your organization, you can instead allow access to the Azure datacenter IP ranges, which are updated weekly. If you require a specific URL instead of a wildcard for proxy configuration, you can configure, where tenantid is the GUID of the tenant for which you're configuring the feature. If your firewall or proxy allows, add the connections to your allowlist for *. URLs over port 443. You use Azure AD Connect version 1.1.644.0 or later. If you use password hash synchronization as your sign-in method and there's a firewall between Azure AD Connect and Azure AD, ensure that: Set up your Azure AD Connect server: If you use pass-through authentication as your sign-in method, no other prerequisite check is required. To deploy Seamless SSO for Azure AD by using Azure AD Connect, complete the steps that are described in the following sections.Įnsure that the following prerequisites are in place:
Seamless SSO provides your users with easy access to your cloud-based applications without using any other on-premises components. Azure Active Directory (Azure AD) Seamless single sign-on (Seamless SSO) automatically signs in users when they're using their corporate desktops that are connected to your corporate network.
0 kommentar(er)
