Forum Discussion

ch0wd0wn's avatar
ch0wd0wn
Copper Contributor
Dec 18, 2019

AAD COnnect object not in metaverse

I have AAD Connect running and cannot sync this one user.  Here are some facts   1. User is in an OU that's configured to Sync 2. User is found in the Connector Space for on prem AD 3. User is NO...
Azure Active Directory (AAD)
  • ch0wd0wn's avatar
    ch0wd0wn
    Dec 25, 2019

    VasilMichev  Thanks for the article. 

     

    I'm really trying to follow this but the verbiage is confusing:

    " In the following scoping filter, if the isCriticalSystemObject value is null or FALSE or empty, it's in scope."

     

    When I look at the "In from AD - User Join" and the scoping filter shows isCriticalSystemObject has a value of "TRUE" … so according to the statement above this rule is NOT in scope? the double negative is confusing me, also because User Join sounds like its something that SHOULD be in scope right?

VasilMichev's avatar
VasilMichev
MVP

It can simply be filtered by one of the default (or custom) rules. You should see which of those affect the object when you run the preview/commit. And do force a Full sync as some changes might not be reflected upon delta.

ch0wd0wn's avatar
ch0wd0wn
Copper Contributor
Dec 19, 2019

VasilMichev  Ok I will check that but how can I tell which rule is applying during the preview?  Sorry I'm very new at this

Resources