AZUREADSSOACC password/key rollover in an existing Seamless SSO environment — any production impact?
Hi everyone,
We have an existing on-prem AD environment where Microsoft Entra Seamless SSO has been configured for quite some time.
During a recent AD security assessment, the AZUREADSSOACC computer account was highlighted as a security risk because its Kerberos decryption key/password has not been rotated recently.
Microsoft's documentation recommends periodically rolling over the Kerberos decryption key for the AZUREADSSOACC account, at least every 30 days. The documentation also provides PowerShell commands to perform the rollover from the Microsoft Entra Connect server.
Before making this change in our environment, we are planning to test it in our lab first.
I would like to understand the practical production impact:
- Has anyone performed an
AZUREADSSOACCpassword/Kerberos key rollover in an existing production environment? - Did the rollover cause any Seamless SSO interruption or authentication issues?
- Did users need to log off/restart their devices or purge existing Kerberos tickets?
- Were there any issues with Microsoft Entra Connect or the existing Seamless SSO configuration after the rollover?
- Is there anything specific we should verify before and after the rollover?
- If you have performed this in a large/older AD environment, did you encounter any unexpected behavior?
We are not looking to disable/reconfigure Seamless SSO; the goal is only to perform the recommended Kerberos decryption key/password rollover on the existing AZUREADSSOACC account as a security remediation.
Any real-world production experience would be really helpful, especially from anyone who has done this in an older AD environment.
Thanks!