Azure AD Connect service critical alert reported: dn-attributes-failure

Iron Contributor

[I sent an email to with the below content a few days ago but haven't heard back so decided to start a conversation here]


As per the below synchronization errors email I have been receiving, there are three cloud-only Office 365 users with “Sign in ‎blocked” that were previously synched using Azure AD Connect.  The accounts were previously moved out of the sync OU and when they appeared as deleted users in Office 365, were restored to keep their data intact.  The AD users have since been deleted and cannot be restored.



There are no further error details other than the type: dn-attributes-failure



There are no other sync errors and Azure AD Connect is showing success on all connector operations.


I do not want to delete these accounts from Office 365.


Could anyone please advise me to know which steps to take to resolve the issue causing these three accounts to be included in the report for synchronization errors?  They are cloud-only and do not need to be synched with AD.


Is it necessary to re-create the AD users in the sync OU and set their Office 365 account ImmutableID to sync and match their AD account (source anchor is objectGUID) so they do not get reported as sync errors?




From: Microsoft Azure []
Sent: 02 September 2019 11:10
Subject: We detected synchronization errors in your directory



There are synchronization errors in your directory.                                                                                                                                                                                                                                                         


 Azure AD Connect Sync errors detected

You’re receiving this email because we have detected a critical alert on your Azure AD Connect service for errors that occurred while data was while synchronizing between your on- premises active directory and your Azure Active Directory.




Sync errors detected on your Azure AD Connect service


Last export time:

August 13, 2019 15:25 UTC


Error count:

3 sync errors






John Hanson School



To get more details, see Sync Error Report.


To learn how to fix sync errors, see troubleshooting sync errors.

If you have any feedback, please post it to the Azure Active Directory Feedback Forums or contact us for any questions.




Privacy Statement

Microsoft Corporation, One Microsoft Way, ​Redmond, WA 98052​

1 Reply

@rs_oakfordLooks like may be stuck in Azure AD Connect, and is still provisioning when it shouldn't be. Maybe try "set-msoluser -UserPrincipalName <name> -ImmutableID "$null" " ?