Failure when creating WVD Hostpool

Copper Contributor

Hi,

 

I am constantly getting this error when creating a WVD Hostpool even though it validates successfully before giving the option to create and then fails in the "CT-WVD-vmCreation-linkedTemplate" with conflict status.

 

Error in "rds.wvd-provision-host-pool-20200424165228 | Overview" screen is:

 

{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"Conflict","message":"{\r\n \"status\": \"Failed\",\r\n \"error\": {\r\n \"code\": \"ResourceDeploymentFailure\",\r\n \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\",\r\n \"details\": [\r\n {\r\n \"code\": \"DeploymentFailed\",\r\n \"message\": \"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.\",\r\n \"details\": [\r\n {\r\n \"code\": \"BadRequest\",\r\n \"message\": \"{\\r\\n \\\"error\\\": {\\r\\n \\\"code\\\": \\\"InvalidParameter\\\",\\r\\n \\\"message\\\": \\\"The Admin Username specified is not allowed.\\\",\\r\\n \\\"target\\\": \\\"adminUsername\\\"\\r\\n }\\r\\n}\"\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n}"}]}
 
 
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"BadRequest","message":"{\r\n \"error\": {\r\n \"code\": \"InvalidParameter\",\r\n \"message\": \"The Admin Username specified is not allowed.\",\r\n \"target\": \"adminUsername\"\r\n }\r\n}"}]}
 
Could you please help this issue?
2 Replies

@Cloudscape Is this through the portal or via an ARM template?

 

I think it's telling you that the admin user you specified for the session host is invalid.  If you're using an ARM Template, look to see what "adminUsername" is set to.  That parameter is usually derived from "exisitingDomainUPN", so see what that value is, and if it's correct.

 

If you're doing this from the portal, then when you get to the "Virtual machine settings" page, make certain you're providing a good "AD Domain Join UPN".  One gotcha is that for us, the UPN is the email address, so our UPN would look like "MyServiceAccount@mycompany.com".  If you have doubts, just go to Azure Active Directory in your subscription and search for the user.  Make certain what's listed as "User name" is what you're providing, *not* the "Name" value.  It's important to remember that, from an AAD perspective, "Name" and "User name" are two different things.

 

Hope this helps.

@FortyMegabytes 

 

I am following the tutorials in this Microsoft guide.

https://docs.microsoft.com/en-us/azure/virtual-desktop/tenant-setup-azure-active-directory

 

All steps are completed using the Azure Portal or Powershell as in the tutorials.

 

I can see this may be a permissions issue but even when speaking to Microsoft support they are unable to assist and advise to raise a new conversation on here to get it resolved.

 

I am using the full email address and not just the name.

The user is a global admin, service pricipal and tenant creator.

 

So unsure what you asking me to check and try?