The Hassle with Remote Routing Addresses in a Hybrid Environment

Nothing is more frustrating for a user to find out it isn’t receiving any e-mail. This easy method can help you monitor this issue and proactively prevent it from happening. Let’s solve the hassle with Remote Routing Addresses in a hybrid environment.

The Remote Routing Address tells Exchange server where to send the e-mail to in case of a remote mailbox. The issue occurs after the migration of mailboxes to Exchange Online because the Remote Routing Address attribute of the remote mailbox isn’t set to the @tenantname.mail.onmicrosoft.com address.

To monitor if the issue occurs in your environment, you can run the following PowerShell oneliner after a mailbox move or migration batch has been completed.

Get-RemoteMailbox -ResultSize Unlimited | ?{$_.remoteroutingaddress -notlike '*mail.onmicrosoft.com'}

Note: In my experience the Exchange admin center often doesn’t show the set Remote Routing Address, instead it shows the first available address. This can cause confusion for the administrator. The Exchange PowerShell module shows more reliable information.