Skip to content

Commit d956264

Browse files
Document asynchronous enterprise credential deletion (#63782)
Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com>
1 parent d39e3c3 commit d956264

1 file changed

Lines changed: 3 additions & 0 deletions

File tree

‎content/admin/managing-iam/respond-to-incidents/revoke-authorizations-or-tokens.md‎

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -102,6 +102,9 @@ Deleting keys and tokens removes credentials that have access to your enterprise
102102

103103
{% ifversion single_user_cred_revocation %}For example, you can delete all {% data variables.product.pat_generic_plural %} for an individual member without affecting that member's SSH keys.{% endif %} To restore programmatic access, users must create new credentials, authorize them with organizations if required, and update affected processes to use the new credentials.
104104

105+
> [!WARNING]
106+
> The "Delete keys and tokens" action is not a point-in-time operation. Credential deletion runs asynchronously and processes enterprise members in batches. Credentials created after the action starts may also be deleted if processing is still underway. To avoid deleting replacement credentials, create them only after the operation has finished.
107+
105108
### Included credentials
106109

107110
Both actions include the following credential types:

0 commit comments

Comments
 (0)