INFRASTRUCTURE — CASE STUDY

One audit found the renewal that would have killed 37 inboxes

Sending estates we operate (names withheld)

131inboxes mapped across 4 tenants and 51 domains, every count verified live in its own tenant
4tenants audited live, one by one
51domains across the four tenants
131inboxes counted, 129 shared plus 2 user mailboxes
1renewal already missed when the audit read the dates
1tenant admin found with no MFA enrolled, fixed the same day
3renewal dates sitting in the following three week danger cluster

How it worked

STEP 1

A live count in every tenant, identity confirmed before counting

STEP 2

One overview sheet, a summary plus one tab per tenant

STEP 3

Auto renewal and days left formulas driven by purchase dates

STEP 4

A dated renewal checklist built straight from the audit

OUTCOME

131 inboxes mapped across 4 tenants and 51 domains, every count verified live in its own tenant

Meet the estate

Four Microsoft 365 tenants carrying the sending infrastructure behind several outreach programs: three vendor built tenants and one tenant of our own. Between them, 51 domains and 131 inboxes. Before this audit, nobody had ever counted all four in one place, on the same day, from live reads. The knowledge lived in fragments: a sheet here, a note there, and renewal dates in a screenshot.

The challenge

Tenants rarely die loudly. They die when a single cheap license lapses and takes every shared mailbox on the tenant down with it, or when an admin account with no second factor gets taken. Both failure modes are invisible until they happen, because a tenant that is working today looks identical to a tenant whose renewal failed last month. The only defence is an audit that reads the estate live and reads the dates as carefully as the counts.

The solution

Count live, tenant by tenant, identity first

Each tenant was opened and counted live, with the tenant identity confirmed on screen before any number was taken, after an early pass showed stale sessions mixing tenants up. The counts: 36 shared inboxes on the first tenant, 33 on the second, 37 on the third (36 shared plus its admin mailbox), and 25 on our own tenant (24 shared plus the admin). Totals: 51 domains, 131 inboxes, 129 of them shared mailboxes running on the single license model the teardown study on this page describes.

Read the dates like they matter

Purchase dates and cycles were pulled together from the owner notes and the tenants themselves: two tenants bought July 31 on monthly cycles, one bought August 13, our own bought September 4. There it was: the August tenant September renewal was already marked missed, and its October date had also passed by audit day. A separate platform subscription on a two month cycle had also passed its renewal date unverified. Both were flagged at the top of the findings, ahead of every count.

Fix the admin gap on the spot

One tenant admin account had no MFA enrolled at all. The forced authenticator registration was completed the same day, closing the single easiest takeover route into a tenant carrying 37 inboxes.

Turn the audit into a system

The findings became one overview sheet: a summary plus one tab per tenant with full domain lists, and live formulas that compute next renewal and days left from purchase date and cycle, so the dates stay current without anyone retyping them. A dated renewal checklist was built from the audit, leading with the danger cluster: the single license renewal on October 29 to 30, the double monthly renewal on October 31, and our own tenant renewal on November 4, where a lapse would have risked the warmup running on its 9 newest inboxes.

The results

The audit also separated noise from signal: the incomplete setup labels showing on working domains across the tenants are a portal wizard flag, not a DNS problem, and the audit recorded them as cosmetic so nobody wastes a day chasing them later.

The return: an estate that was four separate unknowns became one map with dates attached. The missed renewal and the unprotected admin were exactly the kind of findings that pay for an audit on their own, because either one, left alone, ends with a dead tenant and a cold start from zero.

FAQ

Why does one lapsed license matter so much?

These tenants run on the shared mailbox model: dozens of inboxes depend on a single paid license keeping the tenant alive. Let that one cheap license lapse and the whole tenant, every inbox on it, is at risk at once.

How were the counts verified?

Live, inside each tenant, one at a time, with the tenant identity confirmed on screen before counting. An early pass caught stale browser sessions mixing tenants, so identity first became the rule for every count after it.

What did the audit find besides counts?

A renewal already missed on one tenant, a platform subscription past its renewal date unverified, and one tenant admin with no MFA enrolled, which was fixed the same day.

How do the renewal dates stay current?

The overview sheet computes next renewal and days left automatically from each tenant purchase date and cycle length, so the danger dates surface on their own instead of relying on someone remembering them.

By the numbers

tenants audited live, one by one4
domains across the four tenants51
inboxes counted, 129 shared plus 2 user mailboxes131
renewal already missed when the audit read the dates1
tenant admin found with no MFA enrolled, fixed the same day1
renewal dates sitting in the following three week danger cluster3

Bars are scaled so very small and very large numbers fit on one chart. The values printed are exact.

THE ROI
1

missed renewal caught by the audit, on a tenant whose sending inboxes would have died with it

One audit pass produced the full estate map and flagged the missed renewal and the unprotected admin before either cost a tenant.

What was built

The concrete pieces this engagement shipped, in one list.

Your mail is being sent unauthenticated. Here is the full fix.

Lower stack cost. Back in the inbox. Built to send at any scale.

We rebuild it properly: secondary domains, inboxes, SPF, DKIM and DMARC set to enforcement, warmup and safe sending limits, blacklist monitoring on top. Send-ready in about 17 days. No campaigns, no copy, no lead lists. Infrastructure only.

Almost a decade building cold outreach infrastructure, including his own sending and verification stack built from scratch. 20+ B2B clients at companies worth $10M and above, all in tier one countries.

Free · Written plan + fixed price · No sales call required

More case studies

Lead dataA US M&A advisory firm (name withheld)
46,000

prospects matched on LinkedIn, 93% of the final list

151,218 rows in. 49,373 decision-makers out.

READ CASE STUDY →

ROIValid decision-maker leads at $0.067 each in the pilot, then all 49,373 scored for $1.54 total.

InfrastructureA US advisory firm's cold email program (name withheld)
100%

sender health at the end of the wave, with 1 hard bounce in the final campaign

30 inboxes. 1,596 sends. Zero burned.

READ CASE STUDY →

ROIZero inboxes burned: 1,596 sends delivered and the pool ended at 100% health, ready for the next wave.

OutreachPartner outreach for a US advisory firm (name withheld)
Step 2

the follow-up, not the first touch, produced the first interested partner reply

The first yes did not come from the first email

READ CASE STUDY →

ROI958 sends across the wave produced an interested partner and a $1,000 logged opportunity.

Copied
Free tools Get an inbox plan