Paying for Microsoft 365 but not using it? A licence review for small businesses
Bring purchased licences, actual usage and contract terms together, without losing data or overlooking essential features.
The Microsoft 365 bill arrives regularly, but the size of your team has changed. A former employee is still on the user list, a trial subscription was never ended, and nobody remembers why another account needs two additional services. This does not automatically mean that each of these licences is unnecessary. It means that the reason for the assignment is unclear.
A useful licence review therefore does not start with the cheapest plan. It connects people, tasks, technical features and contracts. Only then can you decide what must stay, what can be reassigned and where costs can actually be reduced.
Compare three lists
Start with an overview of purchased subscriptions, assigned licences and the people or functions behind them. An invoice alone does not reliably show who uses a product. The user list, in turn, does not explain every contract term and renewal date.
Identify a responsible person for each entry that needs attention. Does it relate to an active employee, a mailbox still needed for a handover or another documented purpose? Has someone joined, left or changed roles without all the necessary changes being completed?
Distinguish purchased capacity from the assignment of a licence to a user. Microsoft describes assignment as a separate administrative step. A licence that becomes available may still remain part of the subscription. Microsoft guidance on assigning licences.
Use activity data as an indicator
Usage reports in the admin centre help show which services are being used. They do not replace a conversation with the responsible person. Microsoft notes that reports cover different periods and that data is not available immediately. Overview of Microsoft 365 usage reports.
Low activity can have many explanations: holiday leave, an occasional task, a transition period or a service whose value is not reflected in the number of interactive sign-ins. Technical dependencies and security features must also be considered. An account should not be disabled simply because a table shows few events over the past few weeks.
A short checklist is enough for the first review. Flag accounts without a clear owner, unusual product combinations and unassigned licences. Review these entries with someone who understands the actual work being done in the business.
When someone leaves, clarify data and access first
When an employee has left the company, licence costs are only one part of the process. Who needs their business documents? How will unfinished work be handed over? Which access should end, and which data must be retained?
Microsoft documents that removing a licence can affect the associated services and data. First establish a suitable handover and retention process, then adjust licensing. Removing a licence is not a general method for safely archiving data. Guidance on the effects of removing a licence.
This decision belongs within a complete offboarding process. That also includes sign-ins, sessions, devices and, where applicable, additional applications. A lower bill alone does not show that offboarding is complete.
A smaller plan must still support the work
A cheaper package may be suitable if certain features are genuinely not needed. But it may also remove essential desktop applications, management capabilities or security features. Compare the actual way people work, not just the product name.
Before switching, identify the essential features. Test the change on a suitably limited scale and document the result. Savings should not come from inadvertently losing a security feature that was previously in use.
Products that appear to duplicate each other also deserve a closer look. Some combinations overlap; others deliberately extend a base plan. Without checking the included features, they cannot form a reliable list of licences to remove.
Freeing up a licence does not automatically reduce the bill
Whether and when the purchased quantity can be reduced depends on the contract and purchasing channel. Contract terms, renewals and change windows must be considered separately from user administration. If subscriptions are purchased through a partner, contract changes are coordinated with that partner. Microsoft guidance on buying and reducing licences.
Alongside the technical findings, record the next commercial step: reassign immediately, reduce at the next available opportunity or retain for a documented need. A reminder before renewal prevents an identified surplus from simply continuing.
Conclusion
A licence review succeeds when costs and usage clearly align. Sometimes it reduces spending; sometimes it simply clarifies assignments. Both are useful, provided the necessary features, data and safeguards remain in place.
Would you like a review of your Microsoft 365 licences? Talk to shinpo IT.