Forum Discussion
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...
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?
Check that these properties are populated on the user account:
- Mail/Windows Mail
- MailNickname/Alias
- EmailAddress
Even if the user account is not going to have mail, it can keep the account from syncing.
Steve Mahoneythanks so much, I checked and all those attributes are filled out
