Set up a trust by adding or converting a domain for single sign-on The federated domain was prepared for SSO according to the following Microsoft websites. (This doesn't include the default "" domain.) The federated domain is publicly resolvable by DNS. The federated domain is prepared correctly to support SSO as follows: For more info about how to troubleshoot common sign-in issues, see the following Microsoft Knowledge Base article:Ģ412085 You can't sign in to your organizational account such as Office 365, Azure, or Intune The user isn't experiencing a common sign-in issue. The UPN of the on-premises Active Directory user account and the cloud-based user ID must match.īefore you assume that a badly piloted SSO-enabled user ID is the cause of this issue, make sure that the following conditions are true: The Azure Active Directory Sync tool must sync the on-premises Active Directory user account to a cloud-based user ID. The user ID and the primary email address for the associated Microsoft Exchange Online mailbox do not share the same domain suffix. The on-premises Active Directory user account should use the federated domain name as the user principal name (UPN) suffix. The general requirements for piloting an SSO-enabled user ID are as follows: These symptoms may occur because of a badly piloted SSO-enabled user ID. Sorry, but we're having trouble signing you out
0 kommentar(er)
