|
Hey,
If your Azure bounces jumped last week, you're not imagining it.
Since 29 October, Microsoft has been rejecting cold email from Azure tenants with a bounce code it hasn't documented anywhere: 550 5.7.237
The worst-hit accounts got something worse: 550 5.7.708. That one doesn't block a message. It blocks the whole tenant's outbound.
So we pulled the data from our own fleet and our customers' tenants. Here's what decided who got hit… and who didn't.
Same Microsoft. Same weeks. Two outcomes.
Density and volume decided it.
|
25 users · ~76 sends a day
0 blocks
across 1,500+ tenants in 21 days
No tenant blocks, no licence wipes. Bounces held at 1.4% to 2.1%.
|
|
|
50 to 150 users · 200+ a day
Blocked
some tenants, outright
Bounces spiked first. Then the 5.7.708s arrived and the tenant went dark.
|
|
There's a third factor, and it might be the biggest: tenant age. The restriction looks aimed at tenants younger than about 10 to 14 days. Domains on older tenants kept sending through the same sequencer IPs. Prewarmed tenants with a month or more of warmup weren't touched.
In other words, Microsoft isn't going after cold email on Azure. It's going after brand new tenants that start blasting on day one.
Our own fleet
12,103 Microsoft inboxes. It went up. It stayed near 1 in 100.
|
0.62%
bounce rate, Oct 26 to 30
|
1.09%
bounce rate, Nov 2 to 5
|
2×
bounce rate on 100-inbox domains vs 50
|
The domains carrying 100 inboxes caught 80.9% of all our bounces. Same lesson as the customer data: the denser the setup, the harder Microsoft leaned on it.
Do this week
Five rules for Azure right now.
| 01 |
Keep tenants at about 25 users. One tenant, one domain, 25 inboxes. Not 100. |
| 02 |
Cap each tenant at 76 to 150 sends a day. That's the range the unaffected fleet ran at. |
| 03 |
No cold volume on tenants under 10 to 14 days old. Use prewarmed tenants, or warm new ones for a month first. And don't register a domain and send from it in the same week. |
| 04 |
Seeing 5.7.708? Stop that tenant. Move its volume to older tenants. Don't retry, the outbound is blocked. |
| 05 |
Seeing a wave of 5.7.237? Cut volume and users now, before it turns into a 5.7.708. Not sure which you've got? Paste your bounces into the free bounce analyzer, or ask the agent. |
|
What we don't know yet. Microsoft hasn't explained 5.7.237, and the tenant-age split is our diagnosis from affected accounts, not a counted result. We're still processing the numbers on the dense tenants and will update the study as they land. The raw data is free to download from the page.
|
If you're seeing these bounces right now, hit reply with the code and your setup: users per tenant, sends a day, how old the tenant is. I'll tell you exactly what I'd do.
And if you know someone running dense Azure tenants, forward this to them. Today, not next week.
|