550 5.7.708 Access denied, traffic not accepted from this IP is Microsoft 365 refusing to send your mail, not a recipient refusing to receive it. Microsoft says it appears "if you send an email message from an IP address that has a low reputation" and that it "is more likely to affect new customers, such as those who have a Microsoft 365 trial subscription". Only a tenant admin can fix it: assign real licences, rule out a compromised account, then ask Microsoft Support to review the block.
This is one of the outbound protection codes covered in our SMTP error codes guide for cold email. It catches cold senders more than most, because the typical pattern (new domain, new tenant, immediate campaign) is exactly what Microsoft's outbound filtering is designed to stop.
Where the block happens
A normal rejection comes from the recipient's server. 5.7.708 comes from Exchange Online Protection before your message leaves Microsoft. Microsoft sends outbound mail from pools of IP addresses, and mail from tenants it does not yet trust, or that look risky, is routed through addresses with poorer reputation. When that reputation is too low for the destination, Microsoft refuses the relay and generates the NDR itself.
Signs that you are looking at an outbound block rather than a recipient block:
- The NDR is generated by your own tenant (the "Generating server" line names a
prod.outlook.comhost in your organisation). - It affects many unrelated recipient domains at once, not just one provider.
- Internal mail between your own users still works.
The 5.7.70x family side by side
Microsoft groups these codes on one troubleshooting page. Each has different text and a different fix, so read the exact code.
| Code | NDR text | What Microsoft says causes it | Who fixes it |
|---|---|---|---|
550 5.7.703 | "Your message can't be delivered because messages to [recipients] are blocked by your organization using Tenant Allow Block List." | Your own admin blocked that recipient or domain | Your admin edits the Tenant Allow/Block List |
550 5.7.705 | "Access denied, tenant has exceeded threshold." | Your organisation "sends too much spam or bulk mail"; often a compromised account or connector | Your admin fixes the cause, then contacts Microsoft Support |
550 5.7.708 | "Access denied, traffic not accepted from this IP." | Sending IP has low reputation; more likely for new and trial tenants | Your admin; for trials, request an IP exception from support |
550 5.7.750 | "Client blocked from sending from unregistered domain" | Large volume sent from a domain that is not an accepted domain | Your admin adds and verifies the domain, then contacts support |
550 5.1.8 | "Access denied, bad outbound sender" | One user exceeded sending limits or outbound spam policy limits | Your admin unblocks the user from Restricted entities |
550 5.7.236 | Throttled sending from an onmicrosoft.com address | onmicrosoft.com domains are limited to 100 external recipients a day per organisation | Send from your own verified domain |
The difference that matters most: 5.1.8 is about one user, 5.7.705 is about the whole tenant's behaviour, and 5.7.708 is about the IP reputation your tenant is assigned. A cold campaign can trigger any of them, and it is common to see 5.1.8 on one mailbox and 5.7.708 for the tenant in the same week.
Why new tenants on trial licences hit it
A new tenant has no sending history, so Microsoft has nothing to judge it on except what it does first. Several things push a new tenant into the low reputation path:
- Trial status. Microsoft names trial subscriptions explicitly. Trial tenants are also capped at 5,000 external recipients a day under the tenant external recipient rate limit, against a higher licence-based limit for paid tenants.
- Sending from
onmicrosoft.com. Before your own domain is verified, mail goes out as the default domain, which is limited to 100 external recipients a day. - Volume on day one. A tenant created on Monday that sends a few hundred cold emails on Tuesday looks very like a tenant created by a spammer.
- High bounce rates. Guessed or stale addresses produce bounces, which Microsoft treats as a sign of a purchased or harvested list.
- Several new mailboxes sending identical messages. Rotation across mailboxes in a new tenant multiplies the signal rather than hiding it.
Admin steps to recover
Work through these in order. They are all in the Microsoft 365 admin centre, the Exchange admin centre or the Microsoft Defender portal.
- Stop sending. Pause every campaign and any tool that sends through the tenant. Keep person-to-person mail to a minimum.
- Assign real licences. Microsoft's advice for trials is to "contact Microsoft Support to request an IP address exception until you assign Exchange Online licenses". If you intend to keep the tenant, convert from trial and assign Exchange Online licences to the users who send.
- Verify your domains. Under Settings > Domains, make sure each domain you send from is added and verified, so nothing goes out as
onmicrosoft.com. This also prevents 5.7.750. - Check Restricted entities. In the Defender portal, open Email & collaboration > Review > Restricted entities (or
https://security.microsoft.com/restrictedentities). Any user listed there was blocked for exceeding sending or outbound spam limits. Microsoft says to confirm the account is not compromised, require MFA and reset the password before you select Unblock; restrictions are normally removed within one hour and no later than 24 hours. - Rule out compromise. Review sign-in logs for unfamiliar locations, mailbox rules that forward or delete mail, and connectors you did not create. Microsoft lists compromised accounts and rogue connectors as common causes of 5.7.705.
- Run the sender history diagnostic. Microsoft points admins to the Blocked Sender History diagnostic (
https://aka.ms/senderhistory) before unblocking. - Open a service request. From the admin centre's Support area, open a request. Include the full NDR text, the date and time of a recent bounce, your accepted domains, licence status, and what you have changed. Ask for the 5.7.708 block to be reviewed, or for an IP exception if you are still on a trial.
- Wait for confirmation, then test. Send a single message to an external mailbox you control and check it arrives before you touch the campaign.
Microsoft does not publish how long a 5.7.708 review takes. Plan for days rather than hours, and do not create new tenants to get round it. That is working around a protection measure rather than fixing the cause, and a new tenant starts with no reputation, which is how this began.
Warm-up and volume changes to avoid a repeat
Once mail flows again, the tenant is still new. Change the pattern that caused the block:
| Change | Why it helps |
|---|---|
| Start with ordinary business email for the first days | Builds a history of normal traffic and replies |
| Increase campaign volume gradually from a low daily figure | Avoids the sudden jump that triggers outbound spam detection |
| Keep each mailbox well under Exchange Online's published limits (10,000 recipients a day, 30 messages a minute) | Those are hard ceilings, not targets; campaign volume should be a small fraction |
| Verify addresses before sending and remove hard bounces immediately | Bounce rate is one of the strongest negative signals |
| Personalise properly instead of sending identical text | Identical bodies from several mailboxes look like bulk mail |
| Watch replies and complaints daily | An early rise in "not interested" or abuse replies predicts the next block |
Our warm-up schedule for a new domain sets out a day-by-day plan.
When to use a separate sending route instead
Microsoft 365 mailboxes are designed for person-to-person business mail. Microsoft's own limits page recommends Azure Communication Services email for high-volume sending to external recipients. If your outreach volume is genuinely campaign-scale, a route built for that (a dedicated email service, configured with your domain's SPF, DKIM and DMARC) is more honest than pushing a mailbox tenant until it breaks.
What a separate route does not fix: a poor list, missing permission records or messages people do not want. If those caused the block, moving them to another route moves the problem. Outlook.com consumer mailboxes apply their own filtering on the receiving side as well; see Outlook S3150 block list errors and Microsoft's high-volume sender requirements for Outlook.com.
If you own your sending IPs, enrol them in Microsoft's Smart Network Data Services (SNDS), which "gives senders access to detailed data about individual IPs". That does not apply to Microsoft 365's shared outbound IPs, which you do not own.
Cold-sender mistakes that trigger outbound spam detection
- Creating the tenant and sending a campaign in the same week.
- Sending from the
onmicrosoft.comdomain because the custom domain was not verified yet. - Using several brand-new mailboxes in rotation from the start.
- Uploading a list of guessed addresses (
firstname@) without verification. - Leaving the default SMTP AUTH settings and password-only logins, which invites compromise; see 535 5.7.139 SMTP AUTH errors for the authentication side.
- Ignoring the first 5.1.8 restriction on one user and moving the campaign to another user.
How Map Extract helps
Map Extract's bulk email sender sends through the SMTP accounts you configure, including Microsoft 365 mailboxes, so it cannot lift a Microsoft block. It helps you avoid the sending pattern that leads to one:
- Caps at three levels. Hourly, daily and monthly campaign caps, a minimum delay between messages and per-route ceilings per hour and day keep each mailbox at modest volumes.
- Optional warm-up ramp. The ramp starts low and increases by a set amount every set number of minutes, so a new mailbox does not jump straight to full volume.
- Bounce auto-pause. When bounces reach the threshold (5% by default) the campaign stops. If 5.7.708 or 5.1.8 NDRs come back to the sending mailbox and are read as bounces, they count towards that threshold, so sending stops instead of continuing to hit a blocked tenant.
- Sender rotation you choose. You decide which SMTP senders are allowed in rotation, so a blocked mailbox can be taken out of use while the admin works on it.
- Reviewed audiences. Recipients need a recorded permission basis and suppression is checked twice, which keeps the list cleaner than a raw export.
It does not contact Microsoft, change tenant settings or check your domain's SPF, DKIM and DMARC. Those steps stay with your Microsoft 365 admin.
Key takeaways
- 5.7.708 is an outbound block inside your own Microsoft 365 tenant, caused by low IP reputation.
- New and trial tenants are the usual victims; Microsoft's fix for trials is an IP exception via support until Exchange Online licences are assigned.
- Read the exact code: 5.1.8 is one user, 5.7.705 is tenant behaviour, 5.7.750 is an unverified domain.
- Secure accounts, verify domains and check Restricted entities before asking support for help.
- Resume slowly, keep volumes far below Exchange Online's ceilings, and use a purpose-built route for campaign-scale volume.
Frequently asked questions
What does 550 5.7.708 access denied traffic not accepted from this IP mean?
It is Microsoft 365 refusing to send your outbound mail. Microsoft says the NDR appears when you send from an IP address with a low reputation, and that it is more likely to affect new customers such as those on a Microsoft 365 trial. The block sits in your own tenant's outbound path, so the recipient never saw the message and only your admin can resolve it.
How do I fix 5.7.708 on a Microsoft 365 trial?
Microsoft's advice for trial subscriptions is to contact Microsoft Support and request an IP address exception until you assign Exchange Online licences. In practice, buy and assign the licences, verify your domain, secure every account with MFA, stop bulk sending, then open a service request from the admin centre quoting the full NDR text and asking for the block to be reviewed.
What is the difference between 5.7.705 and 5.7.708?
5.7.705 says the tenant has exceeded a threshold: Exchange Online saw too much spam or bulk mail from your organisation and blocked its outgoing mail, often after an account compromise. 5.7.708 says the IP address your tenant's mail would leave from has low reputation, typical of new tenants. Both are admin problems, and for both Microsoft says to fix the cause, then contact support.
How long does a 5.7.708 block last?
Microsoft does not publish a timeline for 5.7.708. It depends on your tenant's licence status, its sending history and the outcome of any support request. Expect it to persist while the conditions that caused it remain. Stop campaign sending in the meantime: repeated attempts from a tenant that Microsoft already rates as low reputation will not shorten the block.
Sources
Written by the Map Extract editorial team. Found an error? Email [email protected] and we will check and correct it. How we research guides: editorial policy.