Az group delete --force-deletion-types fails with api-version mismatch

This is autogenerated. Please review and update as needed.

Describe the bug

Az group delete --force-deletion-types fails with api-version mismatch.

Command Name az group delete

Errors:

(ResourceGroupDeletionTimeout) Deletion of resource group 'ResourceGroupName' did not finish within the allowed time as resources with identifiers 'Microsoft.Compute/virtualMachineScaleSets/VMSSName' could not be deleted. The provisioning state of the resource group will be rolled back. The tracking Id is '51aab640-2cb2-4cd2-a505-43b71602644b'. Please check audit logs for more details.
Code: ResourceGroupDeletionTimeout
Message: Deletion of resource group 'ResourceGroupName' did not finish within the allowed time as resources with identifiers 'Microsoft.Compute/virtualMachineScaleSets/VMSSName' could not be deleted. The provisioning state of the resource group will be rolled back. The tracking Id is '51aab640-2cb2-4cd2-a505-43b71602644b'. Please check audit logs for more details.
Exception Details:      (None) {"error":{"code":"BadRequest","message":"This request can be made with api-version '2022-03-01' or newer."}}
        Code: None
        Message: {"error":{"code":"BadRequest","message":"This request can be made with api-version '2022-03-01' or newer."}}
        Target: /subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-13c8e4160d62/resourceGroups/ResourceGroupName/providers/Microsoft.Compute/virtualMachineScaleSets/VMSSName

To Reproduce:

Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

• Put any pre-requisite steps here…
• az group delete --name {} --yes --debug --force-deletion-types Microsoft.Compute/virtualMachineScaleSets

Expected Behavior

Successfully delete a resource group with the forcedelete option.

Environment Summary

Windows-10-10.0.22621-SP0
Python 3.10.8
Installer: MSI

azure-cli 2.42.0

Extensions:
aks-preview 0.5.114

Dependencies:
msal 1.20.0
azure-mgmt-resource 21.1.0b1

Additional Context

[MinKPark]

@navba-MSFT thanks for pinning me on this. I asked my team to confirm this. I’ll let you know once it is confirmed.

[navba-MSFT]

@MinKPark Thanks for sharing the error message over teams chat internally. Currently I see that you are getting a different error. Could you please share the complete cli command that you ran ? Also run the command with --debug switch and share the error output.

If you want to work on this more closely with a Remote desktop sharing live-meeting session, please open a Microsoft support ticket and our support professional will get in touch with you to work on this.