Forum Discussion

RalphCU's avatar
RalphCU
Copper Contributor
Aug 17, 2023

Azure Virtual Desktop deployment error: resource write operation failed to complete successfully

I have tried to deploy Azure Virtual Desktop several times and it has failed every time, with the same error message: "write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'."

    Details: "The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'. (Code: ResourceDeploymentFailure, Target: /subscriptions/b38d7f27-415a-4877-a594-ff5e4877c8d3/resourceGroups/AVD-Resource-Group-Prefix-deployment/providers/Microsoft.Resources/deployments/easy-button-inputvalidation-job-linked-template)" 

    I've tried using my work/Microsoft 365 Account, and using two different personal accounts, I thought the issue could be billing related, but even when there is $200 in available credit in a new/trial account, it still happens. 

    I've seen suggested elsewhere that this may be due to Azure Policy restrictions, but there are none, at least no non-default policies, and if the default policies restrict creation of Azure Virtual Desktop environments, that should be changed, and at minimum, users/admins should be informed if that is what is preventing them from being deployed, and be given the option to change them.

   The bottom line is that this is absurd that Azure Virtual Desktop fails by default for multiple accounts, and it needs to be fixed, even if my personal deployment issue can be resolved by jumping through hoops. Please, let me know what hoops I need to jump through to get this to work for now.

6 Replies

  • superbox1's avatar
    superbox1
    Copper Contributor
    Was there any resolution to this? Running into the same thing.
  • ML-nl's avatar
    ML-nl
    Copper Contributor

    Have the same issue, since this month.

    If I enable the bood diagnostics (normaly I have this disabled), i see a windows 11 deployment wizard, that asks to select Country, Language en keyboard layout. Normaly this should be covered with the sysprep process right ?

     


    I am just using the same steps as normal, jus selecting the last image from the MS store, install apps, sysprep, create image, deploy image.
    Must be something changed I believe..... but how to fix ?

     

    Edit:
    Just tried with an older image provided by Microsoft (normaly i would take the latest image), but this one also gives the same error. Hope this can be fixed..

    • garlandtech's avatar
      garlandtech
      Copper Contributor
      I'm having this issue today. The image is getting stuck at the country/language/keyboard screen.

      Is there any fix? I'm running out of time to get his deployed!
      Thanks
      • neilgreene's avatar
        neilgreene
        Copper Contributor
        Same problem. Typical Microsoft stuff. Some generic error message that is worthless. Has us all thinking it is permissions, then billing, then some other configuration. Heck, I will deploy a Windows XP environment. Then I though it was because I was selecting to deploy 2 clients. Regardless, I can't deploy. Going to AWS Workspace instead.
  • Hello Ralph. Let's go the basics. Has the Microsoft.DesktopVirtualization resource provider been enabled on the Subscription?
    Are the Required UrL's filtered or restricted by any firewall? Check those and then try the deployment again.

Resources