What the Exchange Online bounce 5.7.708 Access denied, traffic not accepted from this IP means for new and trial Microsoft 365 tenants, how it relates to 5.7.705 and 5.7.750 tenant blocks, why the delist portal does not apply, and what to send Microsoft Support.
Home › Guides › Exchange Online 550 5.7.708
Last updated 17 November 2026
Microsoft documents the complete NDR text as:
5.7.708 Access denied, traffic not accepted from this IP.
Your bounce may show it with a 550 reply code and extra words around it. Match on the code 5.7.708 and the phrase traffic not accepted from this IP. Microsoft says the NDR is generated when a message is sent from an IP address with a low reputation, and that it's more likely to affect new customers, such as tenants on a Microsoft 365 trial subscription.
Only an email admin can fix it. Microsoft's instruction: if you get this error during a trial subscription, contact Microsoft Support to request an IP address exception until you assign Exchange Online licenses. Nothing in DNS or the client clears this block on its own. Still, check your setup first so the request goes smoothly (see below).
Microsoft covers four codes in one article. Its Exchange Online NDR reference groups 5.7.705 and 5.7.708 together: most of the tenant's traffic was detected as suspicious, so the tenant's ability to send is banned. Make sure any compromises or open relays are resolved, then contact support.
| Code | Documented text | Cause | Fix |
|---|---|---|---|
| 5.7.708 | Access denied, traffic not accepted from this IP. | Mail sent from a low-reputation IP. Most common for new or trial tenants. | Microsoft Support: request an IP address exception until Exchange Online licenses are assigned. |
| 5.7.705 | Access denied, tenant has exceeded threshold. | The tenant sent too much spam or bulk mail, often through a compromised on-premises server that routes mail to Exchange Online or a compromised admin account used to create connectors. Rarely, a renewed expired subscription is blocked while it renews (typically for no longer than one day). | Fix the compromise (respond to compromised accounts, MFA, tenant security, Secure Score), then contact Microsoft Support to remove the block. |
| 5.7.750 | Client blocked from sending from unregistered domain (the NDR reference words it as "Service unavailable. Client blocked from sending from unregistered domains") | Many messages sent from a domain that isn't an accepted domain. Less often, misconfigured connectors. | Add and validate every sending domain, use a certificate-based outbound connector whose certificate domain is accepted and validated, look for unusual connectors and compromised accounts, then contact Microsoft Support. |
| 5.7.703 | Your message can't be delivered because messages to <recipients> are blocked by your organization using Tenant Allow Block List. | A recipient address or domain is blocked in your own Tenant Allow/Block List. One blocked recipient blocks the whole message. | An admin changes the Tenant Allow/Block List entry. |
Microsoft's article for 5.7.708 sends you to Microsoft Support, not to a self-service portal. The Office 365 Anti-Spam IP Delist Portal (sender.office.com) is documented for external senders whose IP is on Microsoft's blocked senders list. Their bounce reads 550 5.7.606-649 Access denied, banned sending IP [IP address], and delisting can take up to 24 hours or longer. A different code, 5.7.511 (Access denied, banned sender), can't be fixed through the portal. For that one you email delist@microsoft.com with the full NDR code and IP address.
Two other codes are easy to confuse with this one:
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 sending-domain authentication 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 test headers in the Email Header Analyzer. Related guides: Exchange Online 550 5.4.1, Exchange Online 550 5.7.520, Exchange Online 5.7.57 (SMTP AUTH), Exchange Online 550 5.1.8, Exchange Online 5.7.501 to 5.7.503, Outlook.com 550 5.7.515 and bulk sender requirements.
Microsoft says Exchange Online generates it when mail is sent from an IP address with a low reputation, and that it mostly affects new customers such as tenants on a Microsoft 365 trial. It is a block on your outbound mail, not on the recipient side.
Only an email admin can fix it. Microsoft says to contact Microsoft Support and request an IP address exception until you assign Exchange Online licenses. Before you open the request, check licenses, validate all sending domains, look for unexpected connectors or compromised accounts, and keep the full NDR.
Microsoft does not point to the delist portal for 5.7.708. The portal at sender.office.com is documented for external senders who get 5.7.606-649 banned sending IP bounces, and 5.7.511 is handled by email to delist@microsoft.com. For 5.7.708, Microsoft says to contact Support.
5.7.705 means the tenant exceeded a spam or bulk threshold, often after a compromise. 5.7.708 means traffic came from a low-reputation IP, common on new tenants. 5.7.750 means too much mail was sent from domains that are not accepted domains. All three need an admin, and 5.7.705 and 5.7.750 need Support to remove the block after you fix the cause.
Not by itself. Microsoft documents a Support request as the fix. Good authentication is still worth doing before and after the exception, because a new tenant sending unauthenticated mail is more likely to run into reputation problems again.
Runbooks, checklists and helpdesk templates: IT Admin Packs on Gumroad.