BounceLens

Bounce codes › Microsoft 365

550 5.4.1: Recipient address rejected: Access denied

The address is not in that company's Microsoft 365 directory, so Microsoft refused it. Nothing is wrong with your email, your domain or your SPF.

If you sent the email: remove the address, or get a current one from the person. If you run the domain that rejected it: see the admin steps.

I sent the email I manage the domain that rejected it

Check the domain that bounced

Type the address that bounced, or just its domain. See who handles its email and what that means for this bounce.

Try:

Runs in your browser. Only the domain is looked up, through Cloudflare's public DNS. The address is not sent anywhere or stored.

Fix your list Address does not exist

The address does not exist. Microsoft rejects unknown addresses at the door with this message.

  • Sent by: Microsoft 365 / Outlook
  • Permanent (hard bounce). Sending the same message again fails again.

How Microsoft 365 words it (source):

Recipient address rejected: Access denied

Why the address is not in their directory

  • The address has a typo in the part before the @.
  • The person left the company and the mailbox was deleted.
  • The address was guessed or scraped (for example firstname.lastname@) and never existed.
  • On the recipient side: the mailbox lives on the company's own mail server and was never synced to Microsoft 365, so Microsoft does not know it.

How the bounce looks in your email tool

The same error comes in different wrappers. Look for 550 5.4.1 and Access denied:

Where you see itWhat it looks like (roughly)
GmailA message titled "Address not found", then "The response from the remote server was:" and 550 5.4.1 Recipient address rejected: Access denied
Outlook and Microsoft 365A message "Your message to … couldn't be delivered", with 550 5.4.1 Recipient address rejected: Access denied in the server details
Mailchimp, Brevo, SendGrid and other sending servicesA hard bounce in the campaign report, with a bounce reason such as smtp; 550 5.4.1 Recipient address rejected: Access denied

Often more follows: AS(201806281) and a server name ending in protection.outlook.com. Both are normal parts of this bounce. See AS(201806281) below.

If you sent the email

  1. Check the address letter by letter against where you got it. Fix a typo if you find one.
  2. If it is spelled right, remove it from your list. One bounce is enough: sending again gives the same result, and repeated hard bounces hurt your sender reputation.
  3. If you need to reach the person, ask for a current address another way: phone, LinkedIn, a colleague.
  4. If many addresses at different companies bounce like this at once, your list is old. People change jobs and their mailboxes get deleted. Check the whole list before the next send.

It is not your SPF, DKIM or a blocklist

This bounce is about the recipient address only. Microsoft rejects it because the address is not a valid recipient in that company's directory. Changing your SPF record or asking to be removed from a blocklist will not help.

Problems on your side come with other codes, for example 550 5.7.509 (DMARC failed) or 550 5.7.606 (your sending IP is blocked).

"It worked last week" or "the person says the address is right"

Then the address may be real, but Microsoft 365 does not know it yet, or not any more. Common reasons on their side:

  • The mailbox or alias is new and is not in Microsoft 365 yet. In mixed setups, where some mailboxes live on the company's own Exchange server, Microsoft says changes can take up to 24 hours to reach this check.
  • The company is moving its email to Microsoft 365, and some recipients are not there yet.
  • The address belongs to something that does not sync by itself, such as a mail-enabled public folder or a dynamic distribution group on the company's own server.
  • The person left and the mailbox was deleted.

You cannot fix any of this from outside. Send the person this message for their IT team:

Hi, an email to [the address] bounced with:
550 5.4.1 Recipient address rejected: Access denied

Microsoft 365 (Directory-Based Edge Blocking) rejected it because the address is not a valid recipient in your Exchange Online organization. Could your IT team check that this mailbox or alias exists in Exchange Online?

Microsoft's steps: https://learn.microsoft.com/en-us/troubleshoot/exchange/email-delivery/ndr/fix-error-code-550-5-4-1

If you manage the domain that rejected it

Microsoft calls the feature Directory-Based Edge Blocking (DBEB). It refuses mail for any address that is not a valid recipient in your Exchange Online organization. Microsoft's steps, in short:

  1. Check the spelling of the recipient address in the bounce.
  2. Find out whether one recipient fails or everyone in the domain. Send a test to a second address in the same domain.
  3. Whole domain: in the Exchange admin center, go to Mail flow > Accepted domains and select the domain. Switch it from Authoritative to Internal relay, then back to Authoritative.
  4. One recipient with an on-premises mailbox (Exchange hybrid with directory sync): change the mailbox's SMTP proxy address to a temporary one, then back to the original. Allow up to 24 hours.
  5. An on-premises mail-enabled public folder: check that it exists in Exchange Online. If not, copy it there with Microsoft's Sync-ModernMailPublicFolder script.
  6. An on-premises dynamic distribution group: it cannot sync to Exchange Online. Create a mail contact in Exchange Online with the same external address as the group.

While you set up or migrate a domain, Microsoft recommends Internal relay until every recipient is in Exchange Online and fully replicated. Then switch to Authoritative.

Full article: Fix NDR error 550 5.4.1 in Exchange Online (Microsoft Learn).

What does AS(201806281) mean?

Many of these bounces end with AS(201806281), for example:

550 5.4.1 Recipient address rejected: Access denied. AS(201806281) [DM6NAM10FT045.eop-nam10.prod.protection.outlook.com]

Microsoft does not document this number. What the bounces themselves show: it appears on rejections from Microsoft's filtering servers (Exchange Online Protection; the server name contains eop or protection.outlook.com), and the text before it is the same 550 5.4.1 error. Treat it as an internal tag. The meaning and the fixes on this page stay the same.

Not the same as

CodeWhat it meansWhose move
550 5.4.1 Relay access deniedSame number, different problem: the server that answered does not accept mail for that domain at all. Often an old or wrong MX record.The recipient domain's admin
550 5.1.10Microsoft 365 also found no such recipient, but one step later, after it accepted the connection.You: remove the address
550 5.1.1The same idea from Gmail and most other mail servers: the mailbox does not exist.You: remove the address
550 5.7.1A policy blocked the message, for example the recipient accepts mail only from certain senders. The address itself may be fine.Depends on the text after the code

Questions

Is 550 5.4.1 a hard bounce?

Yes. Your mail system will not retry it, and sending the same message again fails again. Remove the address unless the person confirms it should work.

The address worked last month. Why does it bounce now?

Most often the person left and the mailbox was deleted. If they still work there, their company changed something in Microsoft 365: see It worked last week.

What does AS(201806281) mean?

Microsoft does not document it. It shows up on rejections from Microsoft's filtering servers and does not change the meaning: the address is not in the company's directory.

What does error code 550 5.4.1 mean in plain words?

"We don't know this person here." Microsoft 365 checked the address against the company's list of mailboxes, did not find it, and refused the message.

Can I make the email go through?

Not from your side. Only the company that owns the domain can add or fix the address in Microsoft 365. Send the person the message for their IT.

Can BounceLens tell me if the mailbox exists?

No free tool can confirm one mailbox at Microsoft 365 without sending to it. The domain check shows whether Microsoft 365 handles the domain, and the list checker finds dead domains, typos and throwaway addresses in a whole list.

Got a different bounce?

Paste the whole message into the bounce code lookup. It reads the code and the words and tells you whose move it is.

Related codes

Free tools

Checked on 2 Nov 2026 against Microsoft Learn: Fix NDR error 550 5.4.1 in Exchange Online (updated 2 Oct 2026) and Directory-Based Edge Blocking. Anything Microsoft does not document is marked as such.