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(92.8, 14.000000000000002%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETP%3C/text%3E%3C/svg%3E)
When setting up AzureVirtualDesktop the error
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"VMExtensionProvisioningError","message":"VM has reported a failure when processing extension 'Microsoft.Compute.CustomScriptExtension'. Error message: "Failed to download all specified files. Exiting. Error Message: CustomScript failed to download the blob fileUri_{2} because it does not exist. Please create the blob and try again, the response code and message returned were: "The remote server returned an error: (404) Not Found. The specified blob does not exist." (Service request ID = 8d5c959a-301e-0004-66cd-a312ea000000)"\r\n\r\nMore information on troubleshooting is available at https://aka.ms/VMExtensionCSEWindowsTroubleshoot "},{"code":"VMExtensionProvisioningError","message":"VM has reported a failure when processing extension 'Microsoft.Compute.CustomScriptExtension'. Error message: "Failed to download all specified files. Exiting. Error Message: CustomScript failed to download the blob fileUri_{2} because it does not exist. Please create the blob and try again, the response code and message returned were: "The remote server returned an error: (404) Not Found. The specified blob does not exist." (Service request ID = d6225d60-e01e-0081-54cd-a33f37000000)"\r\n\r\nMore information on troubleshooting is available at https://aka.ms/VMExtensionCSEWindowsTroubleshoot "}]}
is given. When looking at the template provided by Azure it seems the custom script extension field is automatically added. It seems this is done on the Azure side, and can not be edited even with escalated permissions within the Azure environment.
AVD itself deploys CSE's as per design. We are facing multiple deployment failures due to the same issue.
Extension named easy-button-avdsetup-linked-template is failing.
Would this prevent the VM's from being fully deployed preventing login? Yes that is the exact step that keeps failing.
easy-button-avdsetup-linked-template is exactly what fails each time we run the setup.
Would this prevent the VM's from being fully deployed preventing login?
Not sure, I'll update here in some more time. However we have created Sev-A ticket with support to check on.
I found others have reported the same issue on Jun 15th as well.
https://learn.microsoft.com/en-us/answers/questions/1306263/azure-virtual-desktop-deployment-error-vmextension
Also referring to this doc, I feel it can be ignored but still not sure.
https://learn.microsoft.com/en-us/azure/virtual-desktop/troubleshoot-getting-started
Hello Travis Powell
Welcome to Microsoft Q&A Platform, thanks for posting your query here.
Did you specify a custom script during deployment?
If yes, can you verify that the URI which contains your custom script is accessible?
If you didn’t specify a script and the deployment is failing via getting started wizard, request you to please open a support case logged to investigate this.
I have never specified a custom script during deployment, which was the whole point of this form post, I already had a support ticket open for this issue, but I got an email saying they just closed the support ticket.
We have a premier case with MS with TrackingID#2306210030004915 on Sev-A. MS is unable to get an available engineer since yesterday. Keeping aside the resolution they are still not able to answer the impact of extension failure.
It's Azure End issue, we worked with Azure PG & got it fixed.
We have encountered the same issue, created premier Sev-A ticket, had to chase support folks for 6 days to work with Azure PG team to get this issue fixed, we had a successful deployment after that.
Very pathetic experience 😒
The deployment worked as planned. But for some reason even the test user, and other users are not able to login to the remote desktop...
Not sure, might be some misconfiguration issue, cross verify the config again. However we will get to know in our env if this issue is from MS end.
It doesn't look like the host pool VM's actually joined the domain.