Anyone uing AD Connect Sync Health in a non-Express setup yet?

I have a the Sync Health agent installed, and connected to AAD, but am getting an error - in the Sync Error applet it shows "Latest data is not available". AD Connect itself seems fine, my objects are syncing aok.

Interestingly, the DC at the on-premise end shows no Event Log entries in the Microsoft Azure AD Sync/Debug and Sync/Operational logs - not only no errors, no entries at all. Maybe its an issue at the on-premise end?

Any suggestions welcomed, Justin

  • 1
    Does it work now? if not, maybe we should check your on-premise firewall settings, we should add TCP/UDP 443 and TCP/UDP 5671, more infromation about the requirements, refer to the link.docs.microsoft.com/en-us/azure/active-directory/connect-health/… – Jason Ye Feb 22 '17 at 6:03
  • Thanks Jason, missed that one. Will set the firewall rules for 5671 to the windows service bus and re-test, will advise. – Justin Gillfeather Feb 24 '17 at 1:37
  • OK, please let me know if you would like further assistance – Jason Ye Feb 24 '17 at 1:40
  • can you mark an answer as accepted please? – bgtvfr May 23 '17 at 12:36

As of right now, two things can trigger this notice:

  1. Need to update to the latest health agent
  2. You have data freshness alerts active on the service

Update your agent (or turn on auto-update) and verify the connectivity between the agent and the service.

| improve this answer | |

I think Jason Ye's answer about the outgoing firewall port was the issue - i can see traffic in the syslog now, but could not before (not even Deny traffic). I'm thinking the health update is so infrequent my logs are rolling over before it happens.

Working now, thanks all. Justin

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.