What the Exchange Online bounce 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP address lookup means, and how to fix typos, stale Auto-Complete entries, missing or unlicensed mailboxes, broken forwarding, accepted domain type and hybrid sync.
Home › Guides › Exchange Online 550 5.1.10
Last updated 17 November 2026
Microsoft's hybrid troubleshooting article shows the error code as:
550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP address lookup
with a user-facing part like "Your message to User@contoso.com couldn't be delivered. User wasn't found at contoso.com." Some bounces put the address inside the text ("Recipient TestGroup@contoso.com not found by SMTP address lookup"). The Exchange Online NDR reference sums it up as Recipient not found: SMTP address lookup didn't find the recipient's address.
In other words, the recipient's email address doesn't exist or couldn't be found. Work through it in this order:
If you never sent the original message, the NDR is probably backscatter: a spammer forged your address. You can ignore it, but if you get a lot, scan for malware and make sure your domain has SPF: check it with the SPF Record Checker and see SPF for Microsoft 365.
Why the Auto-Complete step matters: Microsoft explains that the list (also called the nickname cache) can hold an outdated entry. For example, if the recipient moved between on-premises Exchange and Exchange Online, the email address stays the same but other internal identifiers change, which breaks the cached entry.
<your domain>.mail.protection.outlook.com or <your domain>.subdomain.mx.microsoft, and DNS changes can take up to 72 hours. Check yours with the MX Record Lookup, the DNS Lookup and the DNS Propagation Checker.| Accepted domain type | When Exchange Online can't find the recipient |
|---|---|
| Authoritative | Delivery stops and the sender gets this bounce. On-premises users must exist in Exchange Online as mail contacts or mail users (created manually or by directory synchronization). |
| Internal Relay | The message is relayed to your on-premises Exchange organization, provided the connector to on-premises is set up. |
Microsoft warns that routing in hybrid setups is complex and that changing the type can cause other problems. Only switch to Internal Relay (Exchange admin center: Mail flow > Accepted domains, open the domain, choose Internal Relay, Save) if a connector already routes mail to on-premises and Internal Relay is the right design. Without that connector, mail to on-premises recipients breaks.
If senders get 550 5.4.1 Recipient address rejected: Access denied instead, the address was rejected at the edge by Directory-Based Edge Blocking. That has its own guide: fix Exchange Online 550 5.4.1.
Recipient on-premises not synced. If the recipient lives in on-premises Exchange, the address may not have synchronized to Microsoft 365. On the server running Microsoft Entra Connect Sync, run a delta sync, then check that the recipient now exists in Exchange Online:
Start-ADSyncSyncCycle -PolicyType Delta
Mailbox created in the cloud. Microsoft documents this exact bounce when a Microsoft 365 user sends to an on-premises user in a hybrid deployment, and the user was created in Microsoft 365. On-premises Exchange has no object for that address, so every lookup fails. The fix is to create the matching on-premises object:
New-RemoteMailbox using the same name, alias and UPN as the cloud mailbox.Get-Mailbox <MailboxName> | FL ExchangeGuid.Set-RemoteMailbox <MailboxName> -ExchangeGuid <GUID>.| Code | Where it comes from |
|---|---|
| 550 5.1.10 Recipient not found | Exchange Online: SMTP address lookup didn't find the recipient. |
| 550 5.4.1 Recipient address rejected: Access denied | Exchange Online Directory-Based Edge Blocking rejected an unknown recipient in an Authoritative domain. |
| 550 5.5.0 Requested action not taken: mailbox unavailable | The recipient's domain is @hotmail.com or @outlook.com and the address wasn't found. Microsoft calls it similar to 5.1.10. |
| 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found | Exchange Server: the recipient doesn't exist, or a recreated mailbox is addressed from an old Auto-Complete entry. |
Need SPF, DMARC and MX checks across a whole client list? Run the Bulk SPF / DMARC / MX Auditor on Apify ($2 per 1,000 domains).
Check the domain's MX with the MX Record Lookup, watch DNS changes with the DNS Propagation Checker, confirm the tenant with the M365 Tenant Lookup, read NDR headers in the Email Header Analyzer and keep cmdlets in the PowerShell Cheat Sheet. Related guides: Exchange Online 550 5.4.1, Exchange Online 550 5.7.520, Exchange Online 4.4.7 message expired, Exchange Online 550 5.7.1, Exchange Online 5.7.133 and 5.7.124 and SPF for Microsoft 365.
Exchange looked up the recipient by SMTP address and found nothing: the address doesn't exist or couldn't be found. Common causes are typos, stale Auto-Complete entries, deleted or never-created mailboxes, forwarding rules that point to bad addresses, and hybrid recipients that are missing or not synced.
Check the spelling, remove the recipient from the Outlook Auto-Complete list, type the full address again and resend. If the address in the NDR differs from the one you sent to, ask the recipient to fix their forwarding rule.
Microsoft's fix steps for 5.1.10 include checking that a mailbox hosted in Exchange Online exists and has a license that includes email, and assigning one if it is missing.
Microsoft documents that this happens when the user was created in Microsoft 365, so on-premises Exchange has no object for that address. Create a remote mailbox with New-RemoteMailbox, set its ExchangeGuid to match the cloud mailbox, and let directory synchronization run.
Both mean the recipient wasn't found. 5.4.1 Recipient address rejected: Access denied comes from Directory-Based Edge Blocking at the edge of Exchange Online for Authoritative domains. 5.1.10 comes from the recipient lookup. Fixes overlap: confirm the address exists and that sync and the accepted domain type are right.
Runbooks, checklists and helpdesk templates: IT Admin Packs on Gumroad.