Sep 05 2017
11:45 PM
- last edited on
Jan 14 2022
05:35 PM
by
TechCommunityAP
Sep 05 2017
11:45 PM
- last edited on
Jan 14 2022
05:35 PM
by
TechCommunityAP
Hello Team,
Today I successfully integrated On-prem AD with Cloud AD. I have verified that changes/additions made on Local AD are being synced to Cloud AD. So sync is working fine.
In my Office365 portal, I am seeing that sync is successful and data is coming in. However, on Azure AD Connect Health, it is showing errors. In that section, the domain listed in the Sync Error section is incorrect, my domain is not an onmicrosoft one but a dedicated one.
So, How do I tell Connect Health to track proper domain? Any method(s) to refresh it or Reinstall that particular software?
Sep 06 2017 01:42 AM - edited Sep 06 2017 01:45 AM
Few thoughts as per screenshot its clearly seen that AD - Azure AD are in Sync .
How many AAD Connect servers we have ?
Do we have AAD Premium license for Health Montoring ?
It seems issue is not with AAD Connect Sync rather seems to be an issue with Health Connect Agent. Health Connect agent requires AD Premium license so if you have installed AD Connect Health Agent inorder to use that successfully you would require AD Premium License.
Please refer FAQ's for AAD Connect Health Agent below
Hope this helps
Sep 07 2017 03:48 AM
I have the license for Azure Active Directory P1. Is that enough for this to work?
Sep 11 2017 03:06 AM
Hi ,
Please check the below as per the same article first agent requires at least one AAD Premium and each additional registered wil require 25 more ......hope this helps
Q: How many licenses do I need to monitor my infrastructure?
Licensing information is also found on the Azure AD Pricing page.
Example:
Registered agents Licenses needed Example monitoring configuration
1 | 1 | 1 Azure AD Connect server |
2 | 26 | 1 Azure AD Connect server and 1 domain controller |
3 | 51 | 1 Active Directory Federation Services (AD FS) server, 1 AD FS proxy, and 1 domain controller |
4 | 76 | 1 AD FS server, 1 AD FS proxy, and 2 domain controllers |
5 | 101 | 1 Azure AD Connect server, 1 AD FS server, 1 AD FS proxy, and 2 domain controllers |
Sep 11 2017 07:15 AM
The problem was indeed linked to my licensing. Thank you for pointing it out.
I was under Microsoft Business License, and Azure P1 comes only for Enterprise editions.