You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ensure the same suite of tests are run against MHSM and KV (depending on your infrastructure, you might remove some annotation or you might need to duplicate the tests)
Note (11/5/21): Creating a key with a release policy and releasing it currently works on Key Vault and Managed HSM. However, importing a key with a release policy, or updating a key's existing release policy, work on Managed HSM but not Key Vault.
Importing a key with a release policy specified results in a key that has None for a release policy.
Updating a key's release policy fails with the following error, even when the exportable attribute isn't specified in update_key_properties: azure.core.exceptions.HttpResponseError: (BadParameter) AKV.SKR.1014: Cannot modify the exportable state of a key.
The text was updated successfully, but these errors were encountered:
SKR is not fully supported in Key Vault, only MHSM.
Once it is available globally in KV implement the following changes:
None
for a release policy.exportable
attribute isn't specified inupdate_key_properties
:azure.core.exceptions.HttpResponseError: (BadParameter) AKV.SKR.1014: Cannot modify the exportable state of a key.
The text was updated successfully, but these errors were encountered: