logo
search
Send & Receive Issues

Fix Microsoft 365 External Out of Office Replies Sending from onmicrosoft.com Domain

Tauseeq MagsiTauseeq Magsi Oct 19, 2026 869 views

Question details

Users migrating from Exchange 2010 to Microsoft 365 in a hybrid setup are experiencing an issue where external automatic out-of-office replies use the default onmicrosoft.com routing address instead of the primary custom domain.

Fix Microsoft 365 External Out of Office Replies Sending from onmicrosoft.com Domain
Product
Microsoft 365 (Exchange Online)
Device & OS
not provided
Scenario
Configuring automatic out-of-office replies for mailboxes migrated to a hybrid Exchange environment.
Observed behavior
External automatic replies are sent from the tenant's onmicrosoft.com domain, even though normal email delivery and internal automatic replies correctly use the primary custom domain.
Before you start

Verify that your organization's custom domain is set as the default domain in the Microsoft 365 admin center before modifying on-premises routing attributes.

Solution 1Recommended

Review Exchange Hybrid Configuration and Target Addresses

Check the target address values and accepted domain settings to ensure the custom domain is primarily used for external routing.

In hybrid deployments, the targetAddress attribute must align with your primary SMTP address. If the targetAddress points to the onmicrosoft.com alias as the primary identifier rather than just a routing alias, external out-of-office messages might default to this address.

1
Check Accepted Domains

Log in to the Exchange Admin Center, navigate to Mail flow > Accepted domains, and confirm your organization's custom domain is set as the Default domain.

2
Verify Remote Mailbox Attributes

Open the on-premises Exchange Management Shell and verify the targetAddress property for the affected users to ensure it points to the correct custom domain SMTP address.

3
Update Email Address Policies

Ensure that your on-premises email address policies stamp the correct primary SMTP address on objects before they are synchronized to Exchange Online via Azure AD Connect.

Review Exchange Hybrid Configuration and Target Addresses
Advanced Hybrid Troubleshooting: Because this issue involves local Exchange server configurations synchronizing to the cloud, complex cases should be escalated to the Microsoft Q&A forum under the Exchange Server tag.
Free Microsoft Office alternative

Looking for a Hassle-Free Office Suite? Try WPS Office

While complex Exchange server setups require extensive IT administration, your daily document work shouldn't. WPS Office provides a free, lightweight, and highly compatible alternative to Microsoft Office, featuring an intuitive interface that makes switching seamless.

  1. 1. Download WPS Office: Visit the official WPS Office website and download the free installer tailored for your operating system.
  2. 2. Install the Software: Run the installer package and follow the brief on-screen instructions to complete the setup process.
  3. 3. Open and Create: Launch WPS Office to instantly start creating, editing, and sharing documents with full Microsoft Office format compatibility.
Fully compatible with Microsoft Word, Excel, and PowerPoint formats (.docx, .xlsx, .pptx).Lightweight design ensuring fast installation and smooth performance even on older devices.Familiar user interface with a minimal learning curve for users switching from Microsoft Office.Built-in PDF editor to view, edit, and manage your documents effortlessly.
microsoft office alternative - wps office

Frequently Asked Questions

Why do internal out-of-office replies work but external ones use onmicrosoft.com?

Internal replies often rely on direct Active Directory lookups and primary SMTP addresses within the tenant, while external replies rely on the remote routing address (targetAddress) configured during the hybrid migration process, which may be defaulting to the onmicrosoft.com alias.

Can I fix the onmicrosoft.com reply issue directly from the Microsoft 365 portal?

In a standard hybrid environment, the source of authority is the on-premises Active Directory. Therefore, you typically need to fix attributes like the targetAddress on your local Exchange server and wait for Azure AD Connect to synchronize the changes to the Microsoft 365 cloud portal.

Will changing the default accepted domain affect my current email delivery?

Setting your custom domain as the default accepted domain ensures new mailboxes get the correct primary address, but it won't disrupt existing email routing as long as the necessary secondary aliases (including the default tenant onmicrosoft.com routing address) remain attached to the mailboxes.