A Windows VM created by an independent standard-pool script is domain joined and can reach required endpoints, but it never appears in the target host pool. The registration token used by the script expired yesterday. What should be corrected?

✓ Correct answer

• Use a valid token from the target pool and complete the AVD Agent and Agent Boot Loader registration workflow.

For independently provisioned standard hosts, use the correct unexpired pool token with the AVD registration components, then verify host health. Option explanations: A. Install only AMA and wait for the VM to become an AVD host.: AMA collects guest telemetry and is not the AVD registration agent. B. Use a valid token from the target pool and complete the AVD Agent and Agent Boot Loader registration workflow.: An expired token cannot authorize the host registration; the agent workflow must succeed. C. Raise the maximum session limit before registering the host.: Capacity settings do not repair token validity or agent registration. D. Give the registration token to the end user to subscribe to the workspace.: The token is for hosts, not user feed subscription, and must remain secret. Sources: Deploy Azure Virtual Desktop — https://learn.microsoft.com/en-us/azure/virtual-desktop/deploy-azure-virtual-desktop

Read the source reference