Can I limit the Excludes that are applied during the Discovery phase?

Yes.

By default, when you utilize the Exclude feature, the exclusions are applied during Discovery. This means that those objects excluded will not be present in your Discovery log Record count or ldif.txt file.

One situation where you may want to force exclusions to process during the Sync phase rather than Discovery is with One to Many configurations. You may want the Discovery of your one connection to pull all Source records, yet process the necessary Excludes on the Sync phase if they differ for each Destination.

To limit the Excludes that are applied during the Discovery phase, you’ll add a parameter to your Raw Config on the Custom tab:

exclude-filter=attribute1,attribute2 ...

When this parameter is set in Raw Config, Excludes on Discovery are limited to just those attributes identified.

In either case the following exclude-filter settings are recommended:

exclude-filter=none

This disables Excludes entirely during the Discovery phase, and forces all to process during Sync

exclude-filter=dn

This will process only DN Excludes during the Discovery phase

Of course you may configure this parameter to specify any attribute that meets your needs.