Microsoft 365 Certified: Administrator ExpertImplement and manage Microsoft Entra IDMedium
A company is implementing Microsoft Entra Connect to synchronize users from a single on-premises Active Directory forest to Microsoft Entra ID. They need to ensure that only users whose 'department' attribute is set to 'Sales' or 'Marketing' are synchronized. Which filtering method should be used?
- AOrganizational Unit (OU) filtering
- BGroup-based filtering
- CAttribute-based filtering
- DDomain-based filtering
Show answer & explanationAnswer & explanation
Correct answer: C. Attribute-based filtering
Attribute-based filtering allows you to filter objects based on the values of specific attributes, such as the 'department' attribute. This method is ideal for scenarios where you need granular control over which users are synchronized based on their properties, matching the requirement to sync only users in 'Sales' or 'Marketing' departments.
Why the other options are wrong
- A. OU filtering excludes entire OUs, which might contain users from other departments.
- B. Group-based filtering is typically used for pilot deployments or specific scenarios, not for broad departmental filtering.
- D. Domain-based filtering applies to entire domains, not specific departments within them.
Microsoft Entra Connect Attribute Filtering
Attribute filtering in Microsoft Entra Connect allows administrators to define which objects are synchronized to Microsoft Entra ID based on the values of their attributes.
- Provides granular control over object synchronization.
- Configured using synchronization rules in the Synchronization Service Manager.
- Useful for filtering based on properties like department, company, or custom attributes.
Memory trick: Filter by OU, Attribute, or Domain to control what goes to the cloud.