In Azure, users from other tenants can have different identity objects such as a guest account, mail contacts, or licensed accounts. In this post, we will discuss how to ensure a single representation of a user in the resource tenant for B2B collaboration.
1. Users with pending acceptance invitation: If a user was invited as a guest but never accepted the invitation, the cross-tenant sync may fail. You can resend the invitation to resolve this issue.
2. Multiple guest accounts with pending acceptance: Sometimes, multiple accounts are created for a user in the home tenant. It is recommended to retain the account that matches the primary SMTP address and delete the others.
3. Multiple guest accounts with accepted and pending acceptance: Similar to the previous scenario, one account may be accepted while the other is still pending. It is advisable to keep the account in the accepted state.
4. Contact object: A user may be added as a contact in the resource tenant. To achieve a single representation, capture the Legacy Exchange DN and group memberships and then delete the contact object.
5. Contact & B2B object: Users can be added as both a contact and a B2B object. If the B2B object’s invitation state is pending, delete the
