You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By using filtering, you can control which objects appear in Azure Active Directory (Azure AD) from your on-premises directory. The default configuration takes all objects in all domains in the configured forests. In general, this is the recommended configuration. Users using Microsoft 365 workloads, such as Exchange Online and Skype for Business, benefit from a complete Global Address List so they can send email and call everyone. With the default configuration, they would have the same experience that they would have with an on-premises implementation of Exchange or Lync.
22
22
23
-
In some cases however, you're required make some changes to the default configuration. Here are some examples:
23
+
In some cases however, you're required to make some changes to the default configuration. Here are some examples:
24
24
25
25
* You run a pilot for Azure or Microsoft 365 and you only want a subset of users in Azure AD. In the small pilot, it's not important to have a complete Global Address List to demonstrate the functionality.
26
26
* You have many service accounts and other nonpersonal accounts that you don't want in Azure AD.
@@ -81,118 +81,13 @@ You can use multiple filtering options at the same time. For example, you can us
81
81
## Domain-based filtering
82
82
This section provides you with the steps to configure your domain filter. If you added or removed domains in your forest after you installed Azure AD Connect, you also have to update the filtering configuration.
83
83
84
-
The preferred way to change domain-based filtering is by running the installation wizard and changing[domain and OU filtering](how-to-connect-install-custom.md#domain-and-ou-filtering). The installation wizard automates all the tasks that are documented in this topic.
84
+
To change domain-based filtering, run the installation wizard:[domain and OU filtering](how-to-connect-install-custom.md#domain-and-ou-filtering). The installation wizard automates all the tasks that are documented in this topic.
85
85
86
-
You should only follow these steps if you're unable to run the installation wizard for some reason.
87
86
88
-
Domain-based filtering configuration consists of these steps:
89
-
90
-
1. Select the domains that you want to include in the synchronization.
91
-
2. For each added and removed domain, adjust the run profiles.
92
-
3.[Apply and verify changes](#apply-and-verify-changes).
93
-
94
-
### Select the domains to be synchronized
95
-
There are two ways to select the domains to be synchronized:
96
-
- Using the Synchronization Service
97
-
- Using the Azure AD Connect wizard.
98
-
99
-
100
-
#### Select the domains to be synchronized using the Synchronization Service
101
-
To set the domain filter, do the following steps:
102
-
103
-
1. Sign in to the server that is running Azure AD Connect sync by using an account that is a member of the **ADSyncAdmins** security group.
104
-
2. Start **Synchronization Service** from the **Start** menu.
105
-
3. Select **Connectors**, and in the **Connectors** list, select the Connector with the type **Active Directory Domain Services**. In **Actions**, select **Properties**.
5. In the **Select directory partitions** list, select and unselect domains as needed. Verify that only the partitions that you want to synchronize are selected.
109
-

110
-
If you've changed your on-premises Active Directory infrastructure and added or removed domains from the forest, then click the **Refresh** button to get an updated list. When you refresh, you're asked for credentials. Provide any credentials with read access to Windows Server Active Directory. It doesn't have to be the user that is prepopulated in the dialog box.
6. When you're done, close the **Properties** dialog by clicking **OK**. If you removed domains from the forest, a message pop-up says that a domain was removed and that configuration will be cleaned up.
113
-
7. Continue to adjust the run profiles.
114
-
115
-
#### Select the domains to be synchronized using the Azure AD Connect wizard
116
-
To set the domain filter, do the following steps:
117
-
118
-
1. Start the Azure AD Connect wizard
119
-
2. Click **Configure**.
120
-
3. Select **Customize Synchronization Options** and click **Next**.
121
-
4. Enter your Azure AD credentials
122
-
5. On the **Connected Directories** screen click **Next**.
123
-
6. On the **Domain and OU filtering page** click **Refresh**. New domains will now appear and deleted domains will disappear.
If you've updated your domain filter, you also need to update the run profiles.
128
-
129
-
1. In the **Connectors** list, make sure that the Connector that you changed in the previous step is selected. In **Actions**, select **Configure Run Profiles**.
130
-

131
-
2. Find and identify the following profiles:
132
-
* Full Import
133
-
* Full Synchronization
134
-
* Delta Import
135
-
* Delta Synchronization
136
-
* Export
137
-
3. For each profile, adjust the **added** and **removed** domains.
138
-
1. For each of the five profiles, do the following steps for each **added** domain:
139
-
1. Select the run profile and click **New Step**.
140
-
2. On the **Configure Step** page, in the **Type** drop-down menu, select the step type with the same name as the profile that you're configuring. Then click **Next**.
141
-

142
-
3. On the **Connector Configuration** page, in the **Partition** drop-down menu, select the name of the domain that you've added to your domain filter.
143
-

144
-
4. To close the **Configure Run Profile** dialog, click **Finish**.
145
-
2. For each of the five profiles, do the following steps for each **removed** domain:
146
-
1. Select the run profile.
147
-
2. If the **Value** of the **Partition** attribute is a GUID, select the run step and click **Delete Step**.
148
-

149
-
3. Verify your change. Each domain that you want to synchronize should be listed as a step in each run profile.
150
-
4. To close the **Configure Run Profiles** dialog, click **OK**.
151
-
5. To complete the configuration, you need to run a **Full import** and a **Delta sync**. Continue reading the section [Apply and verify changes](#apply-and-verify-changes).
152
87
153
88
## Organizational unit–based filtering
154
-
The preferred way to change OU-based filtering is by running the installation wizard and changing [domain and OU filtering](how-to-connect-install-custom.md#domain-and-ou-filtering). The installation wizard automates all the tasks that are documented in this topic.
155
-
156
-
You should only follow these steps if you're unable to run the installation wizard for some reason.
157
-
158
-
To configure organizational unit–based filtering, do the following steps:
159
-
160
-
1. Sign in to the server that is running Azure AD Connect sync by using an account that is a member of the **ADSyncAdmins** security group.
161
-
2. Start **Synchronization Service** from the **Start** menu.
162
-
3. Select **Connectors**, and in the **Connectors** list, select the Connector with the type **Active Directory Domain Services**. In **Actions**, select **Properties**.
4. Click **Configure Directory Partitions**, select the domain that you want to configure, and then click **Containers**.
165
-
5. When you're prompted, provide any credentials with read access to your on-premises Active Directory. It doesn't have to be the user that is prepopulated in the dialog box.
166
-
6. In the **Select Containers** dialog box, clear the OUs that you don’t want to synchronize with the cloud directory, and then click **OK**.
167
-

168
-
* The **Computers** container should be selected for your Windows 10 computers to be successfully synchronized to Azure AD. If your domain-joined computers are located in other OUs, make sure those are selected.
169
-
* The **ForeignSecurityPrincipals** container should be selected if you have multiple forests with trusts. This container allows cross-forest security group membership to be resolved.
170
-
* The **RegisteredDevices** OU should be selected if you enabled the device writeback feature. If you use another writeback feature, such as group writeback, make sure these locations are selected.
171
-
* Select any other OU where Users, iNetOrgPersons, Groups, Contacts, and Computers are located. In the picture, all these OUs are located in the ManagedObjects OU.
172
-
* If you use group-based filtering, then the OU where the group is located must be included.
173
-
* Note that you can configure whether new OUs that are added after the filtering configuration finishes are synchronized or not synchronized. See the next section for details.
174
-
7. When you're done, close the **Properties** dialog by clicking **OK**.
175
-
8. To complete the configuration, you need to run a **Full import** and a **Delta sync**. Continue reading the section [Apply and verify changes](#apply-and-verify-changes).
176
-
177
-
### Synchronize new OUs
178
-
New OUs that are created after filtering has been configured are synchronized by default. This state is indicated by a selected check box. You can also unselect some sub-OUs. To get this behavior, click the box until it becomes white with a blue check mark (its default state). Then unselect any sub-OUs that you don't want to synchronize.
179
-
180
-
If all sub-OUs are synchronized, then the box is white with a blue check mark.
181
-

182
-
183
-
If some sub-OUs have been unselected, then the box is gray with a white check mark.
184
-

185
-
186
-
With this configuration, a new OU that was created under ManagedObjects is synchronized.
187
-
188
-
The Azure AD Connect installation wizard always creates this configuration.
189
-
190
-
### Don't synchronize new OUs
191
-
You can configure the sync engine to not synchronize new OUs after the filtering configuration has finished. This state is indicated in the UI by the box appearing solid gray with no check mark. To get this behavior, click the box until it becomes white with no check mark. Then select the sub-OUs that you want to synchronize.
192
-
193
-

89
+
To change OU-based filtering, run the installation wizard: [domain and OU filtering](how-to-connect-install-custom.md#domain-and-ou-filtering). The installation wizard automates all the tasks that are documented in this topic.
194
90
195
-
With this configuration, a new OU that was created under ManagedObjects isn't synchronized.
196
91
197
92
## Attribute-based filtering
198
93
Make sure that you're using the November 2015 ([1.0.9125](reference-connect-version-history.md)) or later build for these steps to work.
0 commit comments