Most cold email setups follow a simple rule: about 3 inboxes per domain on Google Workspace or Microsoft 365. Azure bulk inboxes break that rule on purpose. They put many Outlook inboxes on one domain for a flat price. This guide explains how they work, what they cost compared with the alternatives, and when putting many inboxes on one domain actually makes sense.
What Azure bulk inboxes are
Azure bulk inboxes are Outlook mailboxes created in bulk on Microsoft’s Azure infrastructure. To a prospect they look like any other Outlook email. To your sending tool they connect like Microsoft inboxes. The difference is how they are set up and priced: many inboxes per domain, one flat price per domain.
Each domain still gets its own MX, SPF, DKIM and DMARC records, the same as a Microsoft 365 domain. The full list is on our Azure inboxes page.
How the pricing works
You pay $40 per domain a month, whether you put 10 inboxes on it or 100. So the cost per inbox depends on how many you use:
| Inboxes on the domain | Monthly cost | Cost per inbox |
|---|---|---|
| 10 | $40 | $4 |
| 25 | $40 | $1.60 |
| 50 | $40 | $0.80 |
| 100 | $40 | $0.40 |
Compare that with Google Workspace at $3 and Microsoft 365 at $3.50 per inbox a month, where every inbox costs the same no matter how many you have.
Azure vs Google Workspace vs Microsoft 365
| Google Workspace | Microsoft 365 | Azure bulk | |
|---|---|---|---|
| Price | $3 per inbox a month | $3.50 per inbox a month | $40 per domain a month |
| Inboxes per domain | 3 recommended, 5 max | 3 recommended, 5 max | Up to 100 |
| Domains for 100 inboxes | 34 | 34 | 1 to 4 |
| Monthly cost for 100 inboxes | $300 | $350 | $40 and up |
| Best for | Most teams, any volume | Prospects on Outlook, any volume | Experienced high-volume teams |
On cost alone, Azure wins at volume. It also needs far fewer domains, which means fewer domains to buy, renew, set up and monitor. For more on the two main providers, see Google Workspace vs Microsoft 365 for cold email.
The trade-off: one domain, many inboxes
Reputation is judged largely by domain. On Google Workspace with 3 inboxes per domain, a flagged domain costs you 3 inboxes. On an Azure domain with 50 inboxes, a flagged domain costs you 50. Every bounce and complaint from any of those inboxes counts against the same domain.
That is why we recommend 3 per domain for most teams, and why Azure needs a different way of working. Read how many inboxes per domain for the reasoning behind the 3 per domain rule.
Who Azure suits, and who it does not
A good fit
- Agencies and teams already sending at high volume across many inboxes.
- Teams with clean, verified lists and low bounce rates.
- Senders who rotate inboxes in their tool and keep volume per inbox low.
- Teams that monitor reply and bounce rates per domain and act quickly.
Not a good fit
- Teams new to cold email, still learning what their lists and copy can handle.
- Small campaigns that only need 10 to 30 inboxes. Google or Microsoft at 3 per domain is simpler and costs about the same.
- Anyone sending to unverified lists, where bounces would hit one shared domain.
If you are not sure, start with Google Workspace or Microsoft 365 and add Azure once your campaigns are stable. Our cold email infrastructure cost guide compares the full monthly cost of each setup.
How to send from Azure safely
- Verify every list. Bounces on a shared domain add up fast. Remove invalid addresses before every campaign.
- Warm up every inbox before it sends campaigns, and bring inboxes into campaigns in stages rather than all at once. See how to warm up a cold email inbox.
- Keep volume per inbox low. The point of many inboxes is to spread volume thinly, not to push each one hard.
- Rotate inboxes in your sending tool, so each campaign draws from many inboxes.
- Grow the domain’s total volume slowly. A sudden jump in what one domain sends is a warning sign to mailbox providers.
- Watch each domain. Track bounce and reply rates per domain and pause any that slip. Our email deliverability checker confirms the DNS is still in place.
Connecting Azure inboxes to your tool
Azure inboxes connect like any Microsoft inbox: by Microsoft sign-in, or by IMAP and SMTP where your tool and the inbox allow it. Some tools, including Instantly, cannot import Microsoft inboxes from a CSV, so they are connected by Microsoft sign-in. When you order, you can ask us to connect them for you. Our guide to connecting inboxes to Instantly and Smartlead walks through both tools.
Frequently asked questions
What are Azure bulk inboxes?
Outlook mailboxes created in bulk on Microsoft’s Azure infrastructure, with many inboxes on each domain and a flat price per domain rather than per inbox.
How many inboxes can I put on one Azure domain?
With us, up to 100 inboxes per domain. You do not have to use all of them, and many teams start well below that and add inboxes as they learn how the domain performs.
Are Azure inboxes cheaper than Google Workspace?
Per inbox, yes, once you put enough inboxes on each domain. Because Azure is priced per domain, the cost per inbox falls as you add inboxes. With only a few inboxes per domain, Google Workspace or Microsoft 365 is cheaper.
Are Azure inboxes good for beginners?
Usually not. Many inboxes share one domain’s reputation, so mistakes are more costly. If you are new to cold email, start with Google Workspace or Microsoft 365 at 3 inboxes per domain.
Do Azure inboxes need warm-up?
Yes. Every inbox needs warm-up before it sends campaigns, and the domain’s total volume should grow slowly as more inboxes start sending.
Which sending tools work with Azure inboxes?
Any tool that connects Outlook inboxes, either by Microsoft sign-in or by IMAP and SMTP. Some tools, including Instantly, cannot import Microsoft inboxes from a CSV, so they are connected by Microsoft sign-in instead.