Skip to content
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

REOPEN: Question about how many times you should run Update-AzureADSSOForest in a given timespan #701

Open
withersravenel opened this issue Apr 23, 2024 · 6 comments

Comments

@withersravenel
Copy link

In the section "How can I roll over the Kerberos decryption key of the AZUREADSSO computer account?" it states that "We highly recommend that you roll over the Kerberos decryption key at least every 30 days." but then at the bottom it states "Ensure that you don't run the Update-AzureADSSOForest command more than once per forest." Should that say don't run it more than once per forest every x days/hours, or does it really mean don't run it more than once ever? It sounded like we need to run "Update-AzureADSSOForest" at least every 30 days, but then it says not to run it more than once.


Document Details

Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

@TPavanBalaji
Copy link

@withersravenel
Thanks for your feedback! We will investigate and update as appropriate.

@SaibabaBalapur-MSFT
Copy link
Contributor

@withersravenel
The recommendation to roll over the Kerberos decryption key at least every 30 days is to ensure maximum security. However, you should not run the Update-AzureADSSOForest command more than once per forest. This command is used to update the Azure AD Seamless Single Sign-On configuration in your on-premises environment and should only be run when necessary, such as when you make changes to your on-premises Active Directory environment or when you need to troubleshoot an issue with Seamless SSO. Running this command more than once per forest can cause issues with your Seamless SSO configuration. So, to clarify, you should roll over the Kerberos decryption key at least every 30 days, but you should only run the Update-AzureADSSOForest command when necessary and not more than once per forest.

@withersravenel
Copy link
Author

The instructions on how to roll over the Kerberos decryption key states:
"...
2. Call Update-AzureADSSOForest -OnPremCredentials $creds. This command updates the Kerberos decryption key for the AZUREADSSO computer account in this specific AD forest and updates it in Microsoft Entra ID.
..."
Is there a way to roll over the Kerberos decryption key without running the Update-AzureADSSOForest command?

@SaibabaBalapur-MSFT
Copy link
Contributor

@withersravenel
Since this issue isn't directly related to improving our docs, and to gain a better understanding of your issue, I'd recommend working closer with our support team via an Azure support request. Or you can leverage our Q&A forum by posting your issue there so our community, and MVPs can further assist you in troubleshooting this issue or finding potential workarounds.
Teams Q&A forum for technical questions about the configuration and administration of Microsoft Teams on Windows.
Microsoft Teams Community forum

@withersravenel
Copy link
Author

Well, I disagree. Your document could be improved by making sense. It says the way to roll over the key is to run the command Update-AzureADSSOForest at least every 30 days, then it says to not run that same Update-AzureADSSOForest command more than once. How can you run it every 30 days and also not run it more than once?

@withersravenel withersravenel changed the title Question about how many times you should run Update-AzureADSSOForest in a given timespan REOPEN: Question about how many times you should run Update-AzureADSSOForest in a given timespan Apr 30, 2024
@SaibabaBalapur-MSFT
Copy link
Contributor

@withersravenel
I'm going to assign this to the document author so they can take a look at it accordingly.

@billmath
Can you please check and add your comments on this doc update request as applicable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants