Soru

Zorluk: OrtaMulti-tenant Applications Configuration

An independent software vendor (ISV) is registering a new multi-tenant line-of-business application in Microsoft Entra ID. The application is designed to allow employees from any enterprise customer to log in with their work credentials, but it must reject sign-in attempts from personal Microsoft accounts.

Which configuration should the developer apply to the application manifest and the application's authentication endpoint?

  1. Set `signInAudience` to `AzureADMultipleOrgs` and use the `/organizations` authority endpoint.Cevap
  2. B
    Set `signInAudience` to `AzureADandPersonalMicrosoftAccount` and use the `/common` authority endpoint.
  3. C
    Set `signInAudience` to `AzureADMultipleOrgs` and use the `/common` authority endpoint.
  4. D
    Set `signInAudience` to `AzureADMyOrg` and use the `/organizations` authority endpoint.

Cevap

Set the signInAudience to AzureADMultipleOrgs and use the /organizations authority endpoint.
Setting the signInAudience to AzureADMultipleOrgs restricts sign-ins to work or school accounts. Using the /organizations authority endpoint enforces this constraint at the Entra ID sign-in screen, ensuring personal accounts cannot log in.

Adım Adım Çözüm

1
Evaluate the required sign-in audience scope.
Determine that `AzureADMultipleOrgs` is required to allow users from any enterprise directory while excluding personal Microsoft accounts.
Choosing `AzureADMyOrg` would limit authentication to a single tenant, whereas `AzureADandPersonalMicrosoftAccount` would allow personal accounts.
2
Determine the optimal authority endpoint.
Select the `/organizations` endpoint instead of `/common`.
The `/organizations` endpoint restricts access to organizational accounts directly at the authentication gate, avoiding user confusion by not allowing personal accounts to enter credentials.

Anahtar Kavram

Microsoft Entra ID Multi-tenant Sign-in Audience and Endpoint Filtering
Tahmini Süre:1m 30s
Bu soruyu puanla