Troubleshooting Microsoft 365 sync issues usecure Help Centre
Public Group
Active 6 months ago
Group Leadership
- Group Administrators
-
-
Content
The ImmutableId attribute, by definition, shouldn’t change in the lifetime of the object. But maybe Microsoft Entra Connect wasn’t configured with some of the scenarios in mind from the preceding list. Starting September 1, 2016, Microsoft Entra ID duplicate attribute resiliency is enabled by default for all the new Microsoft Entra tenants.
Fix the InvalidHardMatch error
When a user is excluded from sync scope the object becomes soft-deleted in Microsoft Entra ID and its DirSyncEnabled attribute is switched to False. This process however doesn’t convert the object to cloud managed, as it still contains attributes and values synchronized from on-premises Active Directory that can’t be managed in the cloud. The DirSyncEnabled value is False to indicate that it’s currently out of sync scope and is available to be matched again.
We have resources to help you identify potential issues and fix them. You can assign the administrative role to the existing user object again after the soft match between the on-premises user object and the Microsoft Entra user object has finished. Microsoft Entra Connect isn’t allowed to soft match a user object from on-premises AD with a user object in Microsoft Entra ID that has an administrative role assigned FixTechGuide support for Office 365 to it.
Fix the Existing Admin Role Conflict error
Sync failure alerts do not always include a full summary or attachment, you can run a test sync to obtain this FixTechGuide mailbox repair steps data. You’ll also receive a mail (to the alternate email and to your admin email) from Microsoft 365 that indicates your tenant has encountered directory synchronization errors. For details see Identify directory synchronization errors in Microsoft 365. Incorrect Outlook settings can also be one of the reasons behind Outlook synchronization errors. When Microsoft Entra Connect tries to sync an object that exceeds this object size limit, an export error is thrown.
Mailing Address
Outlook sync issues can be because of corrupted Outlook OST or PST files. Therefore, now we will know the steps to repair the Outlook data file. The simplest way to resolve authentication issues is to rerun the authentication repair PST file without data loss process by clicking the Sign in with Microsoft on the Microsoft 365 settings page. You run the Microsoft consent process using an eligible M365 account after which you will be taken to the sync’s setup wizard.
What should I do if my sync failed due to authentication issues?
Examples include revoked or expired certificates and outdated or unnecessary addresses, such as SMTP, X.400, X.500, MSMail, and CcMail. As a rule of thumb, it’s safer to assume that the limit of SMTP addresses in the proxyAddresses attribute is approximately 300 addresses to leave room for future growth of the object and its populated attributes. It isn’t possible to determine exactly how many entries an attribute can hold in Microsoft Entra ID, for example, how many SMTP addresses can fit in the proxyAddresses attribute. The amount depends on the size and multiplying factors of all the attributes populated in the object. The admin adds a new user or contact in on-premises Active Directory that isn’t synced to Microsoft Entra ID yet with the same value for the proxyAddresses attribute as that of the Microsoft 365 group.
This solution will be beneficial for users who are facing Outlook syncing issues because of corrupted PST or OST files.Unfortunately, covering every scenario in one document isn’t possible.After these instructions, ensure the sync settings are correct and check everything is working well.Because duplication of these attributes isn’t permitted in Microsoft Entra ID, the operation can result in an ObjectTypeMismatch sync error.Moreover, it maintains the folder hierarchy and metaproperties of the data when processing Outlook data files.Microsoft Entra ID enforces various restrictions on the data itself before allowing that data to be written into the directory.This section discusses potential causes and solutions to resolving the error DeletingCloudOnlyObjectNotAllowed (Error Type 114).We advise customers to enable BlockCloudObjectTakeoverThroughHardMatchEnabled unless they need it to take over existent accounts in Microsoft Entra ID.
Example scenarios for an InvalidHardMatch error
If that doesn’t resolve your missing users issue, please follow our guide to troubleshooting missing users below. After viewing, see fixing problems with directory synchronization for Microsoft 365 to correct any identified issues. To resolve these issues you should run the steps in this article and check whether the groups in your sync’s filtering preference contain users in Azure AD. The sync will fail if the groups you selected to load users from no longer exist in Azure AD. Typically this is because the selected groups have been deleted from Azure AD since the M365 sync was configured on your account.
The operation results in an InvalidSoftMatch synchronization error when the object with the immutableId attribute set with a value, fails the hard match but satisfies the soft match criteria. The other solution to fix Outlook sync issues is recreating Microsoft Outlook profile. 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. 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.
You can stop any accounts from being brought over by adding them to the sync deny list. This means that the authentication setup for your sync is no longer valid. This can happen for the a number reasons particularly if your sync authenticates using Delegated Permissions. You will need to have the correct privileges set on your Azure account in order to set up the M365 sync. This section discusses LargeObject or ExceededAllowedLength errors.