Microsoft 365 license optimization for a small business: right-size the seats you already own

A recommendation, not a transaction

Two questions get confused constantly, so it is worth separating them before anything else. Which plan should we buy? is a purchase decision, and we answer it on a different page — Microsoft 365 Business Premium vs E3 compares the plans line by line, including the 300-seat ceiling that forces most upgrades. Are we using what we already bought? is this page. It assumes the plan decision is behind you and asks whether the estate you own still matches the company you have become since you bought it.

For a 20-to-500-person company, the answer is almost always no, and not because anyone was careless. Seats get bought in a hiring push and never released. Someone leaves, their account is deleted, and the subscription quietly keeps billing for the seat. A shared mailbox gets a license because that was the fastest way to make something work on a Tuesday afternoon. A department buys a tool that does one job, without anyone noticing Microsoft 365 already does that job. None of it is a mistake at the moment it happens; all of it compounds until a renewal invoice makes someone ask.

What we sell is the reading, not the buying. Nothing on this site says we are a Microsoft reseller, because we are not one: we hold no Cloud Solution Provider relationship, we do not procure, resell or discount Microsoft licenses, and we earn nothing whichever way your numbers move. The practical consequence is that the recommendation has no commercial pull in it. You take the document to your admin center or to whoever sells you your subscriptions, and the transaction stays between you and them. The commercial shape of the engagement is the ordinary one described in how our fixed-fee scoping works.

Where the money actually sits

The scope is fixed so the deliverable is comparable, and so you can tell in advance what the review will and will not surface. Eight finding types, in this order, against your own usage data. Where a category does not apply — no frontline staff, no third-party overlap — the report says so rather than quietly dropping the row.

The activity evidence comes from reporting Microsoft already gives every tenant. The Microsoft 365 apps usage report (opens in new tab) trends activity over the last 7, 30, 90 or 180 days and exposes a per-user table with the last activity date for each app and platform, exportable to CSV. Two details matter for a review like this: user-level names are hidden in usage reports by default and an admin has to unmask them deliberately, and the data lags by up to a couple of days. Neither changes a conclusion, but both change how you read a single row — which is exactly why every finding ships with its date rather than a verdict.

Deleting the leaver does not stop the bill

This is the single most expensive misunderstanding in small-business tenants, and Microsoft states it plainly in its own documentation for deleting a user from your organization (opens in new tab): after you delete the account, “you're still paying for the license” until someone separately reduces the seat count under Billing. Deletion frees the seat for reassignment; it does not shrink the subscription. A company that has offboarded thirty people over three years without ever touching the billing page is paying for thirty seats nobody can even sign into.

The order of operations also matters more than most offboarding checklists admit. You have 30 days to restore a deleted account before its data goes for good, and the default OneDrive retention for a deleted user is also 30 days, after which the OneDrive moves to the site collection recycle bin for 93 days and needs PowerShell to recover. Email forwarding and mailbox conversion have their own trap: an account you have set forwarding on cannot have its license removed without deactivating the mailbox. Getting the sequence wrong is how a cost-saving exercise turns into a data-recovery exercise.

Shared mailboxes are the reverse of that problem — a cost you can often remove outright. Microsoft's guidance on shared mailboxes in Microsoft 365 (opens in new tab) is that a shared mailbox stores up to 50 GB without any license assigned to it. A license is required only in specific cases: to raise the limit to 100 GB, to grow an in-place archive, or to place the mailbox on litigation hold, each of which needs Exchange Online Plan 2 or Plan 1 with the archiving add-on. Every licensed shared mailbox that fails none of those tests is a seat you are buying for a mailbox that would work without it.

Add-ons deserve the same test as seats, and one of them changed underneath its buyers this year: Microsoft moved the advanced Teams events capabilities out of Teams Premium on 1 April 2026, so a tenant that bought the add-on for town halls is renewing something that no longer does that job. We work that single decision through separately in is Microsoft Teams Premium worth it, because it turns on one dated licensing change rather than on usage data.

Tools you may be buying twice

The second half of the bill is usually not Microsoft's. Departments buy point tools to solve one problem, and the overlap with what the tenant already includes goes unexamined for years. What you own depends on which plan you are on, so this table is a list of things to check rather than a list of things to cancel — and the check in the right-hand column is the part that stops a saving becoming an outage.

Two of those rows have enough depth to be their own subject, and we have written them up separately rather than compressing them here. Automation licensing runs on a different axis from seats — per flow and per user, with a hard line between standard and premium connectors — and that is covered in Power Automate licensing for small business. Reporting is licensed entirely outside the Microsoft 365 plans, so a tenant full of Business Premium seats still buys Power BI separately; Power BI licensing for small business sets out where Pro and Premium Per User actually fit. If either of those is on the same renewal, read them alongside this review rather than after it.

Timing beats arithmetic

Finding an unused seat and being able to stop paying for it are different things, and a recommendation that ignores the second is just a spreadsheet. Microsoft's rules on cancelling a Microsoft business subscription (opens in new tab) put a narrow window around the decision: on a Microsoft Customer Agreement billing account you can cancel for a prorated credit or refund only within seven days of the subscription starting or renewing, and the same seven-day window applies to subscriptions bought through a partner or reseller. Outside it, the lever is turning off recurring billing, which keeps your access for the rest of the term and stops the next renewal instead.

That is why the deliverable is a dated plan rather than a list. Reductions get grouped against the renewal they belong to; anything inside a seven-day window gets flagged as urgent; and anything that needs a mailbox converted or data moved first gets sequenced behind that work. Where the estate is large enough to keep drifting, the recommendation usually ends with assigning licenses to groups instead of to people — Microsoft's group-based licensing (opens in new tab) makes joining and leaving a team the thing that moves a license, which is the only version of this that stays fixed once we are gone. It has its own rules worth knowing: nested groups are not supported, and when you move someone between licensed groups you add them to the new group before removing them from the old one, or they go briefly unlicensed.

Frontline staff are the other timing-sensitive case, because the move is a plan change rather than a cancellation. Microsoft's own framing in its frontline worker licensing guidance (opens in new tab) splits an organization into information workers, who write and edit documents on a laptop, and frontline workers, who work from a phone or tablet and mostly need chat, schedules, tasks and company information. A retail floor, a warehouse shift or a clinical support team sitting on plans designed for headquarters staff is the single largest line item most reviews find. It is also the one where a wrong move is felt immediately, so the recommendation names the trade-off per group rather than a blanket swap.

What this engagement is not

Scope, timeline, and the fee

Pricing is scoped rather than listed, because the honest drivers are headcount, the number of separate subscriptions, and how many third-party tools your teams have accumulated. Forty users on one subscription is not the same review as two hundred users across five subscriptions and a decade of departmental purchases. The table below is the whole commercial shape of the engagement.

Everything the review produces belongs to you on delivery, including the inventory a future engineer would need to repeat the exercise without us. That is deliberate: a review you have to re-buy every year is a subscription, and we are trying to cancel those, not sell one.

Who books this, and what happens next

The common fit is a 20-to-500-person company where one IT generalist owns the whole tenant, or where subscriptions were set up years ago by someone who has since left. The trigger is almost always a date: a renewal quote that came in higher than expected, a budget round, an acquisition that doubled the user list overnight, or a finance lead who has started reading the Microsoft invoice line by line for the first time.

Where it leads depends on what the numbers say. If the conclusion is that the plan itself is wrong rather than the seat count, the next question is the purchase decision, and Business Premium versus E3 is where we have argued that one out. If the review surfaces protections you already pay for and have never switched on — a common finding, since unused security capability looks identical to unused capability of any other kind — the configuration side of that is our Microsoft 365 tenant security assessment, which reads settings rather than spend and is scoped, priced and delivered separately. Where the duplicate-spend list points at device management specifically, Intune deployment services for small business is the rollout that replaces the incumbent tool properly rather than just cancelling it, and where it points at collaboration sprawl, Teams governance consulting deals with the teams, guests and channels underneath the seats.

Two adjacent bills are worth reviewing in the same sitting, because both are licensed outside your Microsoft 365 plan and both are frequently over-bought: Power BI licensing for small business covers reporting seats, and Microsoft Fabric licensing cost covers the capacity underneath them if anyone has proposed one. If your Azure subscription is on the same invoice, the same discipline applies a layer down — Azure cost optimization quick wins is the equivalent sweep for infrastructure, and Azure migration and cost optimization consulting is where that gets scoped as work. And if what you actually need is to get more out of the seats rather than fewer of them, that is the rest of this site: fixed-fee Microsoft 365 consulting for small business teams, priced per project and finished on a date.