I have a VM (d2d-ubuntu1404) in resource group D2D_MCIT that is blocked from all operations. I need to remove the failed extension.

Question

I have a VM (d2d-ubuntu1404) in resource group D2D_MCIT that is blocked from all operations. I need to remove the failed extension.

TRANSPORTCORP 0

I have a VM (d2d-ubuntu1404) in resource group D2D_MCIT that is blocked from all operations.

- VM uses unmanaged disks (now retired)

- VM cannot start due to platform restriction

- VM cannot be converted because an extension (enablevmaccess) is in failed state

- Extension cannot be removed because VM is not running

- Resource update is blocked due to unmanaged disk policy

This has created a circular dependency deadlock.

Please remove the failed extension (enablevmaccess) from the backend so I can proceed with my managed disk migration.

Hemalatha 14,620 Reputation points Microsoft External Staff Moderator

2026-06-17T18:07:45.66+00:00

Hello,

Thank you for reaching out and for providing the detailed information.

From the information shared, we understand that the VM d2d-ubuntu1404 is currently unable to proceed with the managed disk migration due to a failed enablevmaccess extension, while extension management operations are also blocked because the VM cannot be started. We understand how this creates a dependency situation that prevents further progress.

We are currently reviewing the VM and extension state to validate the behavior and determine the available recovery options. If we confirm that the failed extension cannot be removed through standard management operations, we will engage the appropriate Azure engineering team for further investigation and assistance.

To help us proceed, share any recent error messages received during the extension removal or migration attempts.

Could you please check the private message and provide necessary details:

We appreciate your patience while we investigate this further and will keep you updated on the next steps.

4 answers

Your answer

Hemalatha 14,620 Reputation points Microsoft External Staff Moderator

2026-06-17T18:07:45.66+00:00

Hello,

Thank you for reaching out and for providing the detailed information.

From the information shared, we understand that the VM d2d-ubuntu1404 is currently unable to proceed with the managed disk migration due to a failed enablevmaccess extension, while extension management operations are also blocked because the VM cannot be started. We understand how this creates a dependency situation that prevents further progress.

We are currently reviewing the VM and extension state to validate the behavior and determine the available recovery options. If we confirm that the failed extension cannot be removed through standard management operations, we will engage the appropriate Azure engineering team for further investigation and assistance.

To help us proceed, share any recent error messages received during the extension removal or migration attempts.

Could you please check the private message and provide necessary details:

We appreciate your patience while we investigate this further and will keep you updated on the next steps.

Answer 1

TRANSPORTCORP 0

Hey!

I'm stuck and its been 7 business days and I just need to be allowed access to my server to make the changes requested regarding the unsupported extension. It's stuck in a state where I cant migrate it or access it. I have spoken to some nice support agents but no one is able to get me anywhere I just keep hearing my request is being followed up again for approval. I've attempted to be extremely patient and professional but I don't know what else to do. Any suggestions?!? I can't sit in uncertainty for weeks on end. I don't want to play the money card, but we've spent over 100k in the last 8 years here on Azure on VMs and I can't get help for 1 thing in 8 years inside of a week and a half? Can someone please assist with this Case#2606170040009471 I would be extremely grateful for any help I can get.

Prasad Chaganti 775 Reputation points Microsoft External Staff Moderator

2026-07-01T17:57:23.4+00:00
Hi TRANSPORTCORP,

Backend team successfully removed the extension from backend. As you mentioned before VM was unable to start so please try the below steps:

We recommend initially attempting to reapply the configuration and redeploy the VM. This step often resolves transient platform or provisioning-related issues.

If the issue persists, please proceed with the following recovery steps:

Create a snapshot of the OS disk of the affected (faulty) VM.

Create a new managed disk from the snapshot.

Provision a new VM using the newly created disk.

Attempt to log in to the newly created VM to verify accessibility and OS health.

Please feel free to let me know if you have any queries.
Prasad Chaganti 775 Reputation points Microsoft External Staff Moderator

