'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Remove an onmicrosoft.com Address from a Synced User in Exchange
Question details
The user needs to remove an unwanted onmicrosoft.com email alias that continues to display for a synced user in Outlook or Teams.
- Product
- Microsoft Exchange Online, Outlook, Teams
- Device & OS
- not provided
- Scenario
- An organization using a custom domain as the primary email address notices that an onmicrosoft.com address still appears for a user. Standard Exchange admin center deletion fails because the account is mastered on-premises.
- Observed behavior
- The onmicrosoft.com address persists in Outlook and Teams, and attempts to remove it via the Exchange admin center are blocked due to on-premises directory mastering.
Ensure you have administrative access to your on-premises Active Directory and the server running Azure AD Connect to modify directory attributes and initiate a manual synchronization.
Update On-Premises Attributes and Run Delta Synchronization
Since the user object is mastered on-premises, you must modify the proxyAddresses attribute locally and force an Azure AD Connect sync to push the changes to Microsoft Entra ID and Exchange Online.
When user accounts are synchronized from an on-premises Active Directory to Microsoft 365, attributes like email aliases are strictly controlled by the local AD environment. Any modifications must be made there and synchronized upward.
Open Active Directory Users and Computers (ADUC) on your on-premises server. Ensure 'Advanced Features' is enabled under the View menu. Right-click the affected user, select 'Properties', and navigate to the 'Attribute Editor' tab. Locate the 'proxyAddresses' attribute and remove the unwanted onmicrosoft.com address.
Open an elevated PowerShell prompt on the server running Azure AD Connect. Execute the command `Start-ADSyncSyncCycle -PolicyType Delta` to force a synchronization of your recent on-premises changes to the cloud.
Wait a few minutes for the changes to replicate to Microsoft Entra ID and Exchange Online. Check the user's profile in the Microsoft 365 admin center or Exchange admin center to confirm the address has been successfully removed.
Looking for a Lightweight Alternative for Your Organization's Documents?
While resolving complex enterprise email and directory sync issues, you might also be looking for a highly compatible, cost-effective office suite for your organization's daily document needs. WPS Office offers a lightweight, free alternative that easily integrates with your existing workflows.
- 1. Download WPS Office: Navigate to the official WPS website and download the installation package tailored to your Windows, Mac, or Linux operating system.
- 2. Install the Suite: Run the setup file and follow the standard on-screen prompts to deploy the lightweight office suite on your workstation.
- 3. Open Existing Microsoft Formats: Launch WPS Office and directly open your existing .docx, .xlsx, or .pptx files to enjoy seamless format compatibility without needing any conversions.
Frequently Asked Questions
Why can't I delete the onmicrosoft.com address directly in the Exchange Admin Center?
When your organization uses Azure AD Connect for directory synchronization, the authoritative source for user attributes is your on-premises Active Directory. The Exchange Admin Center blocks cloud-side edits to prevent data conflicts and overwrites during the next sync cycle.
What happens if the onmicrosoft.com address still appears after running the delta sync?
If the address persists, double-check the 'proxyAddresses' and 'targetAddress' attributes in your on-premises AD to ensure the alias was fully removed. Additionally, check if an on-premises Email Address Policy is automatically re-applying the alias.
How long does it take for Outlook and Teams to update after the address is removed?
While the cloud directory updates relatively quickly after the Azure AD Connect sync completes, offline clients like Outlook rely on the Offline Address Book (OAB), which typically updates once every 24 hours. Teams caching can also take up to 24-48 hours to clear entirely.
Where can I get help if the synchronization completely fails?
If synchronization fails, you can review the sync logs in the Synchronization Service Manager on your Azure AD Connect server. For further assistance, submit a request through the Microsoft Entra ID support forum or Microsoft 365 admin center.
