Create an On-Premises Remote Mailbox for an Exchange Online User
Question details
Create an on-premises remote mailbox object for an existing synchronized Exchange Online user so on-premises applications can route mail to the cloud mailbox.

- Product
- Microsoft Exchange hybrid and Exchange Online
- Device & OS
- not provided
- Scenario
- An on-premises Active Directory user has an Exchange Online mailbox, and an on-premises relay application needs to deliver messages to that user.
- Observed behavior
- The synchronized user lacks an on-premises remote mailbox object, preventing delivery through the on-premises relay application.
Confirm that the user was created in on-premises Active Directory and is synchronized to the existing Exchange Online mailbox. Identify the user's correct remote routing address and use an account with the required Exchange management permissions.
Enable the on-premises remote mailbox and verify routing
Use Exchange Management Shell to create the remote mailbox representation for the existing on-premises user and verify the routing address.
Open Exchange Management Shell in the on-premises Exchange environment and identify the synchronized Active Directory user and the tenant's remote routing domain.
Run Enable-RemoteMailbox -Identity "user@contoso.com" -RemoteRoutingAddress "user@contoso.mail.onmicrosoft.com". Replace both addresses with the user's actual identity and remote routing address.
Run Get-RemoteMailbox -Identity "user@contoso.com" | Format-List Identity,RemoteRoutingAddress,ExchangeGuid and confirm that the remote routing address points to the intended Exchange Online recipient.
Allow the normal directory synchronization cycle to run, then send a test message from the on-premises relay application. If delivery still fails, check the relay application's recipient resolution and the hybrid mail-flow configuration.
If provisioning or a planned move back on-premises requires the GUID, connect to Exchange Online PowerShell and run Get-Mailbox -Identity "user@contoso.com" | Format-List ExchangeGuid. In the on-premises Exchange Management Shell, run Set-RemoteMailbox -Identity "user@contoso.com" -ExchangeGuid <GUID>, replacing <GUID> with the Exchange Online value.

Document Exchange Mailbox Changes in WPS Office
WPS Office is a free, lightweight Office alternative with a familiar interface and Microsoft Office format compatibility for a seamless move between productivity suites. It can help document mailbox changes, but it does not configure or repair Exchange.
- 1. Open WPS Writer: Launch WPS Office and choose Writer to create a document for the mailbox change.
- 2. Record the configuration: In the document, record the user identity, remote routing address, verification results, and any GUID-related migration requirement.
- 3. Save the record: Choose File > Save As and select DOCX if the record needs to be shared with Microsoft Word users.

Frequently Asked Questions
Which command creates the on-premises remote mailbox representation?
In on-premises Exchange Management Shell, run Enable-RemoteMailbox with the synchronized user's identity and the appropriate -RemoteRoutingAddress.
What remote routing address should I use?
Use the address associated with the user's Exchange Online recipient in the tenant's remote routing domain, such as user@contoso.mail.onmicrosoft.com. Replace the example with the actual address for your tenant.
Do I have to set the Exchange GUID for mail routing?
Not normally. The remote routing address is used for routing; the Exchange GUID may be required for a provisioning process or a future move back on-premises.
How do I find and apply the Exchange Online mailbox GUID?
In Exchange Online PowerShell, run Get-Mailbox -Identity "user@contoso.com" | Format-List ExchangeGuid. If required, apply that value on-premises with Set-RemoteMailbox -Identity "user@contoso.com" -ExchangeGuid <GUID>.
What should I check if the relay application still cannot deliver mail?
Use Get-RemoteMailbox to verify the recipient and remote routing address, allow directory synchronization to run, and send a test message. If it still fails, check recipient resolution and the hybrid mail-flow configuration.