2026-07-01T22:40:36.74+00:00

Hi TRANSPORTCORP,

Just checking in to see if you had a chance to see my previous answer. Please let me know if it was helpful and don't hesitate to reach out to us if you face any issue.

Thank you.
TRANSPORTCORP 0 Reputation points

2026-07-01T22:43:00.7466667+00:00

We have been working since your first comment to try and recreate our VM. Its been awesome

Answer 2

TRANSPORTCORP 0

Remove-AzVMExtension: Cannot modify extensions in the VM when the VM is not running.

0 comments

Answer 3

TRANSPORTCORP 0

PS /home/transportcorp> Remove-AzVMExtension -ResourceGroupName d2d_mcit -VMName d2d-ubuntu1404 -Name "enablevmaccess" -Force

Remove-AzVMExtension: Cannot modify extensions in the VM when the VM is not running.

ErrorCode: OperationNotAllowed

ErrorMessage: Cannot modify extensions in the VM when the VM is not running.

ErrorTarget:

StatusCode: 409

ReasonPhrase:

OperationID : d4e48c76-500f-4d10-985a-97fbd5c2c35e

0 comments

Answer 4

Backend removal of the failed enablevmaccess extension isn’t possible through self-service tools. However, there are a few supported options to break the deadlock and clear the failed extension state so that migration can proceed.

Verify the VM agent and extension state
- Use Azure CLI or PowerShell to confirm the extension status:
  - Azure CLI:
```
       az vm extension show -g D2D_MCIT --vm-name d2d-ubuntu1404 --name enablevmaccess
```
  - PowerShell:
```
       Get-AzVM -ResourceGroupName D2D_MCIT -Name d2d-ubuntu1404 -Status
```
- This confirms that the VM agent is reporting the extension in a failed state and that the VM is not running.
Trigger a new goal state (Reapply)
- Even when extensions are in a failed state, a VM Reapply can sometimes clear inconsistent extension metadata without requiring a full start:
  - Azure CLI:
```
       az vm reapply -g D2D_MCIT -n d2d-ubuntu1404
```
  - PowerShell:
```
       Set-AzVM -ResourceGroupName D2D_MCIT -Name d2d-ubuntu1404 -Reapply
```
- Reapply usually doesn’t reboot the VM, but in rare cases it might trigger a pending update that requires a restart. Run this at a time when a short downtime is acceptable.
- After reapply completes, re-check the extension state as in step 1. If the extension moves out of the failed state, retry the managed disk migration or conversion.
Remove the extension when possible
- If at any point the platform allows extension modification (for example, after a successful reapply or partial start), remove the enablevmaccess extension:
  - PowerShell:
```
       Remove-AzVMExtension -ResourceGroupName D2D_MCIT -VMName d2d-ubuntu1404 -Name "enablevmaccess"
```
- Once removed, rerun the migration or template that performs the managed disk conversion.
Check extension logs if the VM becomes startable
- If the VM can be started even briefly, inspect the extension and agent logs inside the guest to ensure there are no residual issues:
  - Linux extension logs: /var/log/azure/
  - Extension settings/status: /var/lib/waagent/
- For Windows VMs (for reference in similar cases):
  - Logs: C:\WindowsAzure\Logs\Plugins and C:\WindowsAzure\Logs\WaAppAgent\
  - Settings/status: C:\Packages\Plugins
When the VM remains blocked for all operations
- If the VM cannot be started, re-applied, or modified due to platform restrictions and unmanaged disk policy, the remaining option is a platform-side fix.
- In that case, open an Azure support ticket and clearly state:
  - The VM name and resource group.
  - That the VM uses unmanaged disks and is blocked from start/convert operations.
  - That enablevmaccess is in a failed state and cannot be removed because the VM is not running.
  - That resource updates are blocked by the unmanaged disk policy, creating a circular dependency.
- Support can then adjust the VM model or extension state from the backend so the extension no longer blocks managed disk migration.

References: