In Azure, users from other tenants can have different identity representations. Most users have a cloud guest account, some also have Mail contacts, and a few have licensed accounts. We will discuss how to merge these representations to have a single user representation in the resource tenant for B2B collaboration and Exchange integration.
1. GUEST ACCOUNT WITH PENDING ACCEPTANCE INVITATION:
Users who are invited as guests but never accepted the invitation will not sync cross-tenants. To enable synchronization, you can resend the invite to populate the unique identifier.
2. MULTIPLE GUEST ACCOUNTS WITH PENDING ACCEPTANCE INVITATION:
If a user has multiple accounts in the home tenant and is invited in the resource tenant with both email addresses, it is recommended to retain the account matching the home account’s primary SMTP address.
3. MULTIPLE GUEST ACCOUNTS WITH DIFFERENT INVITATION STATES:
For users with accepted and pending acceptance invitations, keep the account with accepted status for continuity in permissions and update the email address accordingly.
4. EXISTING CONTACT OBJECT:
A user may be added as a contact in the resource tenant when GAL Sync is configured. To have a single representation, capture Distinguished Name and group memberships from the contact object
