Are we paying for Microsoft 365 licences we do not need?

What does an unnecessary Microsoft 365 licence actually mean?

There are several different problems hidden behind the phrase “unused licence”. A paid seat may be unassigned. A licence may remain assigned to someone who has left. An employee may hold an add-on that no longer supports their work. A department may buy a capability already covered by another subscription. Each situation needs a different response, and none can be understood reliably from the invoice total alone.

Start by defining the outcome: pay for the capabilities the organisation needs, with clear ownership and a workable process for change. The objective is not simply to make the number of assigned licences smaller. A reduction that interrupts email, removes a necessary security entitlement or loses access to business information can cost more than it saves. A useful audit combines commercial evidence with operational judgement and produces a controlled action plan.

Which records do we need before starting the audit?

Collect current invoices, subscription quantities, user assignments and renewal terms. Add a role-based staff list showing starters, leavers, contractors and known temporary requirements. Include add-ons bought outside the main purchasing route, such as a departmental pilot. Keep access proportionate to the review: finance and an authorised administrator can assemble much of the evidence without distributing personal employee information widely.

Reconcile records by product and subscription, not just by a shortened plan label. Similar names can conceal different variants, terms or bundled services. If two invoices cover the same product, establish whether they represent legitimate separate subscriptions or accidental duplication. Record uncertainty rather than forcing an unexplained difference into a savings total. The evidence should be good enough for another colleague to reproduce the finding.

How do purchased seats differ from assigned seats?

Purchased quantity is the number of entitlements your contract makes available. Assigned quantity is the number currently allocated to users or groups. The difference can reveal spare capacity, but it does not establish whether those seats are unnecessary or when you can stop paying for them. A reserved allocation may support confirmed starters or an approved project beginning shortly.

Review spare seats with the hiring and project plan. Set a date for each intentional reserve rather than leaving it open-ended. If the seats are unnecessary, check the permitted quantity-reduction window and record the action for that date. Unassigning a licence can make it available to someone else without changing the purchased quantity. Distinguish an immediate reassignment benefit from a future invoice reduction so that savings reports remain credible.

How should we interpret low usage or no recent sign-in?

Usage evidence is a starting point for a conversation. A person may be on leave, work seasonally, use a service infrequently or need an entitlement for a centrally applied control. Some workload activity may not appear in the first report you examine. Choose an observation period that reflects the role, and understand the limitations of the evidence before drawing a conclusion.

Ask the manager and employee what work the entitlement supports, using a neutral question rather than assuming inactivity means waste. If the requirement remains valid, document it. If adoption is the problem, decide whether targeted training or a simpler process would help. If the entitlement genuinely has no purpose, plan its removal under the relevant terms. This approach is more reliable than automatically deleting assignments below an arbitrary activity threshold.

How do we find overlapping subscriptions and add-ons?

Build a capability map showing what each product is intended to provide. Compare it with the current base plan and any third-party service used for the same purpose. An overlap may be justified by specialist requirements, an agreed transition or a particular feature gap. The audit should ask why both products exist and whether that reason still applies, rather than treating all overlap as an error.

Look for products retained after a plan upgrade, trials that became paid subscriptions and small purchases made by individual teams. Confirm the purchase route and owner before proposing a change. A feature can be included but not configured, so removing the old service may require implementation work first. Count a saving only when the replacement works, required data is preserved and the commercial commitment can actually be reduced.

What needs checking before changing a leaver’s licence?

Follow an approved offboarding process covering account access, mailbox and file ownership, delegated access, retention and relevant business records. Preserve the information the organisation needs through a suitable supported approach before changing entitlements. A licence audit should not become an informal data-deletion exercise. Ask the authorised administrator and information owner to agree the sequence and record completion.

Check whether the account owns flows, integrations, shared resources or scheduled tasks. A former employee’s identity may have become an undocumented dependency for a business process. Resolve that dependency with a supported ownership or authentication design before removing the entitlement. NetMonkeys’ Microsoft 365 support services provide a relevant route to discussing the technical review alongside the commercial audit.

Can shared mailboxes replace paid user accounts?

Sometimes an account’s purpose is better served by a shared mailbox, but eligibility and licensing depend on the actual requirements. Storage, archives, retention, access patterns and other features can affect the position. Check current Microsoft guidance for the specific mailbox rather than assuming every generic address can operate without a licence. The people accessing it may also need appropriate entitlements.

Review the business process as well as the mailbox type. A shared mailbox should have an owner, approved members and a clear way to handle customer correspondence. It should not become a shared sign-in used by several employees to avoid named-user licensing. If a conversion is appropriate, test access and mail flow, preserve required information and document the arrangement. The licence decision follows that design, rather than driving an unsupported workaround.

How should service accounts and automated processes be treated?

An unfamiliar account deserves investigation, not immediate removal. Find the application, flow or integration using it and identify an accountable owner. Review how it authenticates, what information it accesses and which capabilities it requires. A licence audit may reveal that the underlying design needs improvement, especially where a personal account supports a process that colleagues depend on.

Separate the investigation from the change. Record the risk, choose an appropriate supported identity arrangement and test it before retiring the old dependency. Do not assume that disabling sign-in or removing a licence will have a visible effect immediately. Some failures appear only when a scheduled job runs later. Include those schedules in the test plan and monitor the affected process for a suitable period after the change.

Why do contract terms matter as much as usage?

Your ability to reduce purchased quantities depends on the subscription agreement and adjustment window. Monthly billing does not automatically mean a monthly commitment. If the business has an annual commitment, an unused seat may need to be reassigned or held until the next permitted change. Keep a distinction between an identified optimisation opportunity and a confirmed reduction in future spend.

For each subscription, record the supplier, renewal date, commitment, payment frequency and process for requesting a quantity change. Give the action to a named person and set a reminder early enough to review the evidence. Microsoft’s licence management guidance notes that cancellation opportunities can be limited for some subscriptions. Confirm the exact contractual position with your supplier before promising a financial outcome.

How can we calculate savings without overstating them?

Use the quantity that can genuinely be removed, the contracted rate and the period during which the reduction will apply. Show one-off costs needed to make the change, such as moving an integration or implementing an included capability. If the benefit is avoiding an additional purchase by reusing a spare entitlement, report it as avoided expenditure rather than a reduction in the current invoice.

An illustrative example is five unnecessary seats at a hypothetical £12 per seat per month. If they can be removed for a full year, the gross reduction would be £720 excluding VAT. If the permitted reduction takes effect halfway through the year, the same year’s gross benefit would be £360. These are arithmetic examples, not market prices or a NetMonkeys quotation. The timing matters as much as the seat count.

Which findings should be addressed first?

Prioritise clear, low-disruption opportunities with good evidence, while separately investigating complex dependencies. An unassigned seat with no planned use may be straightforward at renewal. A licence supporting an undocumented finance workflow needs careful work before any change. Keep commercial, operational and information risks visible so that the audit does not reward the fastest deletion over the most sensible decision.

Use a change log containing the proposed action, evidence, approver, execution date and validation result. Where a decision is deferred, record why and when it will be revisited. A finding should not disappear merely because it is inconvenient to resolve. The log allows progress to be measured without compressing every issue into a single savings number or losing track of work waiting for a renewal date.

How do we change role profiles safely?

Choose a representative employee or small group and test the proposed entitlement against their actual tasks. Include desktop apps, mobile access, collaboration and any security or compliance functions the design depends on. Explain the change and provide a support route. A controlled pilot makes it easier to distinguish a genuine licence gap from a configuration problem or an unfamiliar workflow.

After the pilot, confirm that the required services remain available and no unintended entitlement has been removed. Monitor the relevant processes over their normal cycle, which may include month-end or a scheduled approval. Do not assume a successful sign-in proves everything works. Update the role profile and onboarding instructions only after the evidence supports the change, then expand in a way the support team can manage.

What should happen when low adoption is the main issue?

Ask whether the purchase was meant to solve a specific problem and whether that problem still matters. A tool can be available without employees understanding when to use it. A short task-based session may improve adoption more than a broad product demonstration. Conversely, if the original need has disappeared, further training may simply postpone a sensible reduction at renewal.

Set a short review period with a named owner, a practical use case and a measurable outcome. Measure completion time, quality or reduced handoffs, rather than licence activation alone. At the end, decide whether to keep, reduce or stop the allocation. For a Copilot or specialist analytics pilot, the decision should reflect useful work and the time spent reviewing outputs. An indefinitely extended pilot is difficult to evaluate and easy to forget commercially.

How often should we reconcile the licence estate?

Use a regular operational reconciliation alongside a deeper review before renewal. Staff movements and approved projects should feed the routine process, so that the annual audit does not start from a year of unexplained changes. The appropriate frequency depends on how quickly the workforce and subscriptions change, but each review should have an owner and a clear set of evidence.

Reconcile invoices with purchased quantities, then compare assignments with role profiles and staff records. Check newly introduced add-ons and unresolved exceptions. Keep the output concise enough to act on: confirmed changes, investigations and renewal actions. Where a managed provider performs the review, agree what the business must supply and who approves changes. Shared responsibility works better when both sides can see the same decision record.

What should a completed audit deliver?

A completed audit should explain what you buy, who receives it and why it remains necessary. It should identify reductions that can take effect now or at renewal, with realistic timing and any implementation cost. It should also identify under-covered requirements, because avoiding waste and maintaining an appropriate environment are connected goals. A lower invoice is not evidence of a better design if essential work is left unsupported.

Ask NetMonkeys about a Microsoft 365 licence and support review if you need help turning the evidence into a practical plan. Bring invoices, renewal dates and an anonymised role summary. The useful next step is a scoped review with clear responsibilities, rather than an unqualified promise of savings based only on employee headcount.

How should we turn audit findings into a renewal decision?

Build a renewal worksheet that separates the current purchased quantity, the current assigned quantity and the quantity proposed for the next permitted adjustment date. For each proposed reduction, attach a reason and an owner’s approval. An unassigned seat may be unnecessary, reserved for a confirmed starter or awaiting assignment after a migration. These situations should not all receive the same commercial decision.

Consider a department with several unused subscriptions but a recruitment plan for the next quarter. Finance and the department owner should agree a justified reserve rather than automatically retaining every spare seat or reducing the quantity to exactly today’s headcount. Record when the reserve will be reviewed. If plans change, update the forecast while the relevant purchasing window is still open, rather than discovering the issue after renewal.

Check dependent capabilities before approving a downgrade. A user may rarely open a particular application while still needing an identity, security or device-management entitlement included in the current plan. Ask the administrator to explain the proposed replacement and test the affected workflow. The audit should identify a supportable change, not just a cheaper product name.

After the agreed adjustment takes effect, compare the actual invoice with the worksheet. Confirm that the quantity, rate and effective date match the authorised change, and record any difference with the supplier. Report realised savings separately from future opportunities and avoided purchases. This final reconciliation establishes whether the commercial result happened, and gives the next review a reliable starting point.