DLConversionV2 icon indicating copy to clipboard operation
DLConversionV2 copied to clipboard

DL Migration fails because of duplicate recipients

Open daimhin opened this issue 9 months ago • 2 comments

I have been working on doing my first migration and setup a test group that mirrors one of my production groups. When I ran the migration command, it built the group in Exchange Online, but it threw an error on two entries and logged the migration as failed. The log entries I got for one of the users is:

[4/25/2024 5:04:41 PM] - =====
[4/25/2024 5:04:41 PM] - Post Create Errors:
[4/25/2024 5:04:41 PM] - Primary Email Address or UPN: [email protected]
[4/25/2024 5:04:41 PM] - External Directory Object ID: d9f2b055-9f61-4120-8dc1-6257687e3fc4
[4/25/2024 5:04:41 PM] - Name: AHC_TEA_TEST
[4/25/2024 5:04:41 PM] - Alias: AHC_TEA_TEST
[4/25/2024 5:04:41 PM] - Attribute in Error: Cloud Distribution Group Member
[4/25/2024 5:04:41 PM] - Error Message: Member [email protected] unable to add to cloud distribution group.  Manual addition required.
[4/25/2024 5:04:41 PM] - Error Message Details: Ex8155FB|Microsoft.Exchange.Configuration.Tasks.ManagementObjectAmbiguousException|There are multiple recipients matching the identity "[email protected]". Please specify a unique value.
[4/25/2024 5:04:41 PM] - =====

The two errors were for cross-forest contacts that had been added to the group. I thought this might be the issue, but there is a third cross-forest contact in the group that migrated correctly. These contacts have been synced to the tenant and are available there as a contact. When I ran the Get-Recipient cmdlet for the email address it returns two results. One is the contact, but the other is a guest account where the user has been invited into a team in the tenant.

Name                                 RecipientType
----                                 -------------
username_domain.com#EXT#             MailUser
d80e7381-4895-4d0e-9803-b099fa26c792 MailContact

I can manually add the user to the migrated group afterwards, but would like to figure out if there is any way to resolve this during the migration process.

daimhin avatar Apr 29 '24 23:04 daimhin