Microsoft Online Directory Synchronization In-Depth Download

The information contained in this document is not supported by Microsoft and making any
of the modifications mentioned in the document violates the Directory Synchronization
EULA. We have therefore decided to not make it publically available at this time. If you
would like a copy of the document, please contact MessageOps directly and we'll be happy
to provide you with a copy. Below is a small excerpt from the document to give you an idea
of the type of information it contains.

If you have additional questions,
please don't hesitate to contact us.
Remember that in most cases
MessageOps services are free to
our clients, so you have nothing to
lose by reaching out to us.

In the Configure Connector filter settings, you will find the logic that is used to determine
which objects are synchronized to Microsoft Online. The rules for synchronizing Users and
inetOrgPerson objects are visible in the GUI. If an object matches any of the criteria it is not
synchronized. The default rules for filtering user objects are shown below.

So you can see that if an object does not have the SamAccountName populated, it will not be
synchronized. There is an additional attribute which must be present for an object to
synchronize, DisplayName. If DisplayName is not populated, the user object will be
synchronized to the Metaverse, but not to Microsoft Online. Using this information you could
develop a supported way to exclude certain user objects from the directory sync. One such
way would be to change the mailNickName of the objects you want to exclude to
SystemMailbox{some unique value such as SamAccountname}. If you are currently using
Exchange, you can't just change the mailNickName attribute, without making other
modifications to the user object, so please contact MessageOps for guidance if you want to
make the change and a script that will automate the process.