Entra Connect Sync updated to 2.6.1.0, and now broken.

Question

Entra Connect Sync updated to 2.6.1.0, and now broken.

Scott P 25

Entra Connect Sync updated to 2.6.1.0. since the upgrade, it gave us an alert: Password Hash Synchronization heartbeat was skipped in last 120 minutes.

the syncronizatin manager shows the last update at 2:47AM

when i run start-Adsyncsynccycle, it gives me an error about cloud sync intervals.

is anyone experiencing this? any fix?

James Rudley 10 Reputation points

2026-02-18T17:23:08.34+00:00

Yes, we saw it today when it auto upgraded to this version in gov cloud. We're popping a ticket now.
Dee B 0 Reputation points

2026-02-18T23:01:55.4733333+00:00

Same issue here. I just received the same notification and error about "cloud sync intervals" at 12:49pm EST today(2/18). I found an article, but it was talking about rolling back to the previous version, but I'm trying to avoid doing that. This is definitely caused by a change at Microsoft with the upgrade, so hopefully they can push something out to fix it. I'll see if I can somehow open a ticket also in addition to James.
James Rudley 10 Reputation points

2026-02-18T23:12:14.14+00:00

Ms support has no idea. We fixed it by installing 2.6.1.0 on a test vm, grabbed the miisserver.config, copied to prod machine, reapplied fips config in it and restarted service.
Scott P 25 Reputation points

2026-02-20T16:58:07.5833333+00:00

James,

I installed it but did not complete the wizard. I did not find the miisserver.config. did you have to complete the wizard to create the file? If I complete the wizard it will be asking for credentials and stuff. Just checking on this stuff.
James Rudley 10 Reputation points

2026-02-20T17:10:53.36+00:00

Once the wizard finished, I found the file. I didnt setup the creds to pull the file

1 answer

Your answer

James Rudley 10 Reputation points

2026-02-18T17:23:08.34+00:00

Yes, we saw it today when it auto upgraded to this version in gov cloud. We're popping a ticket now.
Dee B 0 Reputation points

2026-02-18T23:01:55.4733333+00:00

Same issue here. I just received the same notification and error about "cloud sync intervals" at 12:49pm EST today(2/18). I found an article, but it was talking about rolling back to the previous version, but I'm trying to avoid doing that. This is definitely caused by a change at Microsoft with the upgrade, so hopefully they can push something out to fix it. I'll see if I can somehow open a ticket also in addition to James.
James Rudley 10 Reputation points

2026-02-18T23:12:14.14+00:00

Ms support has no idea. We fixed it by installing 2.6.1.0 on a test vm, grabbed the miisserver.config, copied to prod machine, reapplied fips config in it and restarted service.
Scott P 25 Reputation points

2026-02-20T16:58:07.5833333+00:00

James,

I installed it but did not complete the wizard. I did not find the miisserver.config. did you have to complete the wizard to create the file? If I complete the wizard it will be asking for credentials and stuff. Just checking on this stuff.
James Rudley 10 Reputation points

2026-02-20T17:10:53.36+00:00

Once the wizard finished, I found the file. I didnt setup the creds to pull the file

Answer 1

Scott P 25

James! your steps WORKED! I did a custom install (b/c I didn't know any better) and checked custom install directory. after it installed, it did ask to setup credentials but I cancelled that. the file was created. I took that file to the existing server, added the enforceFIPSPolicy enabled="false" line.

Restarted the Service. and now it SUCCESSFULLY updates.

thanks for your guidance!

James Rudley 10 Reputation points

2026-02-20T17:34:41.63+00:00

Awesome. I wish MS would put out a response to this.
Dee B 0 Reputation points

2026-02-20T17:38:42.64+00:00

Nicel! I ended up creating a backup of the existing settings, and uninstalling v2.6.1, downgraded to 2.4.x, then imported the settings to the 2.4.x version. I cut off the "auto update" service so it won't try to update back to 2.6.1 again. I agree with you James, Microsoft needs to respond to this because it's not just us three.

Share via

Entra Connect Sync updated to 2.6.1.0, and now broken.

1 answer

Your answer