Start VM on Connect / Service Principal Missing

If the Azure Virtual Desktop service principal is missing in your tenant after deploying host pools, it may be due to a few reasons. Here are some steps you can take to troubleshoot this issue:

1. Check Deployment Status: Ensure that the host pools were deployed successfully. Sometimes, issues during deployment can prevent the service principal from being created.
2. Role Assignment: Make sure you are trying to assign the Desktop Virtualization Power On Contributor role at the subscription level. If you assign this role at a lower level (like resource group or host pool), it may not work properly.
3. Service Principal Creation: The service principal should be created automatically when you set up Azure Virtual Desktop. If it's missing, you may need to check if there were any errors during the setup process.
4. Permissions: Verify that your Azure account has the necessary permissions to view and manage service principals. You might need to check with your Azure administrator if you lack the required access.
5. Azure Support: If the service principal is still missing after checking the above points, consider reaching out to Azure support for assistance. They can provide more specific guidance based on your tenant's configuration.

Make sure to follow the guidelines for assigning roles to the Azure Virtual Desktop service principal as outlined in the Azure documentation.

References:

• Assign Azure RBAC roles or Microsoft Entra roles to a service principal (avd-service-principal)
• Configure Start VM on Connect