Fix Exchange Online 5.7.501, 5.7.502 and 5.7.503: Access Denied, Spam Abuse Detected or Banned Sender

What the Exchange Online 5.7.501 spam abuse detected and 5.7.502 and 5.7.503 banned sender NDRs mean, what Microsoft documents as the fix (secure the account, reset credentials, contact support) and how they differ from 5.1.8.

Home › Guides › Exchange Online 5.7.501 to 5.7.503

Last updated 17 November 2026

Quick answer

Microsoft's Exchange Online NDR reference lists three codes with the same cause:

CodeTextDescription
5.7.501Access denied, spam abuse detectedThe sending account was banned because of detected spam activity.
5.7.502Access denied, banned senderThe sending account was banned because of detected spam activity.
5.7.503Access denied, banned senderThe sending account was banned because of detected spam activity.

The documented fix is the same for all three: verify that the account issues are resolved and reset the account's credentials, then contact Microsoft Support through your regular channel to restore the account's ability to send mail. Unlike 5.1.8, Microsoft doesn't document a self-service unblock for these codes.

What Microsoft documents, and what it doesn't

Step 1: Treat the account as compromised

A ban for spam activity usually means someone else was sending from the account. Follow Microsoft's compromised-account steps (covered in detail in the 5.1.8 guide):

  1. Disable the account during the investigation, or reset the password (not sent by email, not one of the last five, twice in Active Directory if synced). Delete and recreate app passwords.
  2. Enable and enforce MFA, then revoke sessions with Revoke-MgUserSignInSession -UserId <UPN>.
  3. Remove unknown MFA methods and devices, unwanted app consents and admin roles.
  4. Check forwarding and hidden Inbox rules:
    Get-Mailbox -Identity <Identity> | Format-List Forwarding*Address,DeliverTo*
    Get-InboxRule -Mailbox <Identity> -IncludeHidden | Format-List Name,Enabled,RedirectTo,Forward*,Identity
  5. Review Entra sign-in logs, the audit log and message trace for what the account sent.

If the mailbox is also listed on Email & collaboration > Review > Restricted entities in the Defender portal (or in Get-BlockedSenderAddress), that is the 5.1.8 restriction, and the 5.1.8 steps remove it. Microsoft's reference doesn't say that removing it lifts a 5.7.50x ban.

Step 2: Contact Microsoft Support

Microsoft's reference says to contact support through your regular channel to restore sending. For most tenants that is a service request in the Microsoft 365 admin center: Support > New service request (or Help & support). Include:

Microsoft's support page notes that phone support may send a verification code to the registered contact in your admin center profile, so keep that profile current.

Other banned-sender codes

The same NDR reference uses similar wording for blocks at other levels. The fix depends on what was banned:

CodeTextWhat was blocked and the documented fix
5.1.8Access denied, bad outbound senderOne account restricted for spam; secure it, then remove it from Restricted entities (5.1.8 guide).
5.7.505Access denied, banned recipientThe recipient isn't valid; contact support if you think it's an error.
5.7.511Access denied, banned senderThe sending IP was banned; email delist@microsoft.com with the full NDR code and IP address.
5.7.606-649Access denied, banned sending IP [IP1.IP2.IP3.IP4]The sending IP was banned; request removal in the delist portal.
5.7.705, 5.7.708Access denied, tenant has exceeded threshold / traffic not accepted from this IPThe tenant's sending was blocked (5.7.708 guide).
5.7.800Access denied, banned senderThe EHLO, P1 or P2 sender domain was banned for spam activity; contact Microsoft support.

The delist portal and delist@microsoft.com are for banned IP addresses. Neither is documented as a way to restore a banned account.

Prevent the next ban

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 your sending domain with the Email Deliverability Checker, SPF Record Checker, DKIM Checker and DMARC Record Checker, confirm the tenant with the M365 Tenant Lookup, look up an IP owner with the ASN IP Lookup and read the NDR in the Email Header Analyzer. Related guides: Exchange Online 550 5.1.8, Exchange Online 550 5.7.708, Exchange Online 5.2.2 and bulk sender requirements.

FAQ

What does 5.7.501 Access denied, spam abuse detected mean?

Microsoft's Exchange Online NDR reference says the sending account was banned because of detected spam activity. Verify the account issues are resolved, reset the credentials, and contact Microsoft Support through your regular channel to restore sending.

What is the difference between 5.7.502 and 5.7.503?

Microsoft documents both as Access denied, banned sender with the same description and the same fix. It doesn't document a difference between them.

Can I unblock 5.7.501, 5.7.502 or 5.7.503 myself?

Microsoft doesn't document a self-service unblock for these codes. Secure the account and reset its credentials, then contact Microsoft Support. If the account also appears on the Restricted entities page, that is the separate 5.1.8 restriction, which an admin can remove.

How is 5.7.501 different from 5.1.8?

5.1.8 Access denied, bad outbound sender means the account was restricted for exceeding sending limits. It appears on the Restricted entities page and an admin can remove it after securing the account. For 5.7.501 to 5.7.503 Microsoft says the account was banned and support must restore sending.

Will the delist portal fix 5.7.501?

No. The delist portal (5.7.606-649) and delist@microsoft.com (5.7.511) are for banned sending IP addresses. Microsoft's fix for an account banned with 5.7.501 to 5.7.503 is to secure it, reset the credentials and contact support.

Want the full kit?

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