What Is Mailbox Provisioning? A Plain Definition for Cold Email
Mailbox provisioning is the process of preparing an email mailbox so it can send and receive mail. At its smallest, that means creating one inbox under a domain and pointing the right DNS records at it. At the scale cold-email senders work in, it means doing this for dozens of mailboxes across multiple domains and tenants, in a way that holds up to sustained outbound volume. This post defines the term, walks through each step, and contrasts doing it by hand with handing it to a managed provider.
What “provisioning” actually means
In infrastructure terms, to provision something is to set it up and make it ready for use. A provisioned mailbox is one that exists, is authenticated, is correctly addressed by DNS, and can be loaded into a sending tool. An unprovisioned domain is just a name you bought; it cannot send anything until the surrounding pieces are in place.
For cold email specifically, provisioning is not a one-time act. Sending domains wear out under sustained outbound volume, often within a few months, and faster at higher daily volume per mailbox. So provisioning at scale is really a rolling process: you stand up new mailboxes and domains, ramp them, and retire worn ones over time. The setup work described below repeats.
The steps of provisioning a mailbox at scale
Provisioning one mailbox for a cold-email operation involves a chain of dependent steps. Each one has to be correct, or the mailbox underdelivers or never sends at all.
1. Register and prepare a sending domain
A sending domain is the domain that appears in your “from” address (for example, hello@yourbrand-mail.com). Senders typically register secondary domains for outbound rather than risk their primary brand domain. The domain has to be registered, owned, and pointed at name servers you control so its DNS can be configured.
2. Create a tenant
A tenant is an isolated instance of an email platform that holds the mailboxes for a domain. With Microsoft 365, one sending domain maps to one isolated Microsoft 365 tenant, which can host up to 100 mailboxes. “Isolated” matters: a real tenant is not a shared mailbox pool sitting behind one IP that hundreds of unrelated senders also use. The tenant is the container the mailboxes live in, and it has to be created and verified before mailboxes can be added.
3. Create the mailboxes
Inside the tenant, you create the individual mailboxes — the actual user inboxes that send and receive mail. For this use case a single domain and tenant commonly hosts on the order of 50 to 100 mailboxes, and each mailbox sends a small, ramped daily volume rather than blasting at full rate. Each mailbox needs a user, a password, and a defined sending identity.
4. Configure DNS authentication
This is the step that most often gets done wrong. Three DNS records tell receiving mail servers that your domain is allowed to send and has not been spoofed:
- SPF (Sender Policy Framework): a DNS record listing which servers are permitted to send for the domain.
- DKIM (DomainKeys Identified Mail): a cryptographic signature that proves a message was sent by the domain and was not altered in transit.
- DMARC (Domain-based Message Authentication, Reporting and Conformance): a policy that tells receivers what to do when SPF or DKIM checks fail, and where to send reports.
If these are missing or misconfigured, mailboxes typically land in spam or get rejected regardless of how good the content is. Authentication is the floor, not a bonus.
5. Export the mailboxes to a sequencer
A sequencer (or cold-email tool) is the software that actually runs your outbound campaigns and sends from your mailboxes on a schedule. The final provisioning step is connecting each mailbox to your sequencer, usually by entering its credentials or connection settings so the tool can send through it. Standard Microsoft 365 mailboxes connect to common cold-email sequencers using ordinary inbox connection settings. Once a mailbox is exported and ramped, it is ready to carry campaigns.
Manual provisioning vs managed provisioning
You can do all of the above yourself, or pay a provider to do it. The work is identical; the difference is who carries the operational load and how it scales.
Manual provisioning means you register domains, set up tenants, create mailboxes, edit DNS records by hand, and wire everything into your sequencer. It is the cheapest in cash and the most expensive in time and attention. The error surface is large: one wrong SPF entry or a missing DKIM key can quietly tank deliverability for a whole domain, and you only notice when reply rates fall.
Managed provisioning means a provider stands up the domains, tenants, mailboxes, and DNS for you, hands you ready-to-send mailboxes, and monitors them over time. You trade some control and some money for speed and for not having to become a DNS and tenant administrator.
| Manual provisioning | Managed provisioning | |
|---|---|---|
| Domain registration | You do it | Provider does it |
| Tenant creation | You set up each tenant | Provider sets up each tenant |
| Mailbox creation | One at a time, by you | Done in bulk for you |
| DNS (SPF/DKIM/DMARC) | You edit records by hand | Provider configures and verifies |
| Replacing worn domains | You notice and rebuild | Provider monitors and replaces |
| Upfront time | High | Low |
| Control | Full | Partial |
Neither is automatically correct. A technical solo sender running one or two domains may be fine doing it by hand. An operator running many overlapping domains, rotating them as they burn, usually finds the manual approach turns into a part-time job.
A note on what provisioning does not do
Provisioning makes a mailbox technically able to send. It does not make your sending permitted under law. DNS records, isolated tenants, and where your mailboxes are hosted are infrastructure questions — they govern how and from where mail is sent, not whether you are allowed to email a given person. Many markets, including Germany under UWG §7(2), require prior opt-in even for B2B outreach. Consent and local law are the sender’s responsibility, and no provisioning setup changes that.
How Mailionaire approaches provisioning
Mailionaire provides managed provisioning. For each active sending domain, it registers and prepares the domain, creates an isolated Microsoft 365 tenant, creates the mailboxes (up to 100 per domain), and configures SPF, DKIM, and DMARC, then hands you mailboxes ready to connect to your sequencer. Because domains wear out, it monitors deliverability signals and replaces worn mailboxes and domains as part of the service rather than leaving you to rebuild. Pricing is flat at $50 per month per active domain with no per-mailbox metering, and there is a 14-day money-back guarantee instead of a free trial. You can see the full sequence on the how it works page.
FAQ
What is mailbox provisioning in one sentence?
It is the process of preparing an email mailbox — including its domain, tenant, and DNS authentication — so it can send and receive mail through a sending tool.
How many mailboxes can one domain have?
For cold-email use, a single domain and its tenant commonly hosts on the order of 50 to 100 mailboxes. With Microsoft 365, one tenant supports up to 100 mailboxes, each sending a small, ramped daily volume.
Do I need to provision new mailboxes regularly?
In practice, yes. Sending domains wear out under sustained cold-email volume, often within a few months, so senders typically run several overlapping domains and rotate, provisioning replacements over time.
Does provisioning make my cold email legal?
No. Provisioning and infrastructure decide how and from where mail is sent, not whether you are allowed to send it. Consent and compliance with local law, such as Germany's opt-in requirement, remain the sender's responsibility.
Mailionaire provisions real, isolated Microsoft 365 mailboxes for cold email — built in Switzerland, with optional EU/Swiss data residency — then monitors and replaces them as they wear out. One flat price per domain. See how it works →