How to Resolve Azure AD Connect Duplicate UPN and SMTP Address Errors
Question details
Administrator needs to resolve directory synchronization failures caused by duplicate UserPrincipalName (UPN) or SMTP attributes.
- Product
- Azure AD Connect
- Device & OS
- not provided
- Scenario
- Changing a synchronized user's primary email address while simultaneously converting another mailbox to a shared mailbox.
- Observed behavior
- Directory synchronization fails because the same UPN or SMTP proxy address exists on more than one directory object.
Ensure you have global administrator or Exchange administrator privileges in Microsoft 365, as well as Domain Admin rights in your local Active Directory to modify user attributes.
Assign Temporary Addresses and Force Delta Synchronization
Resolve the conflict by assigning a temporary address to the shared mailbox in Microsoft 365, updating the synchronized user in Active Directory, and forcing a delta sync.
To prevent duplicate attribute errors, you must ensure that a UPN or SMTP address is completely freed from one object before assigning it to another. This requires a sequenced update and synchronization process.
In the Microsoft 365 Admin Center, navigate to Groups > Shared mailboxes. Assign the shared mailbox a temporary, unused UPN and SMTP address. Confirm that no other user, alias, or directory object is currently using the desired primary addresses.
Open Active Directory Users and Computers (ADUC) on your on-premises server. Locate the synchronized user account, open its Properties, and update the UPN and proxyAddresses attributes to the new target email address.
Open PowerShell as an Administrator on your Azure AD Connect server and execute the command: Start-ADSyncSyncCycle -PolicyType Delta. Wait for the synchronization cycle to complete.
Once the sync finishes, verify that the synchronized user's address has updated successfully in Microsoft 365. Finally, update the shared mailbox with its permanent address and check for any remaining duplicate attributes before the next sync.
Manage Your IT Documentation Efficiently with WPS Office
While resolving Azure AD Connect sync issues requires Microsoft administrative tools, managing your IT infrastructure documentation, sync logs, and migration plans shouldn't require an expensive software subscription. WPS Office provides a lightweight, comprehensive, and free alternative that feels highly familiar to Office users.
Frequently Asked Questions
Do existing emails get deleted when I change the UPN and SMTP address?
No. Changing the UserPrincipalName (UPN) or SMTP address only affects the login credentials and email routing. The underlying mailbox data, including all existing emails, folders, and rules, remains completely intact.
Where should I change the primary SMTP address for a shared mailbox?
If the shared mailbox is managed directly in the cloud, its SMTP address should be changed in the Microsoft 365 Admin Center under Teams & Groups > Shared mailboxes. If it is synchronized from an on-premises Exchange environment, changes must be made in the local Active Directory.
How long does it take for Azure AD Connect synchronization to apply the changes?
When manually triggering a delta sync using the PowerShell command, the changes usually reflect in Microsoft 365 within a few minutes, depending on the size of your Active Directory and current network latency.
Why do I get a directory sync error when converting a mailbox?
This typically occurs if you assign an email address or UPN to a new object before the Azure AD Connect sync cycle has successfully cleared it from the old object, resulting in a duplicate attribute conflict in the cloud directory.
