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 Case#2606170040009471, I am getting no responses I Was advised numerous times in my private messages over the past 8-9 business days that They were waiting for AFEC approval and that people were OOF and there has been follow up after follow up but my representative has no longer responded and I have no timelines on when I will hear back. I can't have this case fall by the wayside with my VM stuck and unable to access it. So I am merely posting this hoping to get it on someones radar so I can get some assistance and maybe a timeline to advise my customers. I normally get a follow up between 12-1PM EST on the days someone talks to me but today I am still in the dark with no timelines.

All of the original posts and conversations prior to this being made a case # can be found here:

https://learn.microsoft.com/en-us/answers/questions/5922975/i-have-a-vm-(d2d-ubuntu1404)-in-resource-group-d2d?source=docs

Prasad Chaganti 775 Reputation points Microsoft External Staff Moderator

2026-06-29T21:18:53.41+00:00

Hi TRANSPORTCORP,

Good day!

Thank you for sharing the case number you created. I reviewed the case details, and it appears the team has been coordinating with the backend team and is currently working with the CRP team to register an AFEC for your subscription. This will enable access to VMs that are using unmanaged disks.

I am following up with the case owner and the backend team to ensure a quicker resolution. Once I receive more information from them, I will update you accordingly.
TRANSPORTCORP 0 Reputation points

2026-06-29T21:25:39.1933333+00:00

Hey Prasad, I truly appreciate the response and the information you provided. I have been in the dark for some time and any information or communication really goes a long way! I'm losing customers by the day as I can't spin this thing up. Hope to hear back from you soon and thanks again.
Prasad Chaganti 775 Reputation points Microsoft External Staff Moderator

2026-06-30T20:49:44.18+00:00

Hi TRANSPORTCORP,

Hemalatha shared an update that the PG team removed the extension from the backend. She has already updated you and mentioned that you are unable to start the VM. Please share the error details in private message for further troubleshooting.
Prasad Chaganti 775 Reputation points Microsoft External Staff Moderator

2026-06-30T23:37:37.5633333+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:41:20.02+00:00

Hi TRANSPORTCORP,

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

Thank you.

3 answers

Your answer

Prasad Chaganti 775 Reputation points Microsoft External Staff Moderator

2026-06-29T21:18:53.41+00:00

Hi TRANSPORTCORP,

Good day!

Thank you for sharing the case number you created. I reviewed the case details, and it appears the team has been coordinating with the backend team and is currently working with the CRP team to register an AFEC for your subscription. This will enable access to VMs that are using unmanaged disks.

I am following up with the case owner and the backend team to ensure a quicker resolution. Once I receive more information from them, I will update you accordingly.
TRANSPORTCORP 0 Reputation points

2026-06-29T21:25:39.1933333+00:00

Hey Prasad, I truly appreciate the response and the information you provided. I have been in the dark for some time and any information or communication really goes a long way! I'm losing customers by the day as I can't spin this thing up. Hope to hear back from you soon and thanks again.
Prasad Chaganti 775 Reputation points Microsoft External Staff Moderator

2026-06-30T20:49:44.18+00:00

Hi TRANSPORTCORP,

Hemalatha shared an update that the PG team removed the extension from the backend. She has already updated you and mentioned that you are unable to start the VM. Please share the error details in private message for further troubleshooting.
Prasad Chaganti 775 Reputation points Microsoft External Staff Moderator

2026-06-30T23:37:37.5633333+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:41:20.02+00:00

Hi TRANSPORTCORP,

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

Thank you.

Answer 1

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Answer 2

I was asked in follow up by the agent

Hemalatha

Microsoft External Staff

In the meantime, I wanted to confirm one point from the Microsoft documentation, which states:

"If there is an error during migration, or if a VM is in a failed state because of issues in a previous migration, run the ConvertTo-AzVMManagedDisk cmdlet again. A simple retry usually unblocks the situation."

https://learn.microsoft.com/en-us/azure/virtual-machines/windows/convert-unmanaged-to-managed-disks#troubleshooting

Could you please confirm whether you have already retried running the ConvertTo-AzVMManagedDisk cmdlet? If so, could you also let me know the outcome or share any error message you received?

Thank you.

MY Response to this is:

When I run the...

ConvertTo-AzVMManagedDisk cmdlet

Here is my output,

PS /home/transportcorp> Stop-AzVM -ResourceGroupName "d2d_mcit" -Name "d2d-ubuntu1404" -Force

OperationId : 8c35a0a9-bc52-481c-a9f7-cd3685b8c59d

Status : Succeeded

StartTime : 6/29/2026 10:14:17 PM

EndTime : 6/29/2026 10:14:28 PM

Error :

PS /home/transportcorp> ConvertTo-AzVMManagedDisk -ResourceGroupName "d2d_mcit" -VMName "d2d-ubuntu1404"

ConvertTo-AzVMManagedDisk: Operation 'convertToManagedDisks' is not allowed on VM 'd2d-ubuntu1404' since VM has extension 'enablevmaccess' in failed state.

ErrorCode: OperationNotAllowed

ErrorMessage: Operation 'convertToManagedDisks' is not allowed on VM 'd2d-ubuntu1404' since VM has extension 'enablevmaccess' in failed state.

ErrorTarget:

StatusCode: 409

ReasonPhrase:

OperationID : 8d49afe4-7091-4fd0-bd87-e6c7ebf07e97

PS /home/transportcorp>

Yes, I can confirm that I retried the ConvertTo-AzVMManagedDisk cmdlet.

The VM stopped and deallocated successfully this time, but the conversion still failed. It looks like the operation is being blocked because a VM extension (enablevmaccess) is in a failed provisioning state.

Above is the exact output and error message from my retry:

It appears Azure prevents structural changes to a VM if an extension is in a failed state. The error seems to be happening because Azure enforces a "Succeeded" state on the VM and all its components before allowing major infrastructure changes. The enablevmaccess extension is either hung or failed. Please remove the extension or re-apply it to clear the failed state.

Thank you

Answer 3

The VM is blocked because the Linux VM Agent is failing to process extensions, leaving a failed extension that prevents normal operations. This behavior is consistent with known issues in specific Azure Linux Agent versions.

To remove the failed extension and unblock the VM, use one of the following approaches, depending on what is failing in your scenario.

Check and manage extensions via Azure CLI
Run these commands from a machine that has Azure CLI installed and is authenticated to the subscription:
```
   # List all extensions on the VM
   az vm extension list --vm-name d2d-ubuntu1404 -g D2D_MCIT
   
   # Remove the failed extension (replace <extension name> with the Name from the list output)
   az vm extension delete --vm-name d2d-ubuntu1404 -g D2D_MCIT --name <extension name>
```
This removes the extension definition from the VM model and is the supported way to get rid of a failed extension that is blocking operations.
If the Linux VM Agent is stuck processing extensions (known downgrade issue)
On affected Linux VMs (agent versions 2.2.21–2.2.24), extension processing can stop and block dependent services such as Backup and Site Recovery. In that case:
- Connect to the VM console or SSH (if still possible).
- Remove all manifest files used by the agent to track extensions:
```
     sudo rm /var/lib/waagent/*.manifest.xml
```
- After removing these files, retry the Azure operation (Start, Redeploy, Backup, Restore point, or extension update) from the Azure portal or CLI.
If the issue started after an Azure Linux Agent update (2.2.19 status reporting issue)
For VMs where extension status is not reported after an agent update to 2.2.19, Azure may automatically install an extra extension:
- Publisher: Microsoft.CPlat.Core
- Type: RunCommandLinux
If this extension itself is failed or no longer needed, remove it with the same CLI command as above:
```
   az vm extension delete --vm-name d2d-ubuntu1404 -g D2D_MCIT --name RunCommandLinux
```

After removing the failed extension and cleaning up the agent manifests (if applicable), retry the blocked VM operation (Start, Redeploy, Backup, or restore point creation). If operations remain blocked, rerun the VM assist tool for Linux to diagnose remaining agent/extension issues:

VM assist for Linux

References: