This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(204.8, 33%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMW%3C/text%3E%3C/svg%3E)
I have attempted to deploy an AVD server via QuickStart numerous times only for the process to fail at this step:
We setup an AD server in our tenant that is sync'd with our on-prem AD. Per Microsoft's advice here I removed the Microsoft.Powershell.DSC extension from the server in Azure and began another QuickStart session only to have the same problem. I am using an account with Global Admin, Owner, Virtual Machine Contributor, and User Access Administrator roles set on it. It is also a Domain Admin account with no MFA requirement.
What else should I be looking at? How do I remedy this problem?
Thanks,
Matt
Hi @Matt W
When you check the deployment failure logs do you see the below error?
{
"status": "Failed",
"error": {
"code": "VMExtensionProvisioningError",
"message": "VM has reported a failure when processing extension 'Microsoft.Powershell.DSC'. Error message: \"DSC Configuration 'AddADDSUser' completed with error(s). Following are the first few: Logon failure: the user has not been granted the requested logon type at this computer The SendConfigurationApply function did not succeed.\"\r\n\r\nMore information on troubleshooting is available at https://aka.ms/VMExtensionDSCWindowsTroubleshoot "
}
A few things to check here:
Is the new VM acting as a DC in Azure fully synchronized with the other DCs running on premises?
Is this a full DC or just an RODC?
If it is an RODC, and there is no access to the on-premises DCs, this error might be expected.
Does the VM successfully join the domain?
If not, you need to check, if e.g. the DNS resolution isn't working correctly or the DNS setting on the VNET/Subnet doesn't have the DC IP address listed as DNS
If yes, you might want to try to log on to the VM manually via MSTSC and check if you can add users to the Remote Desktop Users group. If that fails, you need to investigate it from the AD side.
Also worth checking the GPO settings for the local security policy and the granted logon types for users that are applied to VMs when joined into the domain.
Prrudram, thank you for replying. I don't see that any VMs are even created. Are you telling me that at this phase of deployment I should see virtual machines? The DC is Azure is not RODC and is fully sync'd with our on-prem DC.
Also, I do see the error you posted. I don't see any VMs, hostpools, workspaces - nothing.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(243.2, 24%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMT%3C/text%3E%3C/svg%3E)
Could you check the deployment log for the resource group or subscription? Normally you would be able to find an error message that will make it easier for us to help you get it running.
Hi @Matt W
Thanks for the update. I don't have a way to check the logs on your subscription. This is something that the azure technical support team will be able to check using your subscription ID. I would recommend raising a support case for further investigation as it requires looking at the logs. If you don't have the ability to open a support ticket let me know.
@Matt W
I further researched on this, I believe, the user setup template creates the AVD test user account and group in Active Directory
One of the AVD experts from Microsoft Azure, describe the issue and a fix here
If I have answered your query, please click "Accept as answer" as a token of appreciation