Skip to content

Commit e6aeba3

Browse files
edits
1 parent ade0329 commit e6aeba3

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ If you try to remove a user-assigned or system-assigned managed identity that yo
1919
Azure resource '/subscriptions/xxxx/resourcegroups/myGroup/providers/Microsoft.ContainerRegistry/registries/myRegistry' does not have access to identity 'xxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx' Try forcibly adding the identity to the registry <registry name>. For more information on bring your own key, please visit 'https://aka.ms/acr/cmk'.
2020
```
2121

22-
You also won't be able to change (rotate) the encryption key. The resolution steps depend on the type of identity that you used for encryption.
22+
You're unable to change (rotate) the encryption key. The resolution steps depend on the type of identity that you used for encryption.
2323

2424
### Removing a user-assigned identity
2525

@@ -50,13 +50,13 @@ If the problem persists, contact Azure Support.
5050

5151
## Identity expiry error
5252

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".
53+
The identity attached to a registry is set for autorenewal to avoid expiry. If you disassociate an identity from a registry, an error message occurs explaining to you can't remove the identity in use for CMK. Attempting to remove the identity jeopardizes the autorenewal of identity. The artifact pull/push operations work until the identity expires (Usually three months). After the identity expiration, you'll 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. Reassign the identity manually".
5454

5555
You have to reassign the identity back to registry explicitly.
5656

5757
## Accidental deletion of a key vault or key
5858

59-
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.
59+
Deletion of the key vault, or the key, that's used to encrypt a registry with a customer-managed key makes 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.
6060

6161
## Next steps
6262

0 commit comments

Comments
 (0)