Fix Exchange Online 550 5.1.10: RESOLVER.ADR.RecipientNotFound

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

Quick answer

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:

  1. Sender: check the spelling, delete the recipient from the Auto-Complete list, type the full address again and resend.
  2. Sender: compare the address in the NDR with the one in Sent Items. If they differ, the recipient's forwarding rule is sending your message to a bad address.
  3. Recipient's admin: confirm the mailbox or contact exists, the address matches and the user has an Exchange Online license.
  4. Recipient's admin (hybrid): check the accepted domain type, directory sync and the on-premises object for cloud mailboxes.

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.

Sender fixes: typos and stale Auto-Complete entries

  1. Open the NDR and use Send Again (Outlook: Report tab; Outlook on the web: "To send this message again, click here"). If the original had an attachment larger than 10 MB, resend it from Sent Items instead.
  2. Delete the recipient from the To line.
  3. Start typing the address until it appears in the Auto-Complete list, select it with the Down Arrow key and press Delete (or select the Delete icon next to it).
  4. Type the full address again, check the spelling and send.

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.

Admin fixes in Microsoft 365

  1. Recipient exists. In the Microsoft 365 admin center go to Users > Active users and search for the person. If the recipient doesn't exist (for example, the mailbox was removed), create a mailbox or a contact. If the recipient exists, make sure the username matches the address the sender used.
  2. License. For mailboxes in Exchange Online, confirm a license that includes email is assigned. If not, choose Edit and assign one.
  3. Forwarding. Look for a broken forwarding target: the user's Inbox rules, account forwarding (Mail settings > Email forwarding on the user, then turn it off), and mail flow rules in the Exchange admin center (Mail flow > Rules) that redirect messages to another address.
  4. MX record. Under Settings > Domains, select the domain and run Check DNS. Microsoft doesn't support more than one MX record for a domain enrolled in Exchange Online. The MX normally points to <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.
  5. Restored Microsoft 365 group. Mail to a group restored a short time ago can bounce with this code while the group is still initializing or directory replication finishes. Microsoft says to wait at least one hour after the restore and send again.

Accepted domain type: Authoritative vs Internal Relay

Accepted domain typeWhen Exchange Online can't find the recipient
AuthoritativeDelivery 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 RelayThe 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.

Hybrid: sync and cloud-created mailboxes

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:

  1. In the Exchange Management Shell, create a remote mailbox with New-RemoteMailbox using the same name, alias and UPN as the cloud mailbox.
  2. In Exchange Online PowerShell, get the cloud mailbox GUID: Get-Mailbox <MailboxName> | FL ExchangeGuid.
  3. On-premises, set it on the new object: Set-RemoteMailbox <MailboxName> -ExchangeGuid <GUID>.
  4. Wait for or force directory synchronization, and confirm the Microsoft 365 user shows as Synced with Active Directory.

Related "recipient not found" codes

CodeWhere it comes from
550 5.1.10 Recipient not foundExchange Online: SMTP address lookup didn't find the recipient.
550 5.4.1 Recipient address rejected: Access deniedExchange Online Directory-Based Edge Blocking rejected an unknown recipient in an Authoritative domain.
550 5.5.0 Requested action not taken: mailbox unavailableThe 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 foundExchange Server: the recipient doesn't exist, or a recreated mailbox is addressed from an old Auto-Complete entry.

Audit hundreds of domains at once

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).

Related tools and guides

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.

FAQ

What does 550 5.1.10 RESOLVER.ADR.RecipientNotFound mean?

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.

How do I fix 5.1.10 as the sender?

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.

Can an unlicensed mailbox cause 550 5.1.10?

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.

Why do cloud users get 5.1.10 when emailing on-premises users in hybrid?

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.

What is the difference between 550 5.1.10 and 550 5.4.1?

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.

Want the full kit?

Runbooks, checklists and helpdesk templates: IT Admin Packs on Gumroad.