Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Microsoft 365 Certified: Endpoint Administrator Associate · Microsoft
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
In the Synchronization Manager, you can find missing objects in the Connector Spaces. Missing objects are usually caused by domain-based or OU-based filtering, which is prior to rules being applied. https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/tshoot-connect-object-not-syncing
The OU can't be added via Sync Rules
I think its A. Its not related to OU selection/filtering as AAD Connect health says it has synced ALL user accounts BUT these 10 are not appearing in Azure AD. So the accounts are making the initial sync from the OnPrem AD into the Meta zone (AAD Connect). Rules then apply and if the rule conditions are met - then the sync from the Meta to Azure AD will complete. So it's feasible that a rule is causing the problem. Why not impact the other accounts. Maybe these accounts are missing specific attribs from their OnPrem AD that the current rule needs to push the sync. Saying all that... it could potentially be something else. Maybe stale / relic objects in Azure AD that match attribs from these 10 accounts. So its A for me but only a 70% A.