You are developing a multi-tenant web application that will be registered in Microsoft Entra ID. The application must allow authentication for users with work or school accounts from any Microsoft Entra ID tenant, as well as users with personal Microsoft accounts (such as Outlook.com or Xbox Live accounts).
Which two configurations must you implement in the application registration and code? (Select two.)
- Set the signInAudience property in the application manifest to AzureADandPersonalMicrosoftAccountAnswer
- BSet the signInAudience property in the application manifest to AzureADMultipleOrgs
- Configure the authority endpoint in the application code to use https://login.microsoftonline.com/common/v2.0Answer
- DConfigure the authority endpoint in the application code to use https://login.microsoftonline.com/organizations/v2.0
- ESet the signInAudience property in the application manifest to AzureADMyOrg
Answer
To support both work/school accounts from any Microsoft Entra ID tenant and personal Microsoft accounts, you must set the signInAudience property to AzureADandPersonalMicrosoftAccount in the application manifest, and configure the authority endpoint in your code to use the /common endpoint.
The correct configurations are to set the signInAudience property to AzureADandPersonalMicrosoftAccount in the application manifest and to use the common endpoint (/common) in the authority URL. The AzureADandPersonalMicrosoftAccount setting registers the application to accept work or school accounts from any corporate directory as well as personal Microsoft accounts. In the code, the /common endpoint acts as a multiplexer that resolves the user's home tenant type, routing both organizational users and personal account users to their respective login systems.
Step-by-Step Solution
Key Concept
Multi-tenant configuration in Microsoft Entra ID requires aligning the manifest's signInAudience with the correct authorization authority endpoint in the application code.
Estimated Time:1m 30s