Fix Office 365 Primary Email Address Reverting to onmicrosoft.com
Question details
Users need to stop synchronized Microsoft 365 primary email addresses from reverting to the default @onmicrosoft.com domain.
- Product
- Office 365
- Device & OS
- not provided
- Scenario
- Managing user attributes in a hybrid environment where local Active Directory accounts sync to Microsoft 365.
- Observed behavior
- The primary email address ignores the local proxy address configuration and continuously reverts to the default @onmicrosoft.com domain even after directory synchronization is forced.
Ensure you have Domain Administrator privileges in your local Active Directory environment and the necessary Global Administrator rights in your Microsoft 365 tenant to perform attribute edits and force Azure AD synchronization.
Update Proxy Addresses via Active Directory Administrative Center
Use the AD Administrative Center to correctly format and apply the primary SMTP address, which overrides the cloud default during synchronization.
In a hybrid environment, the local Active Directory acts as the source of authority. If the proxyAddresses attribute is missing, incorrectly formatted, or hidden in the standard AD Users and Computers view, the Microsoft 365 cloud environment will default to the onmicrosoft.com routing address.
Launch the Active Directory Administrative Center on your domain controller, as standard AD interfaces may hide certain advanced attributes.
Search for the affected synchronized user account and open its properties window.
Navigate to the Extensions tab or Attribute Editor to find the proxyAddresses attribute. Add the correct primary email address using an uppercase prefix (e.g., SMTP:user@domain.com) and ensure secondary aliases use a lowercase prefix (e.g., smtp:alias@domain.com).
Check the targetAddress attribute to ensure it matches the correct primary routing address and remove any obsolete onmicrosoft.com entries.
Open an elevated PowerShell prompt on your Azure AD Connect server and run 'Start-ADSyncSyncCycle -PolicyType Delta' to force synchronization, then verify the result in the Microsoft 365 Admin Center.
Use PowerShell to Set the MsolUserPrincipalName
Manually update the User Principal Name in Microsoft 365 via PowerShell if the local sync isn't updating the cloud sign-in address properly.
Looking for a Simpler Office Solution? Try WPS Office
Managing complex hybrid environments, Active Directory syncs, and Exchange attributes can be overwhelming. If you are looking for a straightforward, hassle-free desktop productivity suite for your daily document needs, WPS Office provides powerful Word, Excel, and PowerPoint alternatives without the complicated cloud management overhead.
- 1. Visit the WPS Office Website: Navigate to the official WPS Office website to download the latest free version of the suite.
- 2. Install the Software: Run the lightweight installer on your device to set up the Word, Excel, and PowerPoint alternatives.
- 3. Open Your Documents: Double-click any existing Microsoft Office files to seamlessly open and edit them in WPS Office with full formatting retention.
Frequently Asked Questions
Why does my email alias use a lowercase 'smtp' while the primary uses uppercase 'SMTP'?
In Active Directory proxy addresses, the uppercase 'SMTP:' strictly defines the primary email address used for sending outbound emails. The lowercase 'smtp:' designates secondary proxy addresses or aliases that can receive inbound emails but will not be the default sending address.
Can I edit the proxyAddresses attribute from the standard Active Directory Users and Computers console?
Yes, but you must first enable 'Advanced Features' under the View menu to make the Attribute Editor tab visible in the user's properties. If it is still missing or difficult to manage, the Active Directory Administrative Center provides a more robust interface.
What should I do if a cloud account was incorrectly merged and keeps reverting the email?
If an incorrectly created cloud account was merged with an on-premises AD account, legacy cloud attributes might continuously overwrite the synced values. You may need to clear the immutable ID, hard-delete the problematic cloud object, and allow Azure AD Connect to provision a fresh, correctly linked account during the next sync cycle.
