az vm repair create can fail due to policy restrictions

[pagienge]

Describe the bug

It appears that the default repair VM config uses premium SSD disks, with no way to alter this. In scenarios where an organization has put restrictions on potentially costly infrastructure, such as premium ssd, 'az vm repair create' can fail in ways that cannot be mitigated.

Related command

az vm repair create -n rhel9an -g litterbox

Errors

Do not have the call trace / error as this was during SR troubleshooting, but it was clear that policy was restricting the creation of the VM.

Issue script & Debug output

not available

Expected behavior

Would have preferred the default repair VM config to be using the least costly disk available, perhaps with an option to create higher tier disks if desired, much like public IPs can be optional.

Environment Summary

{
"experimental": false,
"extensionType": "whl",
"name": "vm-repair",
"path": "/home/pagienge/.azure/cliextensions/vm-repair",
"preview": false,
"version": "1.0.8"
}

Additional context

Premium disks may be more useful for Windows nested Hyper-V scenarios, but for Linux there is no gain from premium disk in the repair VM.

We are also using 'az vm repair' with ALAR in 'fixit' buttons in the Azure portal, this is one failure mode that could be disruptive in these automated use-cases.

[yonzhan]

Thank you for opening this issue, we will look into it.

[microsoft-github-policy-service]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Drewm3, @TravisCragg-MSFT, @nikhilpatel909, @sandeepraichura, @hilaryw29, @GabstaMSFT, @ramankumarlive, @ushnaarshadkhan.

[microsoft-github-policy-service]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Drewm3, @TravisCragg-MSFT, @nikhilpatel909, @sandeepraichura, @hilaryw29, @GabstaMSFT, @ramankumarlive, @ushnaarshadkhan.

[microsoft-github-policy-service]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Drewm3, @TravisCragg-MSFT, @nikhilpatel909, @sandeepraichura, @hilaryw29, @GabstaMSFT, @ramankumarlive, @ushnaarshadkhan.

[TravisCragg-MSFT]

@pagienge Thanks for the feedback! We are currently assessing this for our roadmap going forward.