Buy Outlook 365 Tenant Accounts in Bulk, from Domain Checks to Send Ramps and 2026 Pricing

The short version before you buy Outlook 365 tenant accounts

You buy Outlook 365 tenant accounts for one narrow reason, and the spend only pays back when your list is heavy with business recipients. In that situation a Microsoft 365 tenant seat is worth 10 to 25 times a free Outlook.com inbox, and outside it the seat is worth almost nothing. Fresh tenant seats trade in the $30-45 band, aged and warmed seats in the $55-90 band, and neither number makes sense unless at least half your recipients sit behind Exchange Online. When they do, tenant seats land B2B mail at 45-78% against 12-38% from consumer Outlook addresses, and the price stops looking like a premium.

If you already know the consumer side of the platform, this page skips it. Our Outlook bulk buying comparison covers Outlook.com inboxes and how they stack against tenant seats. What follows is tenant-only: what sits underneath the seat, which license to order, what DNS should look like on delivery day, how many seats one tenant safely carries, and how to test a batch before you scale.

Three assets stack under every tenant seat

Buyers treat a tenant account as a single item. It is three, and each one fails differently.

The domain

Someone registered a domain, and it has an age. That age drives filtering behavior at every major receiver. A domain registered eight days ago will underperform an identical setup on a 90-day domain by roughly 15-25 percentage points of inbox placement, no matter how clean the authentication is. Domain quality also covers the obvious things sellers skip: a resolving website on the root, plausible WHOIS, and no prior history on spam blocklists. Check the domain against a blocklist lookup before you accept anything.

The tenant

The tenant is the Microsoft 365 organization itself, provisioned on that domain with a billing method attached and a global administrator account. This is where the enforcement risk lives. Microsoft frequently acts at the tenant level, so a violation traced to one mailbox can disable every seat inside the organization at once. It is also where the recurring cost lives, since an unpaid subscription silently disables mailboxes 30 days after a failed charge.

The seat

The seat is the licensed user, the mailbox, and the credentials you actually send from. IMAP, SMTP AUTH and an App Password all need to be enabled at the seat and permitted at the tenant, and legacy authentication is disabled by default in new tenants. A seat delivered without SMTP AUTH turned on is a seat you cannot plug into a sending platform, and that is a frequent reason a delivery stalls on day one.

License SKU sets the ceiling and most of the price

Order the cheapest SKU that supports what the seat has to do. For pure outbound, that is almost always Business Basic.

The deliverability difference between these tiers is negligible. What changes is the surface a prospect sees when they look you up, and the cost you carry every month. Paying for E3 on a cold email seat adds $15-30 per unit and buys nothing your campaign can use.

What correct DNS looks like on delivery day

You should never receive a tenant and then have to configure authentication yourself. Four records need to exist and one setting needs to be on.

• MX pointing at the Microsoft route for the domain, resolving cleanly.
• SPF as a TXT record including spf.protection.outlook.com, with a single SPF record on the domain rather than two conflicting ones.
• DKIM as both selector CNAMEs published, and signing actually enabled in the Defender portal. A published record with signing switched off is the defect we see most often in bulk stock.
• DMARC present, typically at p=none while the domain is new, moving to quarantine once you have visibility.

Unsigned DKIM is expensive and invisible. A tenant seat that authenticates on SPF alone typically gives up 20-30 points of inbox placement against a properly signed seat, and nothing in your sending platform will flag it. Send one message from a delivered seat to a mailbox you control and read the headers. If DKIM does not show a pass with the domain in the signing field, the batch is not ready.

Bulk tenant pricing across 2026

Rates below are what tenant inventory has traded at across the supplier market this year. They are not a MixAcc price list — we do not carry tenants as catalog stock — and most sellers step their own rates down at 25, 100 and 500 units. Tenant stock is slower to produce than consumer mail, so lead times of 2-5 days at the higher volumes are normal rather than a warning sign.

Two things shape those numbers. Domain age accounts for most of the gap between the first two rows, and completed warming accounts for most of the gap between rows three and four. Buying warming rather than doing it yourself saves 21-30 days of calendar time, which on a campaign with a start date is usually worth more than the cash difference. Broader pricing across every account category sits in our rate reference for PVA inventory.

How many seats one tenant should carry

Run 3 to 5 seats per tenant as the default. One seat per tenant is the safest structure and the most expensive, since the domain and provisioning cost lands on a single mailbox. Five seats spread that cost across five sending addresses while keeping the blast radius survivable.

Above 10 seats, the arithmetic turns against you. Microsoft’s enforcement applies to the organization, so a single flagged mailbox in a 20-seat tenant can take all 20 offline in one action. Operators who learned this the hard way describe losing a week of pipeline capacity from one aggressive sequence. Volume concentration compounds it: 20 seats at 300 messages daily puts 6,000 messages a day behind one domain reputation, which is a lot of signal pointed at a single record.

A practical structure for a team sending 6,000 messages a day looks like 5 tenants at 4 seats each, 20 seats total, each running 300 daily. Losing one tenant costs 20% of capacity, not all of it.

The 45-day ramp that keeps tenant seats alive

Tenant seats tolerate a faster ramp than consumer mailboxes, but not the ramp most buyers attempt. Hold this schedule and expect 90-95% of a batch to survive the first quarter.

1. Days 1-3. Sign in through the seat’s own residential proxy, send 5-10 messages daily to mailboxes you control, and reply to some of them. No campaign traffic.
2. Days 4-7. 20-40 messages daily, mixed between warmup pool and a small live segment. Watch bounce rate and stop if it clears 3%.
3. Days 8-14. 80-150 daily. This is where a badly authenticated tenant reveals itself, so run a placement test against Exchange Online receivers at day 10.
4. Days 15-30. 150-250 daily. Reply rates should be stabilizing. Any seat sitting below half the batch average is a candidate for replacement rather than repair.
5. Days 31-45. 250-400 daily on Business Basic, up to 500 on a warmed domain. Hold here rather than pushing further.

The step-by-step mechanics of warmup pools, reply ratios and seeding lists are covered in our 30-day account warming sequence, which applies cleanly to tenant seats with the volume numbers above swapped in.

An acceptance test you can run in 20 minutes

Do this on every delivery, on a sample of 5 seats or 10% of the batch, whichever is larger.

1. Sign in to the Microsoft 365 admin center with the supplied global admin credentials.
2. Open the domains panel and confirm the tenant genuinely owns the sending domain, showing as healthy rather than pending verification.
3. Check the billing page for an active subscription with a payment method attached and a renewal date at least 25 days out.
4. Confirm the license assigned to each seat matches what you ordered.
5. Connect the seat over IMAP and SMTP from your sending platform using the App Password supplied.
6. Send one message to an external mailbox you control and inspect the headers for SPF pass and DKIM pass.
7. Run a WHOIS lookup on the domain and note the registration date against what the seller claimed.
8. Query the domain against two blocklists and confirm it is clean.
9. Check whether other tenants or unrelated mailboxes share the domain, which indicates recycled inventory.
10. Log the results per seat. When more than 10% of the sample fails any step, claim the batch rather than working around it.

Defects that only appear in tenant stock

Aliases dressed as tenants. A consumer Outlook.com mailbox with a custom domain alias attached looks like a tenant seat in a delivery file and behaves like consumer mail in a filter. The admin center check in step two settles it in under a minute.

Seller-retained registrar control. You get tenant admin credentials, the seller keeps the registrar login, and your nameservers remain someone else’s to change. Negotiate registrar transfer before payment or accept that you are renting.

Lapsed billing. A tenant provisioned on a trial or a card that later declines will disable its mailboxes roughly 30 days after the failed charge, usually right as your campaign hits stride. Check the renewal date on delivery and put your own payment method on any tenant you intend to keep past 60 days.

Shared IP pools. Several tenants provisioned by the same operator, sending from the same proxy range, correlate immediately under Microsoft’s cluster filtering. One residential proxy per seat, geo-matched, with no exceptions.

Blocked legacy authentication. New tenants disable SMTP AUTH by default. Sellers who provision quickly sometimes never enable it, and the seat is unusable in every sending platform until they do.

Suppliers who fail on more than one of these are worth screening out early. The behavioral tells are listed in our guide to identifying fraudulent account sellers.

Replacement terms that fit the tenant grade

Seven days is the floor and 14 is the standard on aged inventory, because tenant defects surface under sending rather than at login. A policy worth signing covers credential failure, missing or unsigned DKIM, domain ownership that will not verify, a subscription that lapses inside the window, and geo that does not match the order. It will not cover suspension caused by your own volume, and no honest supplier offers that.

Budget for 3-8% of a tenant batch needing replacement inside the window. Push a batch hard in week one and 10-15% is a fair outcome rather than a supplier failure.

Ordering tenant inventory from MixAcc

Start with what our catalog actually holds, because the distinction matters here. Our listed Outlook stock is consumer Outlook.com inventory: New (Fresh PVA) at $1.25, Mix Old at $2.10, UK IP Old at $3 and USA Old at $3.30, on a five-account minimum. Microsoft 365 tenant seats are not a catalog line and carry no list price from us, because a tenant is not something you pull from a pool. It is a domain to register, a subscription to stand up and bill, DNS to publish and a seat to license, and every one of those is built to a spec rather than stocked.

So tenants are a quoted job. Send the spec to Telegram — seat count, domain age you want underneath them, license SKU, seats per tenant — and we come back with what we can source, what it costs and how long it takes, or tell you plainly that we cannot fill it. There are no standing volume tiers to quote against, so the number you get is the number for your batch rather than a step off a published ladder.

Where consumer Outlook.com does the job, our own stock covers it directly and replacement runs a flat 7 days on every grade. Send us your receiver mix and daily send target and we will size that half of the pool against it. Current grades and rates are on the Outlook accounts page, and teams running Microsoft alongside Google usually split their pool across both estates rather than concentrating reputation in one.

Ready to spec a tenant order? Reach us on Telegram at @nexkyc, on WhatsApp at +1 (737) 307-6751, or at allmixacc@gmail.com, and a quote with a delivery window comes back inside 24 hours.