az vm disk detach to support force-detach

[avinashakka]

Resource Provider

• Compute Resource Provider (Microsoft.Compute)

Description of Feature or Work Requested

Azure will now support force-detaching managed data disks from a VM. This feature is supported as part of VM recovery scenarios, when a VM is unresponsive due to unexpected failure in underlying stack, Client can choose to just forcibly detach a data disk to mount it and use with another healthy VM. This feature is supported exclusively only for managed disks [Azure Managed Disks] and on Single instance/ Availability set VMs

The existing Az-CLI cmd az vm disk detach should be updated to support a optional --forceDetach param which internally should set tobeDetached and detachOption property of the disk. Force-detaching a data disk is currently supported only by setting toBeDetached == true and detachOption == 'ForceDetach' on the DataDisk

Additional References:

• PowerShell cmdlet update design request: https://github.com/Azure/azure-powershell-cmdlet-review-pr/issues/851

Minimum API Version Required
2020-12-01

Swagger Link

• Adding new 'detachOption' property for data disk force-detach using Update VM azure-rest-api-specs#11554
• New optional detachOption property introduced for data disk.
• Sample update (Put/Patch) VM request to force-detach a disk

Target Date
March/April 2021 or the next Az-Cli release which ever is the earliest

[yungezz]

will put it in 3/25 release for now.

[avinashakka]

will put it in 3/25 release for now.

If that is the earliest possible release then that sounds good.

[avinashakka]

@yungezz Any update on this? This was supposed to go in 3/25/2021 but looks like it still hasn't been completed: https://docs.microsoft.com/en-us/cli/azure/vm/disk?view=azure-cli-latest#az-vm-disk-detach. Is there an ETA on this?

[zhoxing-ms]

@avinashakka Sorry, due to re-org, our team is currently responsible for the feature requests related to VM. I'm sorry we didn't realize this request before.
We will plan to develop and release it in the next sprint (09-06), this is the fastest time we can release. May I ask is this time acceptable?

[avinashakka]

We need this ASAP as we discovered that this is still not supported when a customer tried it directly and saw it wasn't working.
@zhoxing-ms Please try to get this in as soon as possible. [Tagging @ramankumarlive, @smotwani also for visibility]