You configure Azure AD Connect for Azure Active Directory Seamless Single Sign-On (Azure AD Seamless SSO) for an on-premises network. Users report that when they attempt to access myapps.microsoft.com

Question

Options

• AFrom the on-premises network, deploy Active Directory Federation Services (AD FS).
• BFrom Azure AD, add and verify a custom domain name.
• CFrom the on-premises network, request a new certificate that contains the Active Directory
• DFrom the server that runs Azure AD Connect, modify the filtering options.

• A
  16% (3)
• B
  74% (14)
• C
  5% (1)
• D
  5% (1)

Explanation

Azure AD Connect lists the UPN suffixes that are defined for the domains and tries to match them custom domain in Azure AD. Then it helps you with the appropriate action that needs to be taken. The Azure AD sign-in page lists the UPN suffixes that are defined for on-premises Active Directory and displays the corresponding status against each suffix. The status values can be one of the following: State: Verified Azure AD Connect found a matching verified domain in Azure AD. All users for this domain can sign in by using their on-premises credentials. State: Not verified Azure AD Connect found a matching custom domain in Azure AD, but it isn't verified. The UPN suffix of the users of this domain will be changed to the default .onmicrosoft.com suffix after synchronization if the domain isn't verified. Action Required: Verify the custom domain in Azure AD.

No community discussion yet for this question.