Submitting forms on the support site are temporary unavailable for schedule maintenance. If you need immediate assistance please contact technical support. We apologize for the inconvenience.
After configuring an Exchange online and Azure AD sync project, both of which are syncing the same set of objects in Azure AD, there was a discrepancy in the number of objects.
원인
The difference results from exchange "internal" objects. These are linked to AADUser like all others, but are managed exclusively by Microsoft.
해결 방안
With the AAD Connector the Graph-API is used, there these objects are filtered out. With the O3E (Exchange) Connector these are retrieved via a Powershell cmdlet.
This schema class is not used directly for a mapping, but to get the correct assignment of the mailboxes to the AAD users. This means that these objects do not appear anywhere on the OIM page, since they are also filtered for the mailbox itself.
Specifically, it is about the objects with the RecipientTypeDetails = DiscoveryMailbox