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

Comentarios · 33 Puntos de vista

Our licensing engineers can help triage complex problems and ensure you're on the right support path.



Troubleshoot Office 365 Sync and Login Issues

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



We tell users to sign out completely and remove stored credentials from Windows Credential Manager or their device’s keychain. Sometimes, rejoining the device to Azure AD or just reauthenticating in Office apps does the trick. This pops up a lot after admins reset a password in the Microsoft 365 admin center. That changes the password in Microsoft Entra ID, but not right away in your local Active Directory. You end up with mismatched passwords between the cloud and your local network. The Users Loaded count will be 0 if all users fail to meet the system's requirements for user records.

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





I have multiple users experiencing sync errors with Outlook and office365. Another which is shown below, is a user opens a new message, or replies to one, and lets it sit for a while. When they go back to the message and press send they get an error that the message has been deleted. Ive repaired the OST and changed cache mode to only cache 1 year. With directory synchronization, you can continue Office 365 Sync Errors Fix to manage users and groups on-premises and synchronize additions, deletions, and changes to the cloud.

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



Troubleshoot Office 365 Sync and Login Issues

But setup is a little complicated and it can sometimes be difficult to identify the source of problems. We have resources to help you identify potential issues and fix them. With apps syncing across devices and cloud services, sync issues are among the most frequently reported M365 problems. These can include missing files, ghost icons, or documents that do not update in real-time. The sync will fail if the total number of all users (active or inactive) on your account exceeds the user limit placed upon it if present.

Reviewing Device Sign-In Settings



Troubleshoot Office 365 Sync and Login Issues

The Summary sheet on the spreadsheet attachment of your sync summary includes an Updated User Count and User Limit. These figures will give you an impression of how far over the limit the account is. Sync failure alerts do not always include a full summary or clear Outlook credentials manager attachment, you can run a test sync to obtain this data.



Password sync usually fails when credentials don’t update between Microsoft Entra ID (Azure AD) and your on-premises Active Directory. Most of the time, the problem comes from timing delays, configuration mistakes, or cached credentials on devices that don’t pick up new passwords. We check that Microsoft Entra Connect (Azure AD Connect) runs the latest version and password sync is on. Keeping things updated helps avoid compatibility issues between on-premises Active Directory and Microsoft 365. If problems stick around, we rejoin the troubleshoot Outlook synchronizing folders error devices to Microsoft 365 services.



  • The sync does not delete users but rather sets them to inactive.
  • Our relationship to the Microsoft Partner Network allows us to provide competitive pricing and authentic software and support, all with a much-needed human element.
  • On macOS or iOS, delete stored credentials from Keychain Access.
  • You will need to have the correct privileges set on your Azure account in order to set up the M365 sync.
  • Checking the sync logs helps confirm password changes are making it everywhere they should.
  • Bad settings in Azure AD Connect cause lots of password sync failures.


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.
Comentarios