Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature]: 2024-11-01 API version for Azure Managed HSM #27067

Open
Cherrett opened this issue Feb 4, 2025 · 0 comments
Open

[Feature]: 2024-11-01 API version for Azure Managed HSM #27067

Cherrett opened this issue Feb 4, 2025 · 0 comments
Labels
Azure PS Team feature-request This issue requires a new behavior in the product in order be resolved. KeyVault

Comments

@Cherrett
Copy link
Member

Cherrett commented Feb 4, 2025

Description of the new feature

I am a part of the Azure Managed HSM team. When creating a new Managed HSM resource using New-AzKeyVaultManagedHsm, 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.

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.

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

Proposed implementation details (optional)

No response

@Cherrett Cherrett added feature-request This issue requires a new behavior in the product in order be resolved. needs-triage This is a new issue that needs to be triaged to the appropriate team. labels Feb 4, 2025
@microsoft-github-policy-service microsoft-github-policy-service bot removed the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Azure PS Team feature-request This issue requires a new behavior in the product in order be resolved. KeyVault
Projects
None yet
Development

No branches or pull requests

2 participants