I've recently been having issues with Autopilot where it hangs during the user phase after prompting users to change their password upon first login. The password change process seems successful in both Azure and on-premises systems, but after the change, a message appears saying: "You're all set—we just need a moment. Your password was successfully updated, but our servers take a little time to catch up. Please try signing in again in a few minutes." This happens with a correlation ID and timestamp noted but if the device is hard reset, it allows sign-in with the new password. If anyone has encountered this before or has suggestions, your help would be greatly appreciated!
3 Answers
Sounds like you’re dealing with an Autopilot OOBE password sync hang! It's a known issue with Entra sync delays. Try waiting 10-15 minutes before retrying the sign-in. If it's stuck, you can do a Shift+Restart, then head to Troubleshoot and Reset PC (keeping your files). If you’re in a hybrid setup, try forcing a delta sync in Azure AD Connect. Autopilot can be a drama queen sometimes!
Are you utilizing passthrough authentication? If that's the case, check if hash syncing is enabled as well. We faced a similar problem and found that disabling either resolved the issue for us.
Yes, we're using both. My IT team says they've been enabled for months without any changes lately.
With this setup, should helpdesk staff be able to reset passwords through the Entra portal or AD users and groups? They should have access to both, right?
This seems to be a classic problem with Entra/Azure AD writeback delays. The password changes successfully, but the sync can lag behind (anywhere from 1 to 15 minutes), which causes the OOBE to get stuck on "just need a moment" or "servers catching up."
Thanks for the insight! I really appreciate all the feedback. I'll keep everyone posted on what Microsoft says.
But what's the cause of this writeback delay? I noticed the password changes in both systems instantly.
Ugh, that's frustrating. We've been using this same setup for three years, so it's odd that it just started happening last week.