The Entra Connect Delta Synchronization process took longer than usual

[Max Coder]

Hi,

Today, users complained that they changed their passwords but the passwords were not synchronized with Entra ID.

First, when I checked Entra Portal, I saw that Password Sync was enabled. Similarly, Entra AD connect was in a healthy state.

I then checked the Entra AD Connect server for any events related to password sync. There were no FAILED events. Everything looked normal.

As shown in the screenshot below, the Delta Sync time for the company.onmicrosoft.com connector took approximately 2 hours.

The only thing I can think of that could have caused this issue is that I was making changes to an M365 group using PowerShell at that time. The group had approximately 5,000 members.

Could this have caused the issue?

Because afterward, password sync returned to normal.

Screenshot:

[Michael B. Smith]

I’ve never seen that behavior before.

 

The most common delay I see is that someone has the Entra ID Connect app open, and sync is suspended during that timeframe.

 

Have you looked at the logs to see what was going on?

--
You received this message because you are subscribed to the Google Groups "ntsysadmin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ntsysadmin+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/ntsysadmin/08916b3d-5358-4921-9ac4-3cdbabe67e42n%40googlegroups.com.

[brett...@hotmail.com]

I concur, the only time I have pauses like this is when someone has opened the Sync Setup app and left it doing nothing. Sync will restart immediately the app is closed, if it's missed a sync cycle, so in your case I would expect someone to have closed the app at 14:19:59, but can't explain why it only did the one delta sync step not the full list of steps, and then it took until 14:57:32 to start the correct full sync run. 

Did you check the eventlog for any app crashes etc, or server restarts? 

[brett...@hotmail.com]

I did think of one other point that I've seen mysterious "sync  stopped" events, but discounted that in my initial thoughts but decided better.

I've had MIIS on a VM stop running with no errors when there's a lack of memory on the VM - we saw it most often when we only had 4Gb RAM VMs in Azure, so we allocated 8Gb and that gave sufficient headroom for it to not randomly stop. If you're on a busy shared use box you might have run out of memory?

[Aakash Shah]

Note that 6gb of RAM is the suggested minimum RAM for Entra Connect (assuming the default SQL Express LocalDB – SQL Server would need more):

Microsoft Entra Connect: Prerequisites and hardware - Microsoft Entra ID | Microsoft Learn

 

-Aakash Shah

To view this discussion visit https://groups.google.com/d/msgid/ntsysadmin/4d70ecba-6a90-430c-b89f-ab6ef339798fn%40googlegroups.com.