Nuage Solutions All articles
Microsoft 365

Seven Silent Leaks in a UK Microsoft 365 Estate — and the Monthly Routine That Plugs Them

Nuage Solutions
Seven Silent Leaks in a UK Microsoft 365 Estate — and the Monthly Routine That Plugs Them

Photo: Sémhur (talk), CC BY-SA 4.0, via Wikimedia Commons

Microsoft 365 rarely produces a single dramatic overspend. It produces a series of small, plausible charges that accumulate because no one owns the whole picture. A licence is added for a project; a shared mailbox is retained after a team disbanded; a backup tool duplicates native retention; storage grows because no one set a deletion rule. By the time finance sees the invoice, the estate has become a collection of historical decisions rather than a managed service.

The answer is not a one-off cost-cutting exercise. It is a monthly control routine shared by finance, IT and service owners. The seven leaks below are common in UK tenants, and each can be tested without a major programme.

1. Licence sprawl between E3, E5 and add-ons

Many UK organisations have a mixed base of Microsoft 365 E3, E5, Business Premium and individual add-ons. The pattern is often inherited rather than designed. E5 may be justified for advanced security, compliance or voice, but it is frequently assigned to users who need only a fraction of the suite. The leak is not the existence of E5; it is the absence of a role-based licence model.

A monthly review should compare assigned licences with actual feature usage. Look for users on E5 who have no active use of the advanced workloads that justify it, and for add-ons that duplicate capabilities already included in another SKU. Finance should receive a simple exception report rather than a full licence dump.

2. Inactive and departed-user accounts

Leavers are usually disabled, but their licences and mailboxes can linger. Contractors and seasonal staff create a similar problem. The cost is both direct, in unused licences, and indirect, in storage and identity sprawl. A monthly check should reconcile the HR or contractor list against active accounts, confirm that leavers have been processed within the agreed service level, and review accounts with no sign-in activity over a defined period.

Be careful not to treat inactivity as proof of waste. A shared service account or a seasonal worker may be legitimately quiet. The control is an owner-led exception process, not automatic deletion.

3. Duplicate backup and retention tooling

Microsoft 365 includes retention and recovery capabilities, but many UK tenants also run third-party backup for Exchange Online, SharePoint, OneDrive and Teams. That can be entirely sensible, particularly where the organisation needs independent recovery or long-term retention. The leak appears when multiple tools overlap without a clear recovery objective.

Ask three questions each month: what recovery scenario does this tool cover, what does native retention already provide, and who tests the restore? If two products protect the same workload for the same scenario, consolidate or document why both are required. If no one has tested a restore in the last quarter, the tool is a cost without confirmed value.

4. Oversized SharePoint and OneDrive storage

Storage growth is often treated as inevitable. In practice, it is driven by large files, duplicated content, abandoned sites and retention settings that keep everything forever. A monthly review should identify the largest sites, the fastest-growing libraries and sites with no active owner. It should also check whether version history and retention policies match the organisation's information management policy.

This is not an argument for aggressive deletion. UK organisations have legal and regulatory retention obligations, and finance should not set retention policy. The aim is to separate deliberate retention from accidental accumulation.

5. Unused calling plans and Teams Phone numbers

Teams Phone can simplify communications, but numbers, calling plans and conference bridges are easy to leave active after a pilot or office move. A monthly review should list active numbers, assigned users, call volumes and associated plans. Numbers attached to vacant roles, old meeting rooms or retired projects should be reassigned or removed under a controlled process. The same discipline applies to audio conferencing add-ons that have been superseded by meeting policies.

6. Azure consumption attached to Microsoft 365 workloads

Microsoft 365 estates often depend on Azure services for backup, archiving, logging, reporting or integration. These charges can grow without appearing in the Microsoft 365 licence review. Finance and IT should review Azure resource groups linked to productivity workloads, looking for oversized virtual machines, unattached storage, long log retention and non-production resources left running.

The control is a monthly exception report by resource owner, not a blanket shutdown. Some logging and backup services are essential; the question is whether their size and retention period still match the risk.

7. Underused Power Platform and security add-ons

Power BI Pro, Power Automate premium connectors, Defender add-ons and other security products are often purchased for a specific initiative and then left assigned. A monthly review should check active usage, owner, business case and renewal date. Where adoption has stalled, the choice is to drive adoption or reduce the footprint, not to keep paying by inertia.

A repeatable monthly routine

A workable routine has five steps. First, finance provides the invoice and licence baseline. Second, IT produces an exception report covering inactive accounts, unassigned licences, duplicate tools and storage growth. Third, service owners confirm which exceptions are legitimate. Fourth, a joint meeting agrees actions with dates and owners. Fifth, the actions are recorded in a simple register and reviewed the following month.

The routine should take hours, not weeks. It should also feed an annual deeper review of licence SKUs, retention policy and backup strategy. The objective is not to shrink Microsoft 365 for its own sake. It is to ensure that every recurring charge has an owner, a purpose and a review date. In a typical UK estate, that discipline alone will close more leaks than a single aggressive cost-cutting exercise.

All Articles

Related Articles

Repatriation Without the Slogan: A 2026 Workload Placement Framework for UK Organisations

Repatriation Without the Slogan: A 2026 Workload Placement Framework for UK Organisations