The sync will fail if it can't find any users that comply with your filtering preferences or the system's requirements for user records. The system requires that users have a first name, last name and a valid email address that conforms with your domain lock if enabled. The sync does not delete users but rather sets them to inactive. The idea is to provide a recycle bin of users who you can delete when you no longer need them.

TrustedTech

If a password reset in Office 365 isn’t syncing, users usually get sign-in errors or find old credentials still hanging around on devices. We focus on restoring sync between Microsoft Entra ID (Azure AD), on-premises Active Directory, and user devices so everyone gets back in without headaches. If password sync is off or the server is in staging mode, passwords won’t update. We turn password sync back on by running the Entra Connect configuration wizard and picking Customize synchronization options. Check that your password change actually synced between your on-premises Active Directory and Microsoft Entra ID (formerly Azure AD). If it didn’t, a few targeted checks usually restore access—no need to keep resetting your password over and over.

What to do when Office 365 password reset doesn’t sync across devices

Real-time collaboration is at the core of Microsoft 365; however, issues can arise due to permissions, software version conflicts, or connectivity problems. Find out what to do if you are having issues with syncing users or groups from Microsoft 365. It seems to be some sort of error with the user not being able to connect and sync with Outlook stuck updating folders solution M365 servers. We also scan Event Viewer logs under Applications and Services Logs → Directory Synchronization for Event IDs like 650–657 (for sync activity). Errors like Event ID 611 point to invalid replication data or outdated software. On the sync server, we open the Synchronization Service Manager and check that the last sync finished without errors.

Login & Sync Errors: Personal & Business Microsoft 365 Accounts on Same Device

Bad settings in Azure AD Connect cause lots of password sync failures. If password writeback isn’t enabled or the service account doesn’t have the right permissions, new passwords won’t update in Active Directory. That leaves people locked out with their new password on the cloud but not locally. We show users how to reset passwords using approved methods like the Microsoft 365 portal or self-service password reset (SSPR). If someone changes their password only in the cloud or just on a local system, things can get out of sync pretty quickly.

Reviewing Device Sign-In Settings

You can view your guide to Office 365 sign-in errors inactive users on the Users page and delete them as you see fit. Similarly you should review the Users Deactivated sheet on the sync summary spreadsheet attachment as you can also delete these users to bring your total down. If sync keeps failing, we make sure the Microsoft Entra Connect service account has the right permissions and the server connects to the domain controller. Updating Azure AD Connect to the latest build often fixes known sync issues.

How Much Do Managed IT Services Cost?

Microsoft 365 is a robust platform, but when problems arise, fast resolution is key to productivity. From sync errors to sign-in challenges and resolve Outlook not sending emails fast collaboration setbacks, these common Office 365 troubleshooting techniques can restore service quickly. If you don't wish an inactive user to be made active by the M365 sync, you can add the user's email address to the sync forbid list. You can do this in the Microsoft 365 Sync Wizard on the configuration page of your platform settings. The most common reason for missing users is that you've run a Test Sync, instead of a Manual Sync. If that doesn't resolve your missing users issue, please follow our guide to troubleshooting missing users below.

• If problems stick around, we rejoin the devices to Microsoft 365 services.
• Even I've only been doing this with test users so far, so haven't actually broken any actual users yet, I still need to get this resolved quickly.
• We also scan Event Viewer logs under Applications and Services Logs → Directory Synchronization for Event IDs like 650–657 (for sync activity).
• Running the Azure AD Connect Health tool gives you alerts for sync errors and interruptions.
• Sync failure alerts do not always include a full summary or attachment, you can run a test sync to obtain this data.
• For managed environments, we use Intune or Group Policy to force sign-in credential sync and clear old tokens.
• The system requires that users have a first name, last name and a valid email address that conforms with your domain lock if enabled.
• You can stop any accounts from being brought over by adding them to the sync deny list.
• Users I create within the Office 365 portal are fine, so I assume it is something to do with Azure AD Connect.

You should run a test sync after re-authenticating the sync to ensure it is working. Devices sometimes keep using cached passwords even after a successful sync. If users access multiple apps with the same login, we make sure Single Sign-On (SSO) settings line up so the new password works everywhere in Microsoft 365. If there’s a delay, we manually trigger a password sync using Microsoft Entra Connect.