Hello!
We are seeing a strange behavior and I found some indirect references about it in MS documentation. I want to get some better visibility into it so that we can appropriately approach it:
1. We deployed AAD Connect with group based filtering for a set of Pilot users.
2. However, we observed that a lot of groups also got synced although they were not member of the Pilot group for filtering. (The groups existed in AD and AAD but the membership differed.)
3. After further investigations, we got to know that a long time back DirSync was deployed but later on the sync was discontinued.
4. I find following documentation referring to the in scope of objects for filtering. Based on its language it sounds like even though we are using a group based filtering for our pilot, the original scope of sync with DirSync might be still interfering.
"Azure AD Connect only deletes objects that it has once considered to be in scope. If there are objects in Azure AD that were created by another sync engine and these objects aren't in scope, adding filtering doesn't remove them. For example, if you start with a DirSync server that created a complete copy of your entire directory in Azure AD, and you install a new Azure AD Connect sync server in parallel with filtering enabled from the beginning, Azure AD Connect doesn't remove the extra objects that are created by DirSync."
5. Can you explicitly confirm that stale configurations with DirSync are interfering with our new AAD Connect setup? If yes, will recreating these objects in AAD will resolve the issue?
Thanks!!