I've deployed connect health to monitor my ADFS implementation (2 federation servers, 2 proxies. server 2012. ADFS 2.1. All in Azure IAAS VMs. No outbound restriction/proxy/limitations, etc.) I have the blade created in my azure portal, and I have the agents deployed to all four servers. I can see the servers in the azure portal, but they are all listed as "warning" status with the error "health service data is not up to date" and additional info about how no information has been received since X date.
If I restart the three windows AD heatlh services on the servers, the date will update (so it seems like it gets a heartbeat from the server), but it doesn't move the warning from active to resolved. Also, I see no data about logins processed, services authenticated to, etc.
So, I have two symptoms with probably only one cause: 1. the agents aren't "phoning home" regularly, 2. I don't get any useful data in the portal.
I'd appreciate any troubleshooting ideas anyone might have.
Thanks!