Sign-in & Login Problems

Change a Synced Microsoft 365 UPN with Azure AD Connect

Ayan MasoodAyan Masood Nov 14, 2026 868 views

Question details

Change a synchronized Microsoft 365 sign-in name to match the user's primary email address.

Change a Synced Microsoft 365 UPN with Azure AD Connect
Product
Microsoft 365 and Microsoft Entra Connect Sync (formerly Azure AD Connect)
Device & OS
not provided
Scenario
A user's account is synchronized from on-premises Active Directory, and its sign-in name should match its primary SMTP address.
Observed behavior
The desired sign-in name should synchronize from on-premises Active Directory without conflicting with the existing sync or federation setup.
Before you start

Confirm the user's primary SMTP address and verify that its domain is verified in Microsoft Entra ID. Check whether the domain is federated and coordinate the change with the identity administrator, since the user may need to sign in again.

Solution 1Recommended

Change the UPN in on-premises Active Directory

Use this method when the user's sign-in name is synchronized from on-premises Active Directory.

For a synchronized user, make the UPN change in the source directory rather than relying on a direct cloud change. Matching the UPN to the primary SMTP address is generally recommended, but changing the UPN does not itself change the email address.

1
Check the UPN suffix

Open Active Directory Users and Computers and locate the user. If the email domain is not available as a UPN suffix, add it under Active Directory Domains and Trusts > Properties > Alternative UPN suffixes.

2
Update the user account

In Active Directory Users and Computers, open the user's Properties > Account. Set the user logon name and suffix to match the primary email address, then select OK.

3
Synchronize the change

Allow the next scheduled synchronization cycle to run. Alternatively, on the Microsoft Entra Connect server, open PowerShell with the required permissions and run Start-ADSyncSyncCycle -PolicyType Delta.

4
Verify the sign-in name

In the Microsoft Entra admin center, open Identity > Users > All users and check the user's updated sign-in name. Ask the user to sign in with the new name after synchronization completes.

Change the UPN in on-premises Active Directory
Check federation and application dependencies: Federated sign-in and applications that use the UPN may require additional coordination. Adding an Active Directory UPN suffix does not verify the domain in Microsoft Entra ID.
Free Microsoft Office alternative

Document Sign-in Changes with WPS Office

WPS Office is a free, lightweight Office alternative with a familiar interface and compatible file formats for a smooth move from Microsoft Office. It can help you document sign-in changes, but it does not change Microsoft 365 identity or synchronization settings.

Document UPN changes and user sign-in instructions in WPS WriterOpen and edit Microsoft Word DOCX filesUse a familiar interface to work with existing Office documentsGet a free, lightweight suite for everyday document work
microsoft office alternative - wps office

Frequently Asked Questions

Should I change a synced user's UPN directly in Microsoft 365?

For a user synchronized from on-premises Active Directory, change the UPN in Active Directory Users and Computers > user Properties > Account, then let Microsoft Entra Connect synchronize it.

Does changing the UPN also change the user's email address?

No. The UPN is a sign-in name, while the primary SMTP address is an email attribute. Check the primary SMTP address separately before matching the UPN to it.

What if the email domain is missing from the UPN suffix list?

Add the suffix in Active Directory Domains and Trusts > Properties > Alternative UPN suffixes. Also confirm that the domain is verified in Microsoft Entra ID before using it for the cloud sign-in name.

Can users sign in with an attribute other than their UPN?

An alternate login ID can be configured in supported environments. Review the Microsoft Entra Connect and federation configuration with your identity administrator before changing the sign-in attribute.