Azure AD Connect Sync Error detected - Display name, Object Type, UPN = BLANK

Cracchiolo, Massimo 31 Reputation points

I'm having a Azure AD Connect Sync error. Not sure how to find this BLANK object that is attempting to sync.

Error Type: Other
Display Name and Object Type on this screen are BLANK
Click on it
Error Type 113
UPN attribute Value is BLANK but I'm provided an Object GUID Attribute Value of: aaf2d098-2d82-49fa-91ad-95f62e24f726

Full message from 'SyncErros' page

Description The object failed synchronization. For more information, please see the error details. If the problem continues and cannot be fixed, please contact Microsoft Support.

Error Details
Error Type
Last Attempted At
9/1/2021, 11:58:16 AM

Related Articles: 1. Azure AD Connect: Troubleshooting Synchronization Errors
Attribute Value
User Principal Name
Object GUID
Synchronization Status
On premises AD only


Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
20,092 questions
{count} votes

Accepted answer
  1. Satya Datla 96 Reputation points

    we had the same issue and able to figure out what was causing this error.

    we have On-prem Security Group for each O365 license, after one of our O365 license expired we have deleted the assosiated AD security group, but didn't remove the Licensed group associated with the license in Azure AD.

    2 people found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. Cracchiolo, Massimo 31 Reputation points

    THIS IS MY FIX as I did indeed have a non-synced OU (it used to be synced, with members in it; empty and non-used now) with an assigned license.:

    Credits to @Satya Datla

    Did you delete any security group associated with a license? also, moving the security group away from non-synced OU after creating a Licensed Group (in Azure AD) on a license gives you the same error... check which licensed group in Azure is attached to the non-synced (or deleted) security group in on-prem and then deleting that Licensed Group on the License should resolve your issue, i may be misleading but just want to give my suggestions.

    here is an article to trace out the issue..

    1 person found this answer helpful.
    0 comments No comments