Skip to content

Commit ade0329

Browse files
Identity expiry error
1 parent 69f1d2c commit ade0329

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

articles/container-registry/tutorial-troubleshoot-customer-managed-keys.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -48,6 +48,12 @@ If you enable a key vault firewall or virtual network after creating an encrypte
4848

4949
If the problem persists, contact Azure Support.
5050

51+
## Identity expiry error
52+
53+
The identity attached to a registry is set for auto-renewal to avoid expiry. If you disassociate an identity from a registry, an error message will occur explaining you cannot remove the identity in use for CMK. Attempting to remove the identity will also jeopardize the auto-renewal of identity. The artifact pull/push operations work until the identity expires (Usually three months). After the identity expiration, you will see the HTTP 403 with an error message "The identity associated with the registry is inactive. This could be due to attempted removal of the identity. Please reassign the identity manually".
54+
55+
You have to reassign the identity back to registry explicitly.
56+
5157
## Accidental deletion of a key vault or key
5258

5359
Deletion of the key vault, or the key, that's used to encrypt a registry with a customer-managed key will make the registry's content inaccessible. If [soft delete](../key-vault/general/soft-delete-overview.md) is enabled in the key vault (the default option), you can recover a deleted vault or key vault object and resume registry operations.

0 commit comments

Comments
 (0)