JerryJordan-6634 avatar image
0 Votes"
JerryJordan-6634 asked JoshuavanLieshout-8607 edited

Azure AD Sync WorkflowException - Cannot Find Object GUID

I've been receiving an synchronization error with Azure AD Connect.

Error Type: WorkflowException

UPN: <blank>

Synchronization status: "On premises AD only"

The only thing I have to work with is the Object GUID, but the search results with Get-ADObject doesn't return anything with that GUID. I even exported all objects to CSV to manually look for it.

Nothing to go on in the Event Viewer for the sync server and the troubleshooting tools are no help since I do not have a DN.

I've even did a search against all DCs for the GUID to include deleted items to no avail.


· 9
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thanks for your question! Can you please provide the full error message that you are seeing and a screenshot if you have one?

1 Vote 1 ·

Sure not much here though.


1 Vote 1 ·
image.png (15.1 KiB)

Just realized the Object GUID is changing. I've now seen three different GUIDs.

1 Vote 1 ·

I have the same issue? Any resolution?
This is the error I receive:

Attribute Attribute Value
User Principal Name
Object GUID
Synchronization Status
On premises AD only

0 Votes 0 ·

I am having the same issue. What there a resolution to this? I haven't been able to find the GUID on prem or in Azure.

0 Votes 0 ·
RKIM-7102 avatar image RKIM-7102 DuncanMarshall-0943 ·

I am using a tool called IDfix to find errors with AD which I've been correcting. I still am getting AD Sync errors though, however, I'm not done correcting errors from IDfix. Something you might look into if you haven't already:

1 Vote 1 ·

I'll check that out.

Thanks for the tip!

0 Votes 0 ·
Show more comments

Today I got the same error and could'nt find the source of the object until I looked in the Synchronisation Service Manager.
Then found the object that was causing the error. After that the main problem was easy to find.

Our servicedesk recovered a deleted user-object in Azure before they did the same on-premise.
The consequense of this was that the user is now a 'cloud-only' user.. but AAD-connect still tries to sync this user-object, hence te error in Azure.

I deleted the cloud-only object and let in sync from on-premise.
Then my problem was fixed.

Maybe the cause of your problem is different, but I hope this helps someone.

0 Votes 0 ·

0 Answers