A migration will introduce Entra-joined hosts alongside an existing AD DS-joined pool. An administrator proposes registering both join types in that same pool and letting the broker select either. What should the migration design do?

✓ Correct answer

• Create a separate host pool for the Entra-joined hosts.

Keep a homogeneous join type within a host pool. A separate pool lets the migration apply the appropriate identity, SSO, and Windows sign-in prerequisites without mixing supported join scenarios. Option explanations: A. Mix the join types after making their hostnames follow the same naming pattern.: Naming conventions do not change the host's join type or authentication requirements. B. Create a separate host pool for the Entra-joined hosts.: A separate pool preserves the required consistent join type and supports deliberate migration. C. Mix the join types after granting every user local administrator rights.: Local administrator membership does not make a mixed-join host pool a supported design. D. Register the new hosts in the existing pool and rely on workspace registration to normalize authentication.: Workspace registration publishes resources; it does not normalize the underlying join types. Sources: Microsoft Entra joined session hosts in Azure Virtual Desktop — https://learn.microsoft.com/en-us/azure/virtual-desktop/azure-ad-joined-session-hosts; Prerequisites for Azure Virtual Desktop — https://learn.microsoft.com/en-us/azure/virtual-desktop/prerequisites

Read the source reference