[PLACEHOLDER] - Place a descriptive title here

Azure / avdaccelerator

AVD Accelerator deployment automation to simplify the setup of AVD (Azure Virtual Desktop) based on best practices

MIT License

324 stars 207 forks source link

[PLACEHOLDER] - Place a descriptive title here #519

Closed alpesh-exigotech closed 10 months ago

alpesh-exigotech commented 10 months ago

Hello there,

I am getting below error while creating resource group through Bicep script. How to resolve this error?

danycontre commented 10 months ago

@alpesh-exigotech thanks for reporting the issue.

The deployment that is failing for you is trying to grant AVD enterprise application access to your pool compute and service objects, this is used by the scaling plan and start VM on connect features.

Please make sure that your Microsoft Entra ID tenant has the following app ID:

Name: could be Azure Virtual Desktop or Windows Virtual Desktop
AppID: 9cdead84-a844-4324-93f2-b2e6bb768d07

If you don't have it on you Entra ID tenant, please check if the Microsoft.DesktopVirtualization resource provider has been registered in a subscription connected to the tenant.

alpesh-exigotech commented 10 months ago

Thank you @danycontre for your guidance. I found that Microsoft.DesktopVirtualization was not registered in my subscription.

After registering it I start getting below error with few successful resource deployments. Can you please let me know what I am missing here.

danycontre commented 10 months ago

@alpesh-exigotech please go inside the AVD-MGMT-Plane* deployment and share the details of the internal deployment that failed.

alpesh-exigotech commented 10 months ago

@danycontre

Are you referring this one ?

danycontre commented 10 months ago

@alpesh-exigotech checking if you are still having this issue?

Did you select a group to be granted access to AVD resources?

alpesh-exigotech commented 10 months ago

Hi @danycontre

Thanks for follow up. Yes, I selected group access and it's working. However, I am facing some issues with Private DNS, and I believe that's it related to open issue https://github.com/Azure/bicep/issues/9839 with this. Please correct me if I am referring to older or different issues. For now, I am closing this issue and will open another one for Private DNS.