@akhilesh Apologies for the delay on this. There could be following reasons for this error to occur while deployment. I would recommend checking these and ensuring it is correctly set up for you.
- This could happen if you are setting a new Vnet, which is not supported in WVD.
Select an existing Vnet, from ADDS service or from domain controller VM.
There are 2 ways:
a. A domain controller VM and then use Azure AD connect to sync with Azure Active Directory;
b. Create a Azure Active Directory Domain Services.
Regarding the second option, when you create a AADDS, Vnet will be created which is connected to your domain. Then you can use this Vnet in the host pool.
- The subnet and subscription should be in the same region while creating the host.
- Few customers shared that this can also happen if you created the Network and Subnet in the same browser session that you plan to use to create the Windows Virtual Desktop pool. Open a browser Incognito and attempt to create the WVD.
Please check the above and let me know if you are still seeing issues and I can troubleshoot further.
Please don’t forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.