About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
The bounce reads "5.7.708 Access denied, traffic not accepted from this IP." It means your message was sent from an IP address that has a low reputation. Microsoft's page says the problem is more likely to affect new customers, such as those with a Microsoft 365 trial subscription. Only an email admin in your organisation can fix it. If this is a trial, the documented step is to ask Microsoft Support for an IP address exception until you assign Exchange Online licences.
Three neighbouring codes look similar and need different fixes: 5.7.703, 5.7.705 and 5.7.750. The sections below tell them apart first, because a wrong guess wastes a day.
What the error means
The NDR (non-delivery report, also called a bounce) is generated when a message is sent from an IP address that has a low reputation. The message was not delivered, and the block is tied to the sending IP address, so the fault is not in the message itself.
A person who receives this bounce cannot fix it from their mailbox. Microsoft's page says only an email admin in your organisation can. The practical first step for staff is to forward the full bounce to whoever administers Microsoft 365, rather than resending the same message again and again. Repeated resends add noise to the message trace and fix nothing.
The same Microsoft page covers four codes:
- 5.7.703 means messages to a recipient or domain are blocked by your own organisation's Tenant Allow/Block List. If one recipient in a message is blocked, every other internal and external recipient in that message is blocked too.
- 5.7.705, "Access denied, tenant has exceeded threshold", means Exchange Online has blocked your outgoing mail because the organisation sent too much spam or bulk mail.
- 5.7.708 is the low-reputation IP block covered here.
- 5.7.750, "Client blocked from sending from unregistered domain", means a large volume of mail was sent from a domain that is not an accepted domain.
A fifth code is easy to confuse with these: 550 5.7.233 means the tenant exceeded its daily limit for external recipients. That is a volume limit, not a reputation block. Trial tenants have a default of 5,000 external recipients per day according to Microsoft's sending-limits page.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| Low-reputation sending IP on a new or trial tenant (5.7.708) | NDR text 5.7.708 on first outbound mail; no spam alerts | Tenant is new or on a trial; no licences assigned yet; volume is far below limits |
| Tenant blocked for spam or bulk mail (5.7.705) | NDR text 5.7.705 "tenant has exceeded threshold" | Unknown connectors, a compromised on-premises server or a compromised admin account |
| Recipient or domain on your Tenant Allow/Block List (5.7.703) | NDR names recipients "blocked by your organization using Tenant Allow Block List" | Entry present in the block list |
| Sending from a domain that is not accepted (5.7.750) | NDR text 5.7.750 | Domain missing from the accepted domains list |
Prove the cause before changing anything
Read, do not change. Start with the exact code in the bounce, because it decides everything. Copy the full NDR text, including the code, and keep it.
Next, check whether the tenant is new, on a trial or without Exchange Online licences. Look at which users hold an Exchange Online licence. Microsoft's 5.7.708 text mentions Exchange Online licences only as the end of the IP exception period, so an unlicensed trial fits this cause but does not prove it.
Then rule out a volume limit. Microsoft's sending-limits page lists the per-mailbox limits: 10,000 recipients per day and 30 messages per minute. Run a message trace in the Exchange admin center (Mail flow, then Message trace) for the failed message so you have its delivery details.
For 5.7.750 and a suspect list of domains, read the accepted domains in Exchange Online PowerShell. These three commands only read settings, and each one saves its output to a named file in the current folder, so you have the record before any change:
Get-AcceptedDomain | Format-List | Out-File -FilePath .\accepted-domains-before.txt
Get-OutboundConnector | Format-List | Out-File -FilePath .\outbound-connectors-before.txt
Get-InboundConnector | Format-List | Out-File -FilePath .\inbound-connectors-before.txt
Check the files for connectors nobody on your team created. Microsoft's 5.7.750 page warns that attackers sometimes create new inbound connectors in organisations to send spam, which is why the inbound command is included. You can also see connectors in the Exchange admin center under Mail flow, then Connectors.
For 5.7.703, save the current blocked senders and domains to a file the same way:
Get-TenantAllowBlockListItems -ListType Sender -Block | Format-List | Out-File -FilePath .\tenant-block-list-before.txt
Example (illustrative): Contoso Pty Ltd starts a Microsoft 365 trial for contoso.com.au with 25 mailboxes. On the first day the staff send mail and some of it bounces with 5.7.708. Each of the 25 users sends about 40 messages a day to 3 external recipients on average. That is 25 x 40 x 3 = 3,000 external recipients a day. The trial limit is 5,000, so 3,000 is 60 per cent of it. Volume is not the cause, and the code is not 5.7.233. No licences are assigned yet, which fits a new trial tenant, the case Microsoft's page names.
Fix
5.7.708 on a trial. Contact Microsoft Support and ask for an IP address exception. Microsoft's page gives the exception as the stop-gap "until you assign Exchange Online licenses". The page mentions licences only as the end of that exception period; it does not say that assigning licences clears 5.7.708, so ask Support what applies to your tenant.
Risk: if you assign licences as part of this, assigning them changes what each user can do and can add to your subscription cost. Back-out: remove the licence assignment from the user in the admin center. Record who held which licence first.
5.7.705. Find and close the route the spam took. The page names two scenarios: a compromised on-premises server that routes mail to Exchange Online, and a compromised admin account used to create connectors. It points to Microsoft's pages on responding to a compromised email account, setting up multifactor authentication, increasing tenant security and Secure Score. Once the cause is fixed, contact Microsoft Support to have the block removed. A renewal of an expired Exchange Online subscription can also trigger a short block, no longer than one day by the page's account.
Save first: connect with Connect-MgGraph -Scopes "User.ReadWrite.All", then run $user = Get-MgUser -Search UserPrincipalName:'jsmith@contoso.com.au' -ConsistencyLevel Eventual and Get-MgUser -UserId $user.Id -Property Id,UserPrincipalName,AccountEnabled | Format-List Id,UserPrincipalName,AccountEnabled | Out-File -FilePath .\jsmith-account-before.txt (Microsoft's AccountEnabled property description says it "Requires $select to retrieve"; -Property is Get-MgUser's way to select properties).
Disruptive step: the next command disables a compromised account, so that user cannot sign in or send until the account is enabled again.
Disable with Update-MgUser -UserId $user.Id -AccountEnabled $false, the command on Microsoft's compromised-account page.
To undo it: once the investigation is finished, reset the password and then enable the account. Microsoft's page says to "reset the password and then enable the account as described in Step 1: Disable the affected user account", but it prints only the disable command, and the Update-MgUser reference shows no example that turns the setting back on. So the restore target is the value in the saved file jsmith-account-before.txt (AccountEnabled was True before you started): set the account's enabled setting back to that value through the admin tool your organisation uses for user accounts, and check the result with the same Get-MgUser -Property Id,UserPrincipalName,AccountEnabled read.
5.7.703. Risk: removing a block entry lets mail from that sender or domain through again, to every user. An admin removes the blocking entry from the Tenant Allow/Block List. Microsoft's page says only an email admin in your organisation can change the list. The Tenant Allow/Block List page gives the path: in the Microsoft Defender portal go to Email & collaboration, then Policies & rules, then Threat policies, then the Rules section, then Tenant Allow/Block Lists, and use the Domains & addresses tab.
Save-first: the tenant-block-list-before.txt file from the read-only step above. Back-out: add the entry again with New-TenantAllowBlockListItems -ListType Sender -Block -Entries "blocked.contoso.com.au" -NoExpiration, using the entry value from your saved file (the page's block syntax needs either -ExpirationDate or -NoExpiration; use the expiry you recorded). To remove the entry from PowerShell, Microsoft gives Remove-TenantAllowBlockListItems -ListType Sender -Entries "blocked.contoso.com.au".
5.7.750.
Save first: accepted-domains-before.txt from the read-only step, plus a copy of the domain's current DNS records from your registrar.
Disruptive step: the domain steps below add a domain, which changes DNS and, if you accept the records Microsoft offers, mail routing. Microsoft's add-domain page says that after you finish setting up a custom domain, the domain's MX record is updated to point to Microsoft 365 and all email for the domain starts coming to Microsoft 365, and that incorrect DNS records can cause email and service outages.
Add and validate every domain you send from in Microsoft 365. The page lists this first. Alternatively use a certificate-based outbound connector whose certificate domain is accepted and validated. Microsoft recommends Domain Connect where the registrar supports it and offers a Manual tab if you prefer to add the records yourself. Add users and mailboxes before any MX change, as Microsoft's page directs, and do not accept an MX change you do not want.
To undo it, Microsoft's remove-a-domain page lets you remove a domain only when no users, shared mailboxes, groups, distribution lists or teams use it and it is not the default domain; a domain added only to send mail meets those conditions, and the page's steps are Settings, Domains, select the domain, Remove domain. Then restore any DNS records you changed from your saved copy.
Save first: the two connector files from the read-only step.
Disruptive step: the step below disables the connector, which stops the mail flow that depends on it.
If you find an unusual connector, disable it rather than deleting it. For an outbound connector run Set-OutboundConnector -Identity "Connector name" -Enabled $false; for an inbound connector use Set-InboundConnector with the same parameter. The reference pages say $true is the default and $false disables the connector.
To undo it, enable it again with Set-OutboundConnector -Identity "Connector name" -Enabled $true.
Confirm the fix
Send a test message from the affected mailbox to an external address you control. Then run a message trace for that message and confirm it shows as delivered. For a trial exception, watch for the 5.7.708 bounce to stop on new sends. For 5.7.705 and 5.7.750, confirm with Microsoft Support that the block is lifted before you send at normal volume.
What to watch afterwards
Keep a short note of the date of the bounce, the code, the sending address and what you changed. If the same code returns, that note shows whether the cause was fixed or only cleared for a while.
- Alert policies: the built-in policies Email sending limit exceeded, Suspicious email sending patterns detected and User restricted from sending email notify the TenantAdmins group by default.
- The Restricted entities page in the Microsoft Defender portal. A single blocked user shows up there. That is a different problem from a tenant block.
- Volume against the trial or licence-based daily limit, so that a growth in mail does not turn into a 5.7.233.
- Any new connector or accepted domain you did not create.
Read next
Related articles you may want next.
- TroubleshootingExchange Online '550 5.1.8 Access denied, bad outbound sender': a user is restricted from sending in Microsoft 365550 5.1.8 bad outbound sender: a user is on the Restricted entities page. Check for compromise first, then unblock in the portal or PowerShell.Read article
- TroubleshootingOutlook.com rejects mail: 550 5.7.1 part of their network is on our block list (S3150)Outlook.com bounce 550 5.7.1 S3150: the bounce text says your provider's network is on a block list. Check the IP, the requirements, then delisting.Read article
- TroubleshootingScanner or app can't send through Microsoft 365: '535 5.7.3 Authentication unsuccessful' and SMTP AUTH settingsScanner or app can't send via Microsoft 365 (535 5.7.3 or 5.7.57)? Check SMTP AUTH on the mailbox and tenant, then choose SMTP AUTH, relay or Direct Send.Read article
Risks and limits
These commands have not been run or lab-tested. The Get- commands only read settings and write a file. The Set-, Update-, New- and Remove- commands change live settings, each one is marked above with its save-first step and back-out, and connectors, licences, domains and the allow/block list should be recorded before every change.
Microsoft documents only the Support exception route, and only for trial subscriptions. There is no documented self-service way to clear a low-reputation IP and no documented timeline. If your tenant is not a trial, the page says only that an email admin must resolve it, so open a support request with the full NDR text. The accepted-domain and outbound-connector reference pages show no date, and the properties they return can differ by version.
Sources
- Fix NDR error codes 550 5.7.703, 550 5.7.705, 550 5.7.708, and 550 5.7.750 — Microsoft Learn, page dated 2026-10-03, accessed 20 November 2026
- Troubleshoot outbound sending limits and blocked users in Exchange Online — Microsoft Learn, page dated 2026-05-27, accessed 20 November 2026
- Respond to a compromised cloud email account — Microsoft Learn, page dated 2026-07-17, accessed 20 November 2026
- Find and fix email delivery issues as a Microsoft 365 for business admin — Microsoft Learn, page dated 2025-06-25, accessed 20 November 2026
- Get-AcceptedDomain — Microsoft Learn, date not shown, accessed 20 November 2026
- Get-OutboundConnector — Microsoft Learn, date not shown, accessed 20 November 2026
- Get-InboundConnector — Microsoft Learn, date not shown, accessed 20 November 2026
- Set-OutboundConnector — Microsoft Learn, date not shown, accessed 20 November 2026
- Set-InboundConnector — Microsoft Learn, date not shown, accessed 20 November 2026
- Allow or block email using the Tenant Allow/Block List — Microsoft Learn, page dated 2026-08-03, accessed 20 November 2026
- Set up connectors to route mail between Microsoft 365 or Office 365 and your own email servers — Microsoft Learn, page dated 2025-07-28, accessed 20 November 2026
- Add a custom domain to Microsoft 365 — Microsoft Learn, page dated 2026-05-08, accessed 20 November 2026
- Remove a domain from Microsoft 365 — Microsoft Learn, page dated 2026-04-23, accessed 20 November 2026
- Get-MgUser — Microsoft Learn, date not shown, accessed 20 November 2026
- Update-MgUser — Microsoft Learn, date not shown, accessed 20 November 2026
- Out-File — Microsoft Learn, date not shown, accessed 20 November 2026
This article was originally published on .