About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
In an Exchange hybrid deployment, a Microsoft 365 user sends to a colleague and gets a bounce that ends "550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP address lookup". Microsoft's page for this exact hybrid case gives one cause: the recipient was created in Microsoft 365, so the on-premises Exchange environment has no object to reference for the user, and every lookup of that SMTP address fails. The fix on that page is to create a matching remote mailbox object on-premises, set its ExchangeGuid to the cloud mailbox's value, and let directory synchronisation run.
Microsoft's 550 5.1.10 page for Exchange Online lists other causes, and the table below includes them: an address that does not exist or has no licence, broken forwarding, and an Authoritative accepted domain where on-premises users are not represented in Exchange Online by mail contacts or mail users. If you have no on-premises Exchange, start with the first rows of that table; the on-premises object steps in the Fix section apply only to hybrid organisations.
What the error means
Microsoft's page quotes the bounce a user sees:
Your message to User@contoso.com couldn't be delivered.
User wasn't found at <contoso.com>
The NDR (non-delivery report, or bounce) then carries the code "550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP address lookup".
The page says the problem occurs if the user was created in Microsoft 365. In that case the on-premises Exchange environment has no object to reference for the user, so all queries for that SMTP address fail. The mailbox itself can be healthy in Exchange Online. The fault is that nothing on the on-premises side stands for it.
The page applies to Exchange Online. The two on-premises cmdlets it uses, New-RemoteMailbox and Set-RemoteMailbox, run in the Exchange Management Shell on the on-premises server. A remote mailbox, in Microsoft's reference wording, is a mail user in Active Directory that is associated with a mailbox in the cloud-based service.
Other bounce codes have other fixes, so read the code in the bounce before you start.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| User created in Microsoft 365, no on-premises object | NDR 550 5.1.10 for that one recipient; the cloud mailbox works | Get-RemoteMailbox on-premises returns no object for that user |
| On-premises object exists but its ExchangeGuid differs from the cloud mailbox | Same NDR; the object is present | Compare ExchangeGuid on both sides (commands below) |
| Change made but directory synchronisation not yet completed | Same NDR shortly after a fix | The user does not yet show as Synced with Active Directory in the admin center |
| Recipient does not exist, was mistyped, or has no licence | NDR for that one address; the sender may have a stale Auto-Complete entry | In the Microsoft 365 admin center, Users, Active users: find the recipient and check the licence for email |
| Broken forwarding on the recipient | The address in the NDR differs from the address the sender typed | Check Inbox rules, account forwarding and mail flow rules (redirect rules) |
| Accepted domain is Authoritative and the on-premises user has no mail contact or mail user in Exchange Online | NDR for on-premises users of that domain | Read the domain type with Get-AcceptedDomain (command below) and check the recipient exists as a mail contact or mail user |
The first row is the cause on Microsoft's hybrid page. Rows 2 and 3 are checks that go with its steps, which set the ExchangeGuid and then wait for or force synchronisation. Rows 4 to 6 come from Microsoft's 550 5.1.10 page for Exchange Online. That page also describes backscatter: a spammer falsifies your address as the sender, so a bounce for a message you never sent can be ignored.
Prove the cause before changing anything
All of these only read. Connect to Exchange Online PowerShell and read the cloud mailbox's ExchangeGuid:
Get-Mailbox USER-ALIAS | Format-List ExchangeGuid
Then, in the Exchange Management Shell on the on-premises server, look for the matching object:
Get-RemoteMailbox -Identity jsmith@contoso.com.au | Format-List
If the command returns nothing, the first cause is confirmed. If it returns an object, find ExchangeGuid in the list and compare it with the cloud value. A mismatch means the object is not tied to the cloud mailbox.
For the accepted-domain row, read the domain type in Exchange Online PowerShell:
Get-AcceptedDomain | Format-List Name,DomainName,DomainType
Microsoft's 5.1.10 page says that when the accepted domain is Authoritative, the service looks for the recipient in the Exchange Online organisation and, if it is not found, delivery stops and the sender gets this bounce. When the domain is Internal Relay, the service relays to your on-premises Exchange organisation, provided the required connector exists. The same page warns that changing the accepted domain type "might cause other unanticipated problems", so the command here only reads.
Also look at the user in the Microsoft 365 admin center. Microsoft's final check is that the user shows as "Synced with Active Directory".
Finally, run a message trace so you have the failed message's details on record. In the Exchange admin center go to Mail flow, then Message trace. Pick a date range close to the time of the failed send, use Add sender and Add recipient, and select Search. Select the message and its Details to see what happened and the How to fix it text. Microsoft says trace data can appear as soon as 10 minutes after sending, or take up to one hour, so a trace run seconds after the bounce can come back empty.
The ExchangeGuid is the value that ties the two sides together. Microsoft's reference says it is a unique Exchange mailbox identifier, corresponds to the msExchMailboxGuid attribute in Active Directory, and "should match the ExchangeGuid value of the corresponding cloud mailbox". That is why a mismatch matters even when the object exists.
Example (illustrative): Contoso has 120 cloud mailboxes and Get-RemoteMailbox on-premises returns 117 objects. The gap is 120 - 117 = 3 users who exist only in the cloud. Messages to those three addresses from other cloud users bounce with 5.1.10. The other 117 are not affected by this cause.
Fix
The page's steps, in order, are: create an on-premises object for the cloud mailbox, set its ExchangeGuid, wait for or force directory synchronisation, then check the sync status.
Step 1: select the right user, then create the object. Microsoft says to use the New-RemoteMailbox cmdlet and notes that the object must have the same name, alias and user principal name (UPN) as the cloud mailbox. First select and record the cloud mailbox you are matching. In Exchange Online PowerShell, save its values to a file:
Get-Mailbox jsmith | Format-List Name,Alias,UserPrincipalName,ExchangeGuid | Out-File -FilePath .\jsmith-cloud-mailbox.txt
Then, in the Exchange Management Shell on-premises, confirm that no remote mailbox already exists for this user:
Get-RemoteMailbox -Identity jsmith@contoso.com.au
That command must return no object. Ask the directory administrator to confirm in Active Directory that no user object exists for the same UPN or alias. If either check finds an object, stop: you have the ExchangeGuid mismatch case, and Step 2 is the fix. Take Name, Alias and UserPrincipalName for the next command only from the saved file, and keep the file.
Disruptive step: the reference says New-RemoteMailbox "creates an on-premises mail user. The mail user contains a specific attribute, which indicates that an associated mailbox in the service should be created when the user is synchronized to the service using directory synchronization." It runs against live directory data and the cloud mailbox already exists, so use it for one selected user at a time. There is no way back from this step that Microsoft documents. Do not use Remove-RemoteMailbox or Disable-RemoteMailbox as a back-out. Microsoft's reference says Remove-RemoteMailbox removes the on-premises user and the associated cloud mailbox, and Disable-RemoteMailbox removes the cloud mailbox. If you are unsure, stop and ask Microsoft Support before you run it.
The reference for the cmdlet shows the form, and it first stores the password in a variable with Get-Credential:
$Credentials = Get-Credential
New-RemoteMailbox -Name "Jane Smith" -Alias jsmith -UserPrincipalName jsmith@contoso.com.au -Password $Credentials.Password
Step 2: match the ExchangeGuid. In Exchange Online PowerShell, read the value again:
Get-Mailbox jsmith | Format-List ExchangeGuid
Then on-premises, record the current on-premises value first, in a file you keep:
Get-RemoteMailbox jsmith | Format-List ExchangeGuid | Out-File -FilePath .\jsmith-onprem-exchangeguid-before.txt
Disruptive step: the next command changes the mailbox identifier on the on-premises object. A wrong GUID leaves mail for the user undeliverable. Back-out: if the object existed before you started (the mismatch case), run the same command again with the value you recorded in jsmith-onprem-exchangeguid-before.txt. If you created the object in Step 1, it had no earlier value worth restoring; correct a wrong GUID by running the same command with the cloud mailbox's ExchangeGuid, which you can read again with Get-Mailbox jsmith | Format-List ExchangeGuid.
Set the on-premises object to the cloud value (the GUID below is the example from Microsoft's reference, replace it with yours):
Set-RemoteMailbox jsmith -ExchangeGuid d5a0bd9b-4e95-49b5-9736-14fde1eec1e3
Step 3: synchronise. Wait for directory synchronisation or force it, then confirm the user shows as Synced with Active Directory. The Set-RemoteMailbox reference says changes depend on the directory synchronisation schedule and are not immediate. Note the time you made each change so you can tell whether a later check is before or after the next synchronisation cycle.
Confirm the fix
Send a test message from another Microsoft 365 user to the affected address. Run a message trace in the Exchange admin center (Mail flow, then Message trace) for it and confirm it is delivered. Check Get-RemoteMailbox returns the object, and that its ExchangeGuid equals the cloud value. Repeat for each user in your gap count. If a user still bounces after the sync status shows Synced with Active Directory, take the trace details and both ExchangeGuid values to Microsoft Support rather than repeating the steps.
What to watch afterwards
- Any user created directly in Microsoft 365 in a hybrid organisation. Create users on-premises, or run the object check above after each cloud-side creation.
- The count of cloud mailboxes against remote mailbox objects, as in the example. A new gap means new bounces.
- Synchronisation errors for the same user, such as duplicate attribute conflicts.
- Whether the user later moves mailbox location, because the remote mailbox object must still match.
- The IsExchangeCloudManaged setting. Microsoft's hybrid page says that after you change a synchronised user's mailbox attributes on-premises with Set-RemoteMailbox you should allow the usual synchronisation cycle plus 24 hours before switching that user's Exchange attributes to cloud managed. For example, with a 6-hour cycle the total wait is 30 hours. Keep the setting at false until then.
Read next
Related articles you may want next.
- Troubleshooting550 5.1.1 RESOLVER.ADR.ExRecipNotFound and IMCEAEX bounces after moving mail to Microsoft 365Bounces with RESOLVER.ADR.ExRecipNotFound or an IMCEAEX address after a migration? Convert it to an X500 proxy address and clear the Outlook cache.Read article
- TroubleshootingExchange Online '550 5.4.1 Recipient address rejected: Access denied': Directory-Based Edge Blocking and missing recipients550 5.4.1 Recipient address rejected: Access denied is Directory-Based Edge Blocking. See which addresses it rejects and how accepted domain types fix it.Read article
- TroubleshootingEntra Connect Sync Errors: Duplicate Attributes, Soft and Hard Match ConflictsClassify Entra Connect export errors (AttributeValueMustBeUnique, InvalidSoftMatch, InvalidHardMatch, LargeObject), fix the source object on-premises and verify on the next cycle.Read article
Risks and limits
These commands have not been run or lab-tested. Microsoft's page on 5.1.10 in a hybrid deployment documents one cause and one fix and gives no command to force synchronisation; Microsoft's 5.1.10 page for Exchange Online does show Start-ADSyncSyncCycle -PolicyType Delta for that, or use your normal directory-sync tool. The other causes come from that Exchange Online page. The PowerShell reference pages show no date. The example GUID in the commands is Microsoft's illustration, not a value to reuse. Creating on-premises objects for existing cloud mailboxes affects live mail flow, so make the change in a quiet period and for one user first.
Sources
- "550 5.1.10 RESOLVER.ADR.RecipientNotFound" when Microsoft 365 users send emails to on-premises users in a hybrid deployment — Microsoft Learn, page dated 2025-06-25, accessed 20 November 2026
- Find and fix email delivery issues as a Microsoft 365 for business admin — Microsoft Learn, page dated 2025-06-25, accessed 20 November 2026
- Cloud-based management of Exchange attributes for Remote Mailboxes in hybrid environments — Microsoft Learn, page dated 2026-09-28, accessed 20 November 2026
- New-RemoteMailbox — Microsoft Learn, date not shown, accessed 20 November 2026
- Set-RemoteMailbox — Microsoft Learn, date not shown, accessed 20 November 2026
- Fix NDR error "550 5.1.10" in Exchange Online — Microsoft Learn, page dated 2026-08-10, accessed 20 November 2026
- Get-AcceptedDomain — Microsoft Learn, date not shown, accessed 20 November 2026
- Get-Mailbox — Microsoft Learn, date not shown, accessed 20 November 2026
- Out-File — Microsoft Learn, date not shown, accessed 20 November 2026
- Get-RemoteMailbox — Microsoft Learn, date not shown, accessed 20 November 2026
- Remove-RemoteMailbox — Microsoft Learn, date not shown, accessed 20 November 2026
- Disable-RemoteMailbox — Microsoft Learn, date not shown, accessed 20 November 2026
This article was originally published on .