Problem "duplication attribute" with first Azure AD Connect Sync

Question

Problem "duplication attribute" with first Azure AD Connect Sync

Allan Stark 561

I'm syncing the local AD with the Azure AD.
Many accounts have been created in the Azure AD for a long time and used cloud services (ExO, SharePoint etc.).

Local domain: company.local, added additional UPN suffix "company.com"
AzureAD: company.com (as primary domain)

Three users have local UPN suffixes which are different from the Azure AD.

Azure AD Connector shows the following error for all these accounts:

"proxyAddress" field in their local AD account is empty, but the "mail" field contains the correct address.
Also I see that error in the "Azure Active Directory Connect Health" tool on the Azure website:

Questions:

How to solve this problem?
How to leave UPN in the O365 cloud the same as it was before the synchronization attempt?
Because I tried to apply the fix ("Troubleshoot" in "Azure Active Directory Connect Health") for a test account with a similar problem and this led to the replacement of the UPN suffix with the one that was in the local AD domain. This will most likely lead to the need to change the settings for connecting to the O365 on users' devices, which is undesirable.
Can I use "Set-MsolUserPrincipalName" PowerShell comandlet after successfully AD sync to solve #2?

Marilee Turscak-MSFT 37,271 Reputation points Microsoft Employee Moderator

2021-02-05T20:28:55.017+00:00
If the UPN was changed after the initial synchronization it must be updated manually.

Manually update a user account UPN

Install Azure Active Directory V2 PowerShell Module. For more information, see Azure Active Directory V2 PowerShell Module.

Run the following cmdlets at the Azure Active Directory V2 PowerShell prompt: $cred = get-credential

When you're prompted, enter your admin credentials.

Connect-AzureAD Set-AzureADUser -ObjectId [CurrentUPN] -UserPrincipalName [NewUPN]

(Or if you wanted to keep the local UPN you could delete the cloud version, make sure the on-prem version is correct, and do a re-sync)
Emily Hua-MSFT 27,876 Reputation points

2021-02-08T01:45:29.097+00:00

@Allan Stark
As your issue is more realted to Azure AD instead of Office Online Server, I would remove the tag "office-online-server-general".
Thanks for your understanding.

1 answer

Your answer

Marilee Turscak-MSFT 37,271 Reputation points Microsoft Employee Moderator

2021-02-05T20:28:55.017+00:00

If the UPN was changed after the initial synchronization it must be updated manually.

Manually update a user account UPN

Install Azure Active Directory V2 PowerShell Module. For more information, see Azure Active Directory V2 PowerShell Module.

Run the following cmdlets at the Azure Active Directory V2 PowerShell prompt: $cred = get-credential

When you're prompted, enter your admin credentials.

Connect-AzureAD Set-AzureADUser -ObjectId [CurrentUPN] -UserPrincipalName [NewUPN]

(Or if you wanted to keep the local UPN you could delete the cloud version, make sure the on-prem version is correct, and do a re-sync)
Emily Hua-MSFT 27,876 Reputation points

2021-02-08T01:45:29.097+00:00

@Allan Stark
As your issue is more realted to Azure AD instead of Office Online Server, I would remove the tag "office-online-server-general".
Thanks for your understanding.

Answer 1

Allan Stark 561

Thank you for your answer.

What is the difference between Set-AzureADUser cmdlet and Set-MsolUserPrincipalName from MSOnline module?

It seems to also allow to change UPN name by:
Set-MsolUserPrincipalName -UserPrincipalName [CurrentUPN] -NewUserPrincipalName [NewUPN]

Vipul Sparsh 16,331 Reputation points Microsoft Employee Moderator

2021-02-26T14:11:53.31+00:00

@Allan Stark Set-MsolUserPrincipalName is part of an older powershell v1 module which is not getting any further updates.
the recommendation is to start using V2 module with Azure AD powershell modules.

----------

Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.

Share via

Problem "duplication attribute" with first Azure AD Connect Sync

1 answer

Your answer