An Azure service that is used to provision Windows and Linux virtual machines.
Welcome to Microsoft Q&A!
Hello Karl,
You dont need to retore your image Your data, operating system, and applications are perfectly safe.
In Azure, the compute hardware (the VM size) and the storage (the OS disk) are decoupled. The "deprecation" and the HTTP 409 Conflict error you are seeing simply mean that Azure currently lacks the physical capacity to allocate your specific VM size (Standard_DC4s_v2) in your current availability zone.
When you resize the VM, Azure simply unplugs your existing, fully intact OS disk and attaches it to a newer, available physical server (such as Standard_DC4ads_v5 or Standard_D4s_v3). All your files remain exactly as they were the moment the VM was shut down.
Step 1: Resize the VM to bypass the 409 Error
Since the VM is already in a stopped (deallocated) state, it is in the perfect condition to be resized:
- Go to the Azure Portal and navigate to your AdAstra virtual machine.
- In the left-hand menu, under Settings, select Size.
- Search for and select the new size you want to use (such as Standard_DC4ads_v5 or Standard_D4s_v3).
- Click the Resize button at the bottom of the screen.
- Once the resize operation completes successfully, click Start on the VM overview page.
Step 2: Clear the Failed Extension
The root cause analysis noted a failed AmdGpuDriverWindows extension. The Standard_DC and Standard_D series do not have physical GPUs, so the extension is failing because it cannot find an AMD GPU to install drivers for.
Once the VM is running, you should remove this extension to clear the error state:
- On the VM page in the Azure Portal, go to Settings > Extensions + applications.
- Locate the AmdGpuDriverWindows extension.
- Select it and click Uninstall.
References:
Help make this community better for everyone: if this answer resolved your issue, please accept it or leave an upvote. If not, share more details in a comment so we can continue the discussion and find the right solution.