In this section, we'll use the standard filtering options to exclude users and groups to be synchronized to the metaverse:

1. Log in as domain administrator to your YD1ADS01.
2. Open the Active Directory Users and Computers console (dsa.msc).
3. Be sure that you are in the advanced features view:

4. Choose one of your users and move to the Attribute Editor tab.
5. Edit the adminDescription attribute and enter User_NoSync, where User_ is the important part:

6. Save your settings and minimize the console.
7. Open the Synchronization Rules Editor.
8. Edit the rule In from AD - User Common.
9. Click on Scoping filter.
10. You'll see a Scoping filter with the following clause:

adminDescription NOTSTARTSWITH User_

The following screenshot shows the configuration to filter users to synchronize to Azure AD by filling the adminDescription attribute:

11. Click Cancel and minimize the synchronization rules editor.
12. Open the Synchronization Service Manager.
13. Click on Connectors and start a delta import on your Active Directory connector.
14. You'll get an update in the sync statistics:

15. Click on Updates.
16. You'll notice add on your modified user account:

17. Click on Preview.
18. Choose Delta Synchronization.
19. Click Generate Preview:

20. You'll see in the result that the Object Deletion Rule was satisfied:

21. Click on Connector Deprovisioning:

22. The object will be disconnected.
23. Click Close.
24. Click Preview.
25. Chose Delta synchronization.

26. Click Commit Preview:

27. Open a Metaverse Search:

28. Click Search.
29. Aaron Painter no longer exists in the Metaverse.
30. Run an Export on the Azure AD connector:

31. You'll get a delete in the sync statistics.
32. Click Deletes:

33. Click on the object GUID:

34. Your user will be deleted from the Azure AD.
35. You'll see Awaiting Export Confirmation.
36. Run delta import on the Azure AD connector.
37. The object will be deleted in the connector space of the Azure AD connector:

38. Run delta sync on the Azure AD connector to finish the change.
39. Open the connector space on the Azure AD connector. You won't find the preceding CN=:

With this option, you've seen that you can filter objects in a filter OU by filling the adminDescription attribute with User_NoSync. The same procedure can be used to filter groups with Group_NoSync, for example. Here, you can find the specific In from AD—Group Common inbound rule, which is shown in the following screenshot:

In the next example, we'll build a custom rule.