Skip to content

Update delegated-managed-service-accounts-set-up-dmsa.md #7996

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -121,7 +121,7 @@ To migrate a service account to a dMSA, follow these steps:
### Complete account migration

> [!WARNING]
> When finalizing the migration, **never** delete the original service account in case you need to revert back to it post migration as this causes several issues.
> When finalizing the migration, **never** delete the original service account! Deleting the original service account prevents you to revert back to a previous state, but also prevents anything still using/configured with that original service account from authenticating successfully. The original service account, although disabled, is the link between the services running the original service account and the dMSA in AD. Deleting the original service account breaks that linkage and logons will fail! Resetting the password in AD of original service account to a stronger password is OK, unless you need to revert back to the previous state. Keeping the history of password(s) of the original service account in a secure password may therefore be recommended.

To complete the account migration, traditional service accounts must be disabled to ensure that all services use the dMSA.

Expand Down