---
title: "Microsoft 5.7.237 and the Azure Tenant Crackdown: Fleet Data"
description: "Microsoft 5.7.237 and 5.7.708 across three segments: 1,500+ tenants at 25 users unharmed; 142 dense tenants refused, 49% bouncing, then under 1%."
url: https://warminboxes.com/research/microsoft-azure-tenant-crackdown
breadcrumb: "Home > Blog > Research > Azure Tenant Study"
---
[WarmInboxes.com](https://warminboxes.com/)
 [Offer](https://warminboxes.com/offer)
 [Free Leads](https://warminboxes.com/leads)
 [Free Tools](https://warminboxes.com/deliverability-tools)
 [Blog](https://warminboxes.com/blog)
 [Reviews](https://warminboxes.com/reviews)

[Home](https://warminboxes.com/) › [Blog](https://warminboxes.com/blog) › [Research](https://warminboxes.com/research) › Azure Tenant Study

[Blog](https://warminboxes.com/blog)[Deliverability Research](https://warminboxes.com/research)
Azure Tenant Study

Original research

10 min read

# Microsoft’s Azure tenant crackdown and the 550 5.7.237 bounce: what three fleets showed

From 29 October 2026, vendors and senders across sequencers started reporting a bounce code nobody had seen before, 550 5.7.237, on Microsoft tenants. Here is what it did to three fleets we can see into, in three segments: two of our customers’ and our own.

WarmInboxes original research · WI-RESEARCH-2026-004

·

Fieldwork: 20 October to 8 November 2026

Download PDF reportSave for later

Share this

The data behind this study

Every figure on this page is computed from these files. Fieldwork 20 October to 8 November 2026. Licensed [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/): reuse with attribution to WarmInboxes.com.

- [JSONmicrosoft-azure-tenant-crackdown.json](https://warminboxes.com/research/microsoft-azure-tenant-crackdown.json)
- [CSVmicrosoft-azure-tenant-crackdown-days.csv](https://warminboxes.com/research/microsoft-azure-tenant-crackdown-days.csv)
- [CSVmicrosoft-azure-tenant-crackdown-configs.csv](https://warminboxes.com/research/microsoft-azure-tenant-crackdown-configs.csv)
- [CSVmicrosoft-azure-tenant-crackdown-segment-2-days.csv](https://warminboxes.com/research/microsoft-azure-tenant-crackdown-segment-2-days.csv)
- [CSVmicrosoft-azure-tenant-crackdown-segment-2-traces.csv](https://warminboxes.com/research/microsoft-azure-tenant-crackdown-segment-2-traces.csv)
- [CSVmicrosoft-azure-tenant-crackdown-segment-2-watch.csv](https://warminboxes.com/research/microsoft-azure-tenant-crackdown-segment-2-watch.csv)

## The short version

0 / 0

Segment 1: tenant blocks / licence wipes across 1,500+ customer tenants at 25 users

1.4–2.1%

Segment 1: bounce rate across those tenants, at 76 sends per tenant on an active day

49.0%

Segment 2: of everything the dense tenants sent on Oct 27–30, this much bounced

0.94%

Segment 2: the same tenants' bounce rate on Nov 1–2, once Microsoft lifted the block

0.62% → 1.09%

Segment 3: our own fleet's bounce rate, Oct 26–30 against Nov 2–5

2.0×

Segment 3: bounce rate on our 100-inbox domains against our 50-inbox domains

Segment 1 came through untouched. Customer tenants at 25 users, sending around 76 a day and up to 162 on the busiest, had no blocks and no licence wipes.

Segment 2 got blocked, then came back. 142 dense customer tenants at 50 or 100 users had their outbound refused with 550 5.7.708 from 20 October 2026. On Oct 27–30, 49.0% of everything they sent bounced. By Nov 1–2 it was 0.94%, and from Nov 3 there wasn’t a single 550 5.7.708. Not one licence was suspended.

Segment 3, our own fleet, stepped up and stayed low. Bounce rate went from 0.62% to 1.09% across 12,103 Microsoft inboxes, about 1.7× and still around one in a hundred, with the densest domains carrying most of it.

## The three segments

| Segment | Tenants | Window | What happened |
| --- | --- | --- | --- |
| [Segment 1](#segment-1)Customer tenants, 25 users each | 1,500+ | Last 21 days | 1.4–2.1% bounces, no blocks, no licence wipes |
| [Segment 2](#segment-2)Customer tenants, 50 or 100 users each | 142 | Oct 20 – Nov 8 | Outbound refused with 550 5.7.708; 49.0% bounced, then 0.94% |
| [Segment 3](#segment-3)Our own agency fleet, two workspaces | 12,103 inboxes | Oct 26 – Nov 5 | 0.62% → 1.09%, heaviest on 100-inbox domains |

## What happened

From 29 October 2026, reports came in from several infrastructure vendors and from senders themselves: Microsoft was restricting Azure tenants used for cold email, and bounces carrying `550 5.7.237` were appearing across sequencers. Operators started calling it a crackdown.

Microsoft has not said what 5.7.237 means. We found no Microsoft documentation for the code as of 6 November 2026. Microsoft’s guidance groups the 5.7.x family as policy and permission rejections, so it reads as a policy refusal rather than a bad address, but that is a reading of the family, not of the code. Paste one into the [bounce analyzer](https://warminboxes.com/bounce-analyzer) and it is named for what it is.

The worst-affected accounts saw something harsher: `550 5.7.708 Service unavailable. Access denied, traffic not accepted from this IP`. That is not a refusal of one message but of the tenant’s outbound traffic. Microsoft’s own [Q&A threads](https://learn.microsoft.com/en-us/answers/questions/5786886/550-5-7-708-access-denied-traffic-not-accepted-fro) tie it to Exchange Online blocking outbound mail from a low-reputation IP, most often on new or trial tenants. And it started earlier than anyone reported: Segment 2’s Exchange records show 550 5.7.708 from 20 October 2026, nine days before the first 5.7.237 reports.

## The diagnosis: tenant age

Working through the affected accounts, the restriction appears to fall on tenants younger than about 10 to 14 days. Domains placed on older tenants performed normally, even sending through the same sequencer IPs as the ones being refused, which points at the tenant rather than the IP pool behind the sequencer.

It fits the three segments. Segment 1’s 1,500+ tenants with no blocks were established tenants, and the prewarmed ones with a month or more of warmup behind them were not affected at all. Segment 2’s refusals ran for about two weeks, from 20 October 2026 to 2 November, and then stopped while the tenants kept sending, which is what tenants ageing out of a restriction would look like. It also fits 550 5.7.708’s association with new tenants.

This is a diagnosis from the accounts we worked, not a counted split: the Exchange records do not carry tenant age, and we have not yet tallied every tenant by age against its outcome. We will publish that if the pattern holds.

What it changes for anyone buying Microsoft infrastructure: a brand-new tenant is now the riskiest place to start cold volume. Inboxes on tenants that are already weeks old and warmed, which is what a prewarmed pool is, and sending domains aged before they carry cold mail, are worth more now than they were a month ago.

## Method

| Segment 1 | 1,500+ customer tenants WarmInboxes built at 25 users each. Read from the tenants over the last 21 days: tenant count, average and peak daily sends, bounce range, tenant blocks and licence wipes. The fleet's total sends and bounces are worked out from those, with the formula shown. |
| --- | --- |
| Segment 2 | 142 customer tenants at 50 or 100 users (73 and 69), the ones that were hitting 550 5.7.708 when we pulled the October data. Read from Microsoft's Exchange records: every failed send on all 142 for Oct 20–30, two windows with full send counts (Oct 27–30 and Nov 1–2), hourly checks of Microsoft's bounce notices to Nov 8, and one licence check on 3 November 2026. These overlap in time, so we never add their counts together. Dates as the traces recorded them (India Standard Time). |
| Segment 3 | Our own agency fleet, 12,103 Microsoft inboxes across two workspaces. Sends and bounces per day, per workspace and per inboxes-per-domain configuration, read from the sequencer for 26 October to 5 November 2026. |
| Tenant block | Outbound sending refused for the whole tenant, every user at once: 550 5.7.708. |
| Licence wipe | The tenant's mailbox licences removed, so the users stop existing as mailboxes. |
| Named | No customer, vendor, domain or sequencer. Workspaces are lettered. |

Segment 1

## Customer tenants at 25 users: no blocks, no wipes

Over the last 21 days, across 1,500+ Microsoft tenants we built at 25 users per tenant and domain, warming ones included:

- 76 sends per tenant on an average active day; the busiest tenant on its busiest day sent 162.
- Bounce rate between 1.4% and 2.1% across the range.
- 0 tenant blocks and 0 licence wipes.
- Tenants sending 76 to 150+ a day were fine, and prewarmed tenants with a month or more of warmup behind them were not affected at all.

The numbers

Over 26 October to 6 November 2026, 12 days, that fleet sent up to **1,368,000** emails (1,500 tenants × 76 sends × 12 days), of which **19,152 to 28,728** bounced at the measured 1.4–2.1%. The sends take every tenant at its active-day average every day, so they are the ceiling, and 1,500 is the floor of the tenant count.

Segment 2

## Customer tenants at 50 or 100 users: refused, then recovered

142 dense customer tenants, 73 at 50 users and 69 at 100, each sending around 220 cold emails a day. These are the tenants that were getting hit when we pulled the October data, so this shows how hard it hit and for how long, not how many dense tenants got hit.

### Refused from Oct 20

Between Oct 20 and Oct 30, Microsoft’s records for these 142 tenants show 117,605 failed sends. 113,244 of them, 96.3%, were 550 5.7.708: the tenant’s outbound refused, not a bad address. Every single tenant had them. Oct 20 is as far back as the records go, so it may have started earlier.

| Date | Failed sends | With 550 5.7.708 |
| --- | --- | --- |
| Oct 20 | 13,790 | 13,751 |
| Oct 21 | 9,514 | 9,432 |
| Oct 22 | 10,828 | 10,710 |
| Oct 23 | 17,249 | 17,095 |
| Oct 24 | 11,590 | 11,438 |
| Oct 25 | 14,407 | 14,229 |
| Oct 26 | 9,946 | 9,682 |
| Oct 27 | 4,786 | 4,126 |
| Oct 28 | 10,761 | 9,167 |
| Oct 29 | 14,288 | 13,170 |
| Oct 30 | 446 | 444 |

These records count failures, not sends, so they don’t give a bounce rate on their own. The two windows below do. Oct 30 is a part day.

### Half of everything bounced, then under 1%

| Window | Tenants | Sent | Bounced | Rate | 550 5.7.708 |
| --- | --- | --- | --- | --- | --- |
| Oct 27–30 | 59 | 55,191 | 27,067 | 49.0% | 26,750 |
| Nov 1–2 | 135 | 170,290 | 1,595 | 0.94% | 966 |

Oct 27–30: 27,067 of 55,191 bounced. That’s 49.0%, and 98.8% of those were 550 5.7.708. The median tenant bounced 52.0%, 42 of 59 were above 40%, and not one was under 2%.

Nov 1–2: 1,595 of 170,290, or 0.94%, with tenants sending around 600 a day. The median tenant bounced 0.3%, 132 of 135 were under 2%, and there was no 5.7.237 on any of them.

The two windows don’t cover exactly the same tenants, so we checked the 52 that are in both: 48.5% on Oct 27–30, 1.72% on Nov 1–2. Same tenants, same drop.

Inbox count didn’t make a difference here. On Oct 27–30 the 50-inbox tenants bounced 49.9% and the 100-inbox tenants 46.5%, even though the 50s were sending more each (around 465 a day against 144).

### Gone by Nov 3

We check Microsoft’s bounce notices every hour. This is how many tenants showed any 550 5.7.708 each day, out of the ones we could read in full.

| Date | Tenants with 550 5.7.708 | Tenants checked |
| --- | --- | --- |
| Oct 31 | 24 | 126 |
| Nov 1 | 3 | 125 |
| Nov 2 | 1 | 125 |
| Nov 3 | 0 | 125 |
| Nov 4 | 0 | 125 |
| Nov 5 | 0 | 125 |
| Nov 6 | 0 | 125 |
| Nov 7 | 0 | 125 |
| Nov 8 | 0 | 125 |

No licence was suspended. When we checked on 3 November 2026, 135 tenants had their Microsoft licences enabled and none were suspended; the other 7 couldn’t be read that day. 550 5.7.708 blocks a tenant’s mail. It doesn’t take its mailboxes away.

Segment 3

## Our own agency fleet, day by day

12,103 Microsoft inboxes across two workspaces, 26 October to 5 November 2026: 188 bounces on 19,876 sends, 0.95%.

| Date | Sent | Bounced | Rate |
| --- | --- | --- | --- |
| Oct 26 | 1,587 | 6 | 0.38% |
| Oct 27 | 496 | 4 | 0.81% |
| Oct 28 | 2,711 | 21 | 0.77% |
| Oct 29 | 1,369 | 8 | 0.58% |
| Oct 30 | 399 | 2 | 0.50% |
| Oct 31 | 30 | 0 | 0.00% |
| Nov 1 | 83 | 3 | 3.61% |
| Nov 2 | 4,976 | 59 | 1.19% |
| Nov 3 | 3,338 | 36 | 1.08% |
| Nov 4 | 2,491 | 22 | 0.88% |
| Nov 5 | 2,396 | 27 | 1.13% |

The step came on Nov 2. Oct 26–30 ran at 0.62% (41 on 6,562); Nov 2–5 at 1.09% (144 on 13,201). Nov 2 was also the biggest send day by far, 4,976, so volume and the new code arrived together. Oct 31 and Nov 1 sent 113 between them; Nov 1’s 3.61% is 3 bounces and reads as noise.

### By inboxes per domain

| Configuration | Sent | Bounced | Rate | Share of bounces |
| --- | --- | --- | --- | --- |
| 100 inboxes per domain | 14,120 | 152 | 1.08% | 80.9% |
| 50 inboxes per domain | 4,197 | 23 | 0.55% | 12.2% |
| 25 inboxes per domain | 1,548 | 13 | 0.84% | 6.9% |
| 3 or 1 inbox per domain | 11 | 0 | 0.00% | 0.0% |

The 100-inbox domains carry 80.9% of the bounces. They carry most of the volume too, but they still bounce at 2.0× the rate of the 50-inbox domains, 1.08% against 0.55%.

It is not a clean line: the 25-inbox domains sit between them at 0.84%, on 1,548 sends, which is too few to rank against the 50s with confidence. Read it with segments 1 and 2, where the difference between 25 and 50+ users was blocks against none.

### By workspace

| Workspace | Sent | Bounced | Rate | Share of bounces |
| --- | --- | --- | --- | --- |
| Workspace A | 12,240 | 133 | 1.09% | 70.7% |
| Workspace B | 7,636 | 55 | 0.72% | 29.3% |

## What this study does not show

- What 5.7.237 means. Microsoft has not published it; this records what the fleets did.
- A counted split by tenant age. The 10 to 14-day line is our diagnosis from the affected accounts.
- Cause. Density, daily volume and the new restriction arrived together; the fleets show which tenants were hurt, not why Microsoft chose them.
- How many dense tenants were hit. Segment 2 is the 142 tenants that were hit, so it shows how hard and for how long, not what share.
- A bounce rate for every day of Segment 2. Microsoft’s records count failures without sends, so the rates come from the two windows with full send counts.
- Send-by-send totals for segment 1. Its fleet totals come from the tenant count and averages, with the sends as the ceiling.
- A heavy-volume agency test. Our own fleet sent about 1.6 emails per inbox over the whole window, so it shows the step in bounce rate, not how it holds at full pace.
- Google Workspace or Microsoft 365 bought direct. Every tenant here is Azure, built for cold email.

## What to do with this

- Keep Azure tenants at about 25 users per tenant and domain, and daily sends per tenant in the 76–150 range the unaffected fleet ran at.
- Do not start cold volume on a tenant younger than about 10 to 14 days. Start on prewarmed tenants, or give new ones a month of warmup first: prewarmed tenants with a month or more behind them were unaffected.
- Age sending domains before they carry cold email, rather than registering and sending in the same week.
- If a tenant bounces 550 5.7.708, its outbound is blocked: stop sending from it, and move its volume to older tenants rather than retrying.
- Treat a wave of 550 5.7.237 as a tenant-level warning: cut that tenant’s volume and users before it becomes a block, and check the bounces with the [bounce analyzer](https://warminboxes.com/bounce-analyzer).

[Prewarmed Azure inboxes on established tenants](https://warminboxes.com/azure-inboxes)[Analyse your bounces](https://warminboxes.com/bounce-analyzer)

Hit by this?

## Move your Azure to us and pay what you pay now

If your tenants are bouncing 550 5.7.708 or 5.7.237, you don’t have to rebuild on your own. Tell us what you pay your current vendor for fresh Azure inboxes and, depending on your volume, we’ll match it.

At that price you get the whole suite:

- Client workspaces
- Automated domain forwarding to your website
- Deliverability monitoring (daily blacklist, SPF, DKIM, DMARC and expiry checks; the dashboard is in closed beta)
- Expert technicians on WhatsApp

And you get the team that ran Segment 1 through this. We set tenants up at 25 users, keep each one’s daily sends in the range that came through untouched, and warm new tenants before they carry cold mail, because a brand-new tenant is exactly what got hit. If you need to send this week, our prewarmed Azure tenants are already past that age (prewarmed isn’t part of the price match).

[Get a price match on WhatsApp](https://api.whatsapp.com/send/?phone=19047362539&text=Hey%2C%20I%20want%20a%20price%20match%20on%20my%20inboxes&type=phone_number&app_absent=0)[Book a consultation](https://warminboxes.com/consultation)

Read next

- [The inbox placement log](https://warminboxes.com/research/inbox-placement-log): every seed test on the prewarmed batches we build, Azure included.
- [Top-level domains by sends](https://warminboxes.com/research/google-sender-reputation): the Google side of reputation, measured send by send across five top-level domains.
- [All WarmInboxes studies](https://warminboxes.com/research), each with its data and citation.

[Back to the studies](https://warminboxes.com/research)

## Prewarmed & Fresh Inboxes

Google, Microsoft 365 and Azure inboxes with free prewarmed domains and DNS configured before you log in. Prewarmed inboxes send the day they land; every order is delivered within 48 to 72 hours.

 [Get Prewarmed & Fresh Inboxes](https://app.warminboxes.com)

More from WarmInboxes

[Google Workspace Inboxes](https://warminboxes.com/google-workspace-inboxes)[Microsoft 365 Inboxes](https://warminboxes.com/microsoft-365-inboxes)[Azure Inboxes](https://warminboxes.com/azure-inboxes)[Cold Email Notes](https://warminboxes.com/blog/notes)[Deliverability](https://warminboxes.com/deliverability)[Terms of Service](https://warminboxes.com/terms)[Privacy Policy](https://warminboxes.com/privacy)[Developers](https://warminboxes.com/developers)[Deliverability Agent](https://warminboxes.com/deliverability-agent)[Free Tools MCP](https://warminboxes.com/mcp-tools)[For AI Agents](https://warminboxes.com/for-ai)[Inboxes for Instantly](https://warminboxes.com/instantly-inboxes)[Inboxes for PlusVibe](https://warminboxes.com/plusvibe-inboxes)[Inboxes for Smartlead](https://warminboxes.com/smartlead-inboxes)[Inboxes for EmailBison](https://warminboxes.com/emailbison-inboxes)[Inboxes for Apollo](https://warminboxes.com/apollo-inboxes)[Inboxes for ManyReach](https://warminboxes.com/manyreach-inboxes)[Inboxes for Clay](https://warminboxes.com/clay-inboxes)[Inboxes for Claude](https://warminboxes.com/claude-inboxes)[Inboxes for ChatGPT](https://warminboxes.com/chatgpt-inboxes)[Inboxes for Grok](https://warminboxes.com/grok-inboxes)[About](https://warminboxes.com/about)[Huzayfa Majeed](https://warminboxes.com/authors/huzayfa-majeed)[How it works](https://warminboxes.com/how-it-works)[Deliverability Hub](https://warminboxes.com/deliverability-hub)[Platform](https://warminboxes.com/features)[Deliverability Monitoring](https://warminboxes.com/features/deliverability-monitoring)[Automated Reconnections](https://warminboxes.com/features/automated-reconnections)[Client Workspaces](https://warminboxes.com/features/client-workspaces)[State of Cold Email](https://warminboxes.com/state-of-cold-email)[Gemini](https://warminboxes.com/gemini)[Warm Rotation](https://warminboxes.com/warm-rotation)[Studies](https://warminboxes.com/research)[Placement Test Log](https://warminboxes.com/research/inbox-placement-log)[Top-Level Domains](https://warminboxes.com/research/google-sender-reputation)[Azure Tenant Study](https://warminboxes.com/research/microsoft-azure-tenant-crackdown)[SURBL Study](https://warminboxes.com/research/surbl-blocklist-study)[Playbooks](https://warminboxes.com/playbooks)[Calculator](https://warminboxes.com/calculator)[Consultation](https://warminboxes.com/consultation)[Affiliate Program](https://warminboxes.com/affiliate)[Tool demos](https://warminboxes.com/videos)[Testimonials](https://warminboxes.com/testimonials)[Reddit Reviews](https://warminboxes.com/reddit)[Prewarmed on Reddit](https://warminboxes.com/prewarmed/reddit)[Inboxes on Reddit](https://warminboxes.com/inboxes/reddit)[Revenue Boost](https://warminboxes.com/revenueboost)[MailFirst](https://warminboxes.com/mailfirst)[Agency Advanta](https://warminboxes.com/agencyadvanta)[Liquid Syntax Guide](https://warminboxes.com/playbooks/liquid-syntax-guide)[The SPAM Plague](https://warminboxes.com/playbooks/spam-plague-segmentation-playbook)[Inboxing Playbook](https://warminboxes.com/inboxing-playbook)[Data Ops Hub](https://warminboxes.com/hub/data-ops)[Agency Hub](https://warminboxes.com/hub/cold-email-agency)[Deliverability AI for ChatGPT](https://warminboxes.com/chatgpt-plugin)[Deliverability AI for Claude](https://warminboxes.com/claude-connector)

Contact

[WhatsApp +1 904 736 2539](https://api.whatsapp.com/send/?phone=19047362539&text=Hey%2C%20I%20need%20WarmInboxes&type=phone_number&app_absent=0)
 ·
 [support@warminboxes.com](mailto:support@warminboxes.com)
 ·
 Pembroke Pines, FL 33024, USA