The Seats Nobody Sits In: A Pre-Renewal Microsoft 365 Licence Tidy-Up

The renewal email arrives, the number looks bigger than you remember, and nobody is quite sure why. In plenty of UK small businesses, Microsoft 365 licensing has grown the same way the stationery cupboard did: one order at a time, usually for a good reason, with very little clearing out afterwards.

That is not a scandal. It is just admin gravity. Someone left, and their mailbox was kept. A shared mailbox was created and a licence got attached because it seemed safer. A project tool appeared inside Teams, but the old standalone app stayed on the bill. Before long you are paying for seats that nobody sits in.

A proper tidy-up does not need a consultant, a change freeze, or a dramatic all-staff email. It needs twenty focused minutes, a little restraint, and a clear rule: remove cost only after you have handled the data and the people depending on it.

Start with the list, not the panic

Open the Microsoft 365 admin centre and go to Billing, then Licences. You want the product names and how many seats are assigned versus available. Then go to Users, Active users, and use the column chooser to show sign-in activity. If the columns look unfamiliar, that is normal. Microsoft moves the furniture around regularly.

The useful question is not who has a licence. It is who needs one this month. A licence is not a badge of seniority, a filing cabinet, or a nice thing to leave switched on in case someone pops back. It is a working tool with a monthly cost.

Make a simple four-column sheet: person or account, licence type, last meaningful sign-in, and what would break if the licence changed. That last column is where the actual judgement happens.

The four buckets that usually hide the waste

Most small-business licence waste falls into a few familiar buckets. You do not need to chase every edge case on day one.

1. Leavers who still have a seat

A departed employee may need their mailbox kept for a while, especially if there is a handover, a client relationship, or a legal reason. But keeping the mailbox does not always mean keeping the full licence. The safe pattern is usually to block sign-in, convert the mailbox to shared if appropriate, remove the licence once retention requirements are met, and make sure someone else can access what they need. Check with whoever owns the staff leaver process before you touch anything.

2. Shared mailboxes with unnecessary licences

Shared mailboxes are often free, but not always. If a shared mailbox is under the standard storage limit and does not need features that require a licence, it may not need one. If it is enormous, has an archive, or is being used in a way that genuinely needs a paid plan, that is a different conversation. Do not strip a licence just because the word shared appears in the name. Check the mailbox size and what the team actually uses.

3. Duplicate tools wearing a Teams hat

Teams and SharePoint now cover a lot of ground that used to need separate products. Look for overlapping tools: a standalone file-sharing service when SharePoint is already paid for, a separate chat app alongside Teams, a survey tool when Forms does the job, or a note-taking app that duplicates OneNote. Be fair here. If the specialist tool is genuinely better for the work, keep it and say so. The point is to make a decision, not to punish convenience.

4. The just-in-case accounts

Test accounts, old project accounts, seasonal accounts, and accounts created for a supplier who never logged in. Some may need to stay for operational reasons. Many do not. If an account has not signed in for months, ask who owns it and what it feeds. If nobody can answer, that is a strong clue.

Downgrade safely, not heroically

Cost recovery has a bad reputation because people remove the wrong thing at the wrong time. Avoid that by working in a sensible order.

First, confirm the person or team no longer needs the full plan. Second, deal with mailbox data, files, and any shared calendars or forms they own. Third, check whether any apps, scripts, or sign-in flows depend on that account. Fourth, change the licence during a quiet period, not at 4:55pm on a Friday. Fifth, tell the person or their manager what has changed.

If you use group-based licensing, check the group membership first. Removing someone from the wrong group can be tidy and instant and still cause a very messy morning. If you are unsure, downgrade to a lower plan rather than removing everything at once. That keeps the account alive while you confirm what is actually needed.

Who to ask, and what to ask them

You do not need a committee. You need three or four short conversations. Ask line managers which leavers still need mailbox access. Ask finance whether any software is being bought outside the Microsoft 365 bill and duplicating it. Ask the people who run shared inboxes whether the mailbox is growing or just sitting there. Ask whoever handles starters and leavers whether the joiners and leavers checklist includes licence assignment and removal.

Keep the tone practical. This is not a hunt for wasteful colleagues. It is a check that the business is paying for the tools it actually uses.

A simple renewal checklist

• Export the current licence list and assigned seat count.
• Check sign-in activity for every licensed account.
• List leavers, shared mailboxes, test accounts, and seasonal accounts.
• Confirm mailbox retention and access needs before removing any licence.
• Look for duplicate tools that overlap with Teams, SharePoint, or Forms.
• Downgrade or reassign during a quiet period, not during a busy deadline.
• Tell managers and inbox owners what changed.
• Put a monthly or quarterly licence review on someone's calendar.
• Record the decisions so the next renewal is not a mystery.

Twenty minutes will not catch every oddity, but it will usually find the obvious waste. That is enough to make the next renewal conversation a lot less speculative. And if you only do one thing this month, make it this: find the seats nobody sits in before the invoice finds you.