Office 365 Mailbox Migration – Target Mailbox Doesn‎'t Have An SMTP Proxy Matching

When migrating mailboxes from on-premises Exchange to Office 365, we can run into the error where the migration fails with an error stating that the target mailbox doesn’t have an SMTP proxy matching the Microsoft Online Routing Domain. 

This can happen due to a number of causes.  For example the mailbox is managed by an Email Address Policy (EAP) that was not updated with the online routing domain.  Alternatively, the mailbox may not be managed by an Email Address Policy.  Office 365 will display the following, indicating which mailboxes failed to be migrated:

Office 365 Mailbox Migration Failed As Target Mailbox Doesn't Have A Matching SMTP Proxy

The error logged is "target mailbox doesn‎'t Have An SMTP Proxy Matching <>".


If we look to see what EAPs are present in this organisation, there are two.  The Default Policy and an additional one called Corp-Policy-1.  The mailbox above is managed by the Corp-Policy-1 EAP.  Looking at the settings of the EAP there is a difference between them.  There is an extra address in the Default EAP – this is the address.  This is not present in the Corp-Policy-1 EAP.

Get-EmailAddressPolicy | FL Name, *EMAIL*

Checking Email Address Policy Addresses

For mailboxes located in the OU managed by the Corp-policy-1 EAP, they will pick up the above settings from that EAP.

We need to edit the Corp-Policy-1 EAP, and add in the namespace.


Updating EAP

Let’s update the Corp-Policy-1 EAP with the additional SMTP address. 

Updating Email Address Policy

Note that it does not have to be the primary address, just present on the mailbox as a secondary.


The EAP is applied once the changes have been made.

Note that the online routing domain is now present on both EAPs:

Checking Email Address Policy Addresses


Looking at this user’s mailbox we can now see that the additional SMTP address has been added. 

Checking Addresses Assigned Via Email Address Policy On A Mailbox

Now we can either wait for the next automatic iteration of Directory Synchronisation, or manually launch a delta sync to synchronise these changes to Office 365. 

Once that has completed, the migration can be re-attempted.


Proactively Addressing This Issue

We can identify users who are not inheriting an EAP quickly using PowerShell.  A sample PowerShell query to quickly check all mailboxes could look like this:

Get-Mailbox -ResultSize unlimited | Where-Object  {$_.EmailAddressPolicyEnabled -eq $FALSE}

Checking All Mailboxes To Determine If Email Address Policy Is Enabled




Comments (2)
  1. Mike Koch says:

    Is it a requirement that the mailbox be managed by an EAP? I have a mailbox that has a proxy address for our Exchange Online tenant, but the user has a custom reply-to address, therefore the EAP checkbox is unchecked. Attempts to move this mailbox to Exchange
    Online continue to fail with the same error that no proxy address exists for the tenant domain (which is not true).

    If it were just one user, it wouldn’t be an issue, but I know we have more and I just want to know for sure that that’s what’s causing the failures. Thanks!

Comments are closed.

Skip to main content