Paying for Ghosts: A Renewal-Season Audit of Cloud Seats

The renewal notice usually arrives about a month before the contract ends, carrying a number that looks much like last year's. For a great many UK teams, that resemblance is the entire problem: the seat count was set when the organisation was a different shape, and nobody has tested it since.

The renewal figure is a habit, not a decision

Cloud estates grow by accretion. A new joiner needs Microsoft 365, so a seat is bought. A campaign needs Zoom Pro, so a licence is added. Slack is upgraded for a group that later reorganises into two. Every one of those purchases made sense at the time; added together, they amount to an estimate.

The renewal then inherits the estimate, because by the time the quote lands there are a fortnight and a finance team that would rather not reopen the budget. A four-week sprint begun before the quote is requested changes the terms of that conversation. It needs no new platform, no consultancy and no data project — four exports and one properly minuted meeting will do it.

Week one: obtain the usage exports, and read them sceptically

Every mainstream suite will tell you when each account last signed in. Microsoft 365 exposes it through the admin centre and the sign-in activity reports; Google Workspace through the Admin console's user reporting; Slack through the member activity export and workspace analytics; Zoom through its active user and usage reports. Pull all four into one spreadsheet on the same day, so the comparison is fair.

Treat the numbers as evidence with known limits. A last sign-in is not a measure of value: someone may log in weekly to approve expenses in a system that authenticates through Microsoft, or never log in on desktop while relying on a mobile app. Service accounts, calendar room mailboxes, shared inboxes and guest accounts all distort the picture. Note these exceptions now, because they will otherwise be raised — correctly — at the meeting where you propose to remove something.

Week two: map seats to roles, not to people

A list of names and dates invites an argument about individuals. A list of roles invites a decision about the organisation. Build a small entitlement matrix: for each role in the business, state the tier that role actually needs.

The output is not simply fewer seats; it is fewer expensive seats. Downgrading twenty E3 licences to frontline tiers frequently recovers more than deleting five outright, and it is far easier to defend.

Week three: agree the reclamation rule with finance and IT

Reclamation fails when it is decided per case. Fix a rule in advance and let the rule do the difficult talking. A workable starting point for most teams:

• No interactive sign-in for 60 or 90 days, agreed once and applied uniformly.
• Any exception must be named, dated and reviewed at the next quarterly check.
• Reclaim means downgrade first, removal second.
• Removal always follows the archive workflow below, never a same-day switch-off.

Finance needs to know what the saving is and when it lands in the budget; IT needs to know who carries the risk if something breaks. Write both answers down before anyone sends a message to staff.

Week four: negotiate with figures in hand

With a cleaned seat count and a usage profile, approach the renewal as a buyer rather than a renewer. Ask the reseller or cloud solution provider for the quote broken down by product and tier, and compare it against a second quote — the market for Microsoft and Google licensing in the UK is competitive, and pricing varies more than most teams assume. Ask specifically about annual versus multi-year terms, co-termination dates so that contracts align, true-up timing if you expect to grow mid-term, and any auto-renewal clause that would lock the decision in again next year. Registered charities should check eligibility for donated or discounted licensing before accepting commercial pricing.

The reclaim-and-archive workflow

1. Confirm the leaver, mover or dormant account against the agreed rule.
2. Notify the line manager and, where appropriate, the individual — housekeeping, not punishment.
3. Convert the mailbox to a shared mailbox or export it to the archive, and record where it went.
4. Transfer file ownership: OneDrive or Drive contents to a manager, Slack or Teams files to a channel.
5. Reassign any groups, aliases, distribution lists or app integrations owned by the account.
6. Downgrade or remove the licence, and log the date and actor.
7. Confirm the change appears in next month's export.

The cases that stall a sprint

Shared accounts are the most common tripwire: a generic reception@ or social@ address that three people use, none of whom can be identified from a sign-in report. These should be converted to shared mailboxes or channels rather than quietly deleted. Contractors on fixed terms should have an end date recorded at the point of creation — the drift is nearly always caused by open-ended contractor accounts. Leavers on long notice or garden leave need a decision on whether the account stays live for handover, and that decision belongs to the line manager, not to IT. Parental leave, secondments and seasonal peaks all produce genuinely dormant accounts that are not vacancies, and the rule should say so explicitly.

Stopping the drift returning next quarter

One sprint is a clean-up; the process is what keeps it clean. Attach licence allocation to the existing joiner-mover-leaver checklist so a seat is never created without an owner and an end date. Give each major application a named licence owner — usually the person who would notice if it disappeared — and send them a one-page monthly report of inactive accounts. Then hold a thirty-minute quarterly review, with finance present, over the same four exports. That cadence, rather than any single saving, is what turns renewal season from an annual surprise into a routine administrative task.