From the on-premises Active Directory domain, you assign User2 the Allow logon locally user right. You instruct User2 to sign in as user2@fabrikam.com. Does this meet the goal?

Last Updated on November 5, 2021 by Admin 3

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.

After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

Your network contains an on-premises Active Directory domain named contoso.com. The domain contains the users shown in the following table.

MS-100 Microsoft 365 Identity and Services Part 06 Q04 035
MS-100 Microsoft 365 Identity and Services Part 06 Q04 035

The domain syncs to an Azure Active Directory (Azure AD) tenant named contoso.com as shown in the exhibit.

MS-100 Microsoft 365 Identity and Services Part 06 Q04 036
MS-100 Microsoft 365 Identity and Services Part 06 Q04 036

User2 fails to authenticate to Azure AD when signing in as user2@fabrikam.com.

You need to ensure that User2 can access the resources in Azure AD.

Solution: From the on-premises Active Directory domain, you assign User2 the Allow logon locally user right. You instruct User2 to sign in as user2@fabrikam.com.

Does this meet the goal?

  • Yes
  • No
Explanation: 
This is not a permissions issue.
The on-premises Active Directory domain is named contoso.com. To enable users to sign on using a different UPN (different domain), you need to add the domain to Microsoft 365 as a custom domain.
0 0 votes
Article Rating
Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments