An Azure service that is used to provision Windows and Linux virtual machines.
Gisli Þorvaldsson - Azure requires all VM extensions to be in a healthy Provisioning succeeded state before performing operations like converting unmanaged disks to managed disks. If any extension is Failed, Transitioning, or in an inconsistent backend state, Azure blocks the operation with the error:
Operation is not allowed since VM has an extension in failed state
This validation occurs at the Azure control plane, and the portal view may not always reflect the internal extension state accurately. Slow Azure VM Start operations when extensions are "Failed" - https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/slow-vm-start-extensions-troubleshooting
The OmsAgentForLinux purge script only removes the agent binaries from the guest OS. It does not remove or update the VM extension record stored in Azure. As a result, the extension continues to appear as Transitioning in the portal and continues to block disk migration.
- Troubleshooting Azure Windows VM extension failures - https://learn.microsoft.com/en-us/azure/virtual-machines/extensions/troubleshoot
- Troubleshoot issues with the Log Analytics agent for Linux - https://learn.microsoft.com/en-us/azure/azure-monitor/agents/agent-linux-troubleshoot
Migration from unmanaged disks to managed disks is mandatory due to the retirement of unmanaged disks. Azure does not support exemptions for remaining on unmanaged disks. - https://docs.azure.cn/en-us/virtual-machines/windows/migrate-to-managed-disks