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
- 4 tenants audited live in one pass
- 51 domains and 131 inboxes mapped in one overview sheet
- 1 missed renewal caught and flagged as the first billing item to check
- 1 admin account with no MFA found and secured the same day
- 3 renewal dates clustered in one three week window, all on a checklist
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.
