How can we improve Azure Virtual Machines?

New SQL Server Resource Provider not idempotent?

It seems that the new Microsoft.SqlVirtualMachine/SqlVirtualMachines resource provider is not idempotent when deployed from an ARM template. Every first deployment succeeds and yields the expected results, but subsequent deployments time out on the Microsoft.SqlVirtualMachine/SqlVirtualMachines resource after > 2 hours.

Currently, the workaround is to move this resource to a separate template which is kicked off only once, but obviously that's not ideal. Am I missing something, or is this a bug and should the Microsoft.SqlVirtualMachine/SqlVirtualMachines be idempotent?

2 votes
Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)

We’ll send you updates on this idea

Annejan Barelds shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

1 comment

Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
Submitting...
  • David Bustos commented  ·   ·  Flag as inappropriate

    I'm seeing issues with it trying to create the storage pool again and failing saying storage the target disk is already in a storage pool... Is this your experience?

Feedback and Knowledge Base