2024-11-01 API version for Azure Managed HSM

[Cherrett]

Related command

I am a part of the Azure Managed HSM team. When creating a new Managed HSM resource using az keyvault create, the SKU defaults to the B family, irrespective of the SKU name specified. This is not correct since we have certain SKUs in the C family.

Source Code

Is your feature request related to a problem? Please describe.

az keyvault create --hsm-name "test" --resource-group "test" --sku Custom_C42

Describe the solution you'd like

The new SKUs are included in the Microsoft.KeyVault 2024-11-01 API version. Azure CLI should use this API version.

Additional context

These are all of the valid Managed HSM SKUs:

B SKU family: Standard_B1, Custom_B32, Custom_B6
C SKU family: Custom_C42, Custom_C10

For Custom_C42 and Custom_C10, the SKU family passed to ARM should be C instead of B.

This can be determined by checking the letter following the underscore in the SKU name.

[yonzhan]

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

[github-actions]

Here are some similar issues that might help you. Please check if they can solve your problem.

• Managed HSM SKU defaults to B family #30292

---

Possible solution (Extracted from existing issue, might be incorrect; please verify carefully)

Azure CLI is using 2023-07-01 API version for MHSM operations and from the swagger there're only skus for B family: Standard_B1,Custom_B32,Custom_B6. We are not aware of any C family. If there's feature added, can you pls update swagger to generate SDK new version and then file a feature request for CLI team?

Reference:

• Managed HSM SKU defaults to B family #30292 (comment)

[evelyn-ys]

@Cherrett Pls make sure that the new API version has been added in swagger repo and the related Python SDK has been released