How to get delisted from Microsoft 365 / Outlook.com
AdminKit's guide to Microsoft/Outlook delisting starts with the bounce itself: a non-delivery report naming 'Access denied, banned sending IP' or 'banned sender' points to one of two separate removal processes depending on the exact error code, and Outlook.com's consumer service sometimes points further to a third-party list like Spamhaus. This covers the public procedure only — Microsoft decides the outcome.
By AdminKit team, Netbase JSC · Updated
Key takeaways
- Read the exact code in the bounce first.
5.7.606–5.7.649goes to Microsoft’s self-service delist portal;5.7.511goes todelist@microsoft.com; other codes are not Microsoft’s blocked senders list at all. - The portal takes one email address and one IP per visit, then emails you a confirmation link. Microsoft says removal can take up to 24 hours or longer.
- For
5.7.511, Microsoft says it will contact you within 48 hours with next steps. Neither path guarantees removal. - Outlook.com (the consumer service: hotmail.com, live.com, outlook.com addresses) has its own error codes and its own delisting form.
- Delisting only removes the block. Mail still has to pass Microsoft’s filtering, and Microsoft warns the IP can be blocked again.
What does this guide cover, and what doesn’t it?
This is the public, documented removal procedure for Microsoft’s own blocked-senders list — not a guarantee of outcome or timeline. Microsoft’s own systems decide whether and when a given IP is actually removed; neither AdminKit nor any third party controls that decision.
Microsoft’s list isn’t a public DNSBL, so the DNS-based lookup explained on AdminKit’s blacklist check page doesn’t cover it. The way to confirm you’re affected is the exact wording of the bounce (NDR) message Microsoft already sent you. This guide is part of AdminKit’s email authentication cluster, alongside the other delisting and authentication guides linked throughout.
Microsoft runs two separate mail services with separate processes. Microsoft’s delist portal page covers mail to Microsoft 365 (business) recipients. Outlook.com, the consumer service, is covered by the Outlook.com postmaster site and its own codes.
Which error code did you get, and which path does it mean?
The removal path depends entirely on the code. Microsoft documents its Microsoft 365 codes in Email non-delivery reports and SMTP errors in Exchange Online, and its Outlook.com codes on the postmaster troubleshooting page.
| Code in the bounce | Microsoft’s description | Service | Path |
|---|---|---|---|
550 5.7.606–5.7.649 | Access denied, banned sending IP | Microsoft 365 | Self-service delist portal |
550 5.7.511 | Access denied, banned sender; the IP was banned | Microsoft 365 | Email delist@microsoft.com |
5.7.513 | Recipient domain blocked your IP with its own Customer Block list | Microsoft 365 | Contact the recipient |
5.7.507 | Rejected by recipient; their organization blocked the IP | Microsoft 365 | Contact the recipient |
5.7.509 | Sending domain fails DMARC and has p=reject | Microsoft 365 | Fix your SPF/DKIM/DMARC alignment |
550 SC-004 | Block placed because of complaints about mail from the IP | Outlook.com | Outlook.com sender support; enroll in JMRP |
550 OU-001 | Policy rejection; page points to Spamhaus for removal | Outlook.com | Spamhaus’s own process |
550 5.7.515 | High-volume domain lacks required SPF, DKIM and DMARC | Outlook.com | Fix authentication records |
421 RP-001–RP-003 | Rate or connection limit, tied to IP/domain reputation | Outlook.com | Slow down; work on reputation |
If an Outlook.com bounce points at a third-party list rather than a Microsoft-specific code, the actual removal procedure is that list’s own — see how to get delisted from Spamhaus or how to get delisted from Barracuda depending on which one is named. Outlook.com’s page also lists 550 DY-001 for mail from dynamic IPs, which it generally does not accept.
To decode the reply code and enhanced status code in any bounce line, paste it into AdminKit’s SMTP status code decoder. It explains the RFC codes in your browser; it doesn’t know Microsoft’s internal reasons.
What does a Microsoft 365 banned-IP bounce look like?
Microsoft publishes the template for this NDR on its delist portal page. The following is an illustrative example of that template filled in with a documentation address, not a real bounce:
550 5.7.606 Access denied, banned sending IP [198.51.100.25]: To request
removal from this list please visit https://sender.office.com/ and follow
the directions.
The two values you need are the IP in square brackets and the recipient address the bounce came back for. The 5.7.511 variant names delist@microsoft.com instead of the portal; Microsoft’s example of it reads “Access denied, banned sender[xxx.xxx.xxx.xxx]”.
If you aren’t sure the bracketed IP is really yours, compare it with your outbound address using AdminKit’s what is my IP tool from the sending host.
How do you use the delist portal for a 5.7.606–649 code?
You request removal yourself through the Office 365 Anti-Spam IP Delist Portal at sender.office.com. These are the steps from Microsoft’s documentation:
| Step | What you do | What Microsoft says about it |
|---|---|---|
| 1 | Open sender.office.com and follow the instructions | — |
| 2 | Enter the email address that received the NDR and the IP from the error | One email address and one IP per visit |
| 3 | Select Submit | A confirmation message is sent to the address you entered |
| 4 | Open the confirmation link in that message | It returns you to the portal |
| 5 | Select Delist IP | Removal can take up to 24 hours or longer |
Per Microsoft, results can vary widely before the restrictions are removed. Submitting the request doesn’t pause the block while it’s pending.
The NDR reference adds a precondition: check you follow Microsoft’s deliverability best practices and that your IP’s reputation isn’t degraded by compromise or malicious traffic. It describes the portal as the route “if you believe that you’re receiving this message in error.”
How do you handle a 5.7.511 code?
The delist portal explicitly does not handle this error. Microsoft says it uses 5.7.511 when it may need to investigate traffic from your IP further. Send an email to delist@microsoft.com including the full NDR code and the affected IP address.
Microsoft’s documentation states it will contact you within 48 hours with next steps. This is a manual review rather than a self-service form, so expect it to take longer than the portal path above.
How do you get delisted from Outlook.com, the consumer service?
Use the Outlook.com delisting form that Microsoft links from its delist portal page, and read the postmaster FAQ first, as that page asks. That FAQ is the postmaster troubleshooting page, which lists the Outlook.com codes in the table above.
The same page says its sender support form is only for issues with the Outlook.com system, meaning addresses at @outlook.com, @hotmail.com, @live.com and @msn.com. It states that submitting a request “does not guarantee” your mail will be delivered. It also says Outlook.com does not run an allow list that lets senders bypass its junk filters.
What should you fix before or while you request removal?
Fix whatever earned the block, or expect it to come back. Microsoft says that after delisting, mail still has to pass its built-in filtering, including composite authentication, and that you should make sure messages aren’t abusive or malicious, “otherwise, the IP address might be blocked again.”
Outlook.com’s troubleshooting page lists the factors its SmartScreen filters weigh: sending IP, domain, authentication, list accuracy, complaint rates and content. It names the junk complaint rate as one of the principal factors.
| Signal | What Microsoft says | What to check |
|---|---|---|
| Authentication | 5.7.509 rejects DMARC failures under p=reject; 5.7.515 rejects non-compliant high-volume senders | SPF, DKIM and DMARC alignment for every sending service |
| Complaint rate | A principal factor in Outlook.com reputation; SC-004 blocks follow complaints | List consent, unsubscribe handling, JMRP reports |
| Reverse DNS | Outlook.com may not accept mail from senders who fail a reverse-DNS lookup | PTR record on the sending IP |
| New IPs | No reputation yet, so more deliverability issues at first | Expect a ramp-up period; keep complaint rates low |
| Namespace mining | Verifying addresses without sending is not allowed; Microsoft acts on IPs that do it (SC-002) | Compromised hosts, address-validation tools |
| Shared or dynamic IP | DY-001: dynamic IPs generally not accepted | Send from a static, dedicated address |
- Authentication gaps. See SPF, DKIM and DMARC explained to check your domain’s current setup.
- A shared or dynamic IP. If the blocked IP is shared hosting, a VPS range, or CGNAT space, abuse from an unrelated customer on the same address can trigger a block regardless of anything you personally sent — see what is my IP and why is my IP address blacklisted for how shared addressing complicates this.
- Reverse DNS. Look up the sending IP’s PTR record with AdminKit’s reverse DNS lookup, and see PTR records and reverse DNS for mail servers for what a sensible one looks like.
- Sending volume or pattern changes. A sudden spike in volume, a new campaign to a purchased or stale list, or a high bounce/complaint rate are operational practices to review, not something a delist request alone resolves.
What are Outlook.com’s requirements for high-volume senders?
Domains sending more than 5,000 messages a day to Outlook.com must authenticate with SPF, DKIM and DMARC. Microsoft announced this in an April 2025 Tech Community post, with enforcement starting May 5, 2025.
The post lists three requirements: SPF must pass for the sending domain, DKIM must pass, and DMARC must be at least p=none and align with SPF or DKIM (preferably both). Its April 29 update says non-compliant messages are rejected with “550; 5.7.515 Access denied, sending domain [SendingDomain] does not meet the required authentication level.” The postmaster page lists the same 550 5.7.515 code.
How do SNDS and JMRP help you monitor reputation?
Separately from delisting, Microsoft offers Smart Network Data Services (SNDS), a free service showing per-IP data for addresses you’ve proved you control. It’s not a delisting tool — being enrolled doesn’t prevent or resolve a block — but it’s the clearest window Microsoft provides into how Outlook.com sees those IPs. SNDS now runs at a new address that replaces the old sign-up URL.
According to the SNDS FAQ, you sign in with a Microsoft account and request an IP range or ASN. SNDS then offers authorization addresses it finds through reverse DNS (such as postmaster@ and abuse@ at the hosts’ domain) or RDAP records. Access lasts 10 months before you must reattest.
| SNDS data point | What it shows |
|---|---|
| Activity period | First and last hour of the day the IP sent mail |
| RCPT, DATA, message recipients | SMTP command and recipient counts; a large gap can point to stale lists or namespace mining |
| Filter result | Green (spam under 10%), yellow (10–90%), red (over 90%) |
| Complaint rate | Complaints divided by message recipients |
| IP status | Whether the IP has an abnormal status, such as blocked |
The FAQ notes data may be missing for IPs that sent fewer than 100 messages that day. The Junk Email Reporting Program (JMRP), enrolled through SNDS, sends you reports when Outlook.com users mark your mail as junk. The Services page says feedback typically starts within as little as 72 hours.
This guide is general information, not a security audit of your specific network — see our disclaimer for what AdminKit's guidance does and does not commit to.
Frequently asked questions
My bounce shows error code 5.7.606 through 5.7.649 — what do I do?
That range means 'Access denied, banned sending IP' and is resolved through Microsoft's self-service Office 365 Anti-Spam IP Delist Portal at sender.office.com. Enter the email address that received the bounce and the IP address named in the error (one of each per visit), submit, then follow the confirmation link Microsoft emails to that address and select 'Delist IP.'
My bounce shows error code 5.7.511 instead — is the process different?
Yes — the delist portal explicitly does not handle this code. A 5.7.511 'Access denied, banned sender' error means Microsoft wants to review the traffic itself rather than offer self-service removal: send an email to delist@microsoft.com including the full NDR text and the IP address, and Microsoft states it will contact you within 48 hours with next steps.
How long does the delist portal take to actually clear the block?
Microsoft's own documentation says results 'can vary widely' and that it may take up to 24 hours or longer after you complete the portal steps. There's no guaranteed turnaround, and submitting the request doesn't pause or pre-approve anything while it's pending.
What's Smart Network Data Services (SNDS), and do I need it to get delisted?
SNDS is Microsoft's free, separate reputation-monitoring service for senders, showing complaint rates and filtering data for IPs you've verified you control. It's not a delisting mechanism by itself — you can be delisted via the portal above without ever using SNDS — but it's the closest thing Microsoft offers to visibility into why an IP might be flagged before it gets blocked, which is useful for a sender who delivers mail to Outlook/Hotmail regularly enough to monitor.
Will delisting stick if I haven't fixed the underlying cause?
Microsoft's own guidance is explicit that after delisting, mail still has to pass its built-in spam, spoofing and phishing filters to actually get delivered — otherwise 'the IP address might be blocked again.' A block usually reflects a real signal (complaint volume, authentication failures, spam-like sending patterns), and removing the block without addressing that signal is likely to result in the same IP being re-flagged.
My bounce says 5.7.513 or 5.7.507 — is that Microsoft's list?
No. Microsoft's Exchange Online error reference says 5.7.513 means the recipient's own organization added your IP to its custom block list, and 5.7.507 means the recipient's organization blocked the IP. The delist portal doesn't apply; contact the recipient and ask them to remove the block.
Does a 550 5.7.515 bounce from Outlook.com mean my IP is blocked?
No. Outlook.com's postmaster site lists 550 5.7.515 as a policy rejection for domains sending over 5,000 messages a day without SPF, DKIM and DMARC in place. It is fixed by correcting your authentication records, not by a delisting request.
Sources
- Microsoft Learn — Remove yourself from the blocked senders list and address 5.7.511 errors
- Microsoft — Office 365 Anti-Spam IP Delist Portal
- Microsoft — Smart Network Data Services (SNDS) sign-up
- Microsoft Learn — Email non-delivery reports and SMTP errors in Exchange Online
- Outlook.com Postmaster — Troubleshooting and SMTP error codes
- Outlook.com Postmaster — Services for senders and ISPs (SNDS, JMRP)
- Outlook.com SNDS — Frequently asked questions
- Microsoft Tech Community — Outlook's new requirements for high-volume senders
Want AdminKit to watch this for you?
Free checks tell you the state today. Protective DNS and monitoring tell you when it changes.
Talk to an expert
Huy Nguyen (David), Founder & CEO, Netbase JSC
Ask whether this fix applies to your setup, or get a second pair of eyes on your DNS and mail records.