What’s the impact of shared vs dedicated IPs at Microsoft?
Still have a question, spotted an error, or have a better explanation or a source we should cite?
Here's a scenario that plays out more often than senders expect. You're on a shared IP, your campaigns are performing fine, and then out of nowhere your Outlook delivery tanks. You didn't change anything. But someone else on that IP did, and Microsoft noticed.
Microsoft leans on IP reputation harder than most other mailbox providers. It feeds directly into how Microsoft scores your mail before it ever reaches content filtering. A troubled IP can drag your messages to junk or block them entirely, even if your domain reputation is solid.
With a shared IP, you're pooling that reputation with everyone else your ESP puts on the same address. Reputable ESPs police their shared pools, so for most senders this works fine. But the risk is real. One high-complaint sender on your IP can cause Microsoft to throttle or block the whole range. You'll see errors like 421 RP-001 and have limited recourse because it's not your IP to remediate.
With a dedicated IP, you own the reputation entirely. That's the upside. The catch is that Microsoft expects consistent, predictable sending volume from a dedicated IP. If you're sending 10,000 emails one week and nothing the next, Microsoft treats that pattern as suspicious. Think of it like a new face walking into the post office every few weeks. Familiarity matters. Dedicated IPs need a proper warmup period and a reliable ongoing volume, roughly 50,000 to 100,000 sends per month at minimum to stay warm and trusted.
Your authentication setup matters here too. Whether you're on shared or dedicated, Microsoft wants to see clean SPF, DKIM, and DMARC alignment. A dedicated IP with broken authentication still gets filtered aggressively. Authentication doesn't replace IP reputation at Microsoft. It works alongside it.
The practical breakdown looks like this:
- Under 50k sends/month: stay on a quality shared IP. You'll benefit from the ESP's established sending reputation and you won't starve a dedicated IP of the volume it needs to build trust.
- 50k to 200k sends/month: shared IP is still reasonable, but it's worth asking your ESP which pool you're in and how they monitor it.
- 200k+ sends/month with consistent cadence: a dedicated IP starts to make sense. You have the volume to warm it properly and you take full control of your Microsoft reputation.
You can also check whether your IP is currently listed with our free blocklist checker. If something looks off and you're not sure where to start, our SOS hotline is free and someone will actually pick up.
Contributors
Who worked on this answer
Every name links to their profile. Every company links to their site. Real people, real accountability.