The operating principle
Separate waste from necessary entitlement
An unused paid seat may be reclaimable. An account whose licence enables Conditional Access or retention cannot necessarily be reduced to a cheaper plan safely. Check feature dependencies and the company's contractual commitments before approving a change.
Build a usable entitlement ledger
List purchased SKUs, quantities, assigned users, renewal or commitment terms, price, unused seats and assigned add-ons. Tie identities to actual employees and business systems; a shared service account may need different handling from a departing individual.
A licence report only becomes actionable when it distinguishes dormant accounts from active integrations and explains what each licence supports.
| Review category | Question | Evidence needed |
|---|---|---|
| Unassigned seats | Is the business paying for unused capacity? | Invoice, seat count and commitment |
| Former employees | Can the seat be reclaimed safely? | Offboarding and retention approval |
| Premium security features | Which policies depend on current SKUs? | Feature/tenant entitlement mapping |
| Duplicate services | Are overlapping products genuinely redundant? | Active use, integrations and owners |
| Upcoming renewal | What changes can be made without penalty? | Contract terms and billing owner |
Never assume the lowest tier will work
Conditional Access, advanced identity governance, security and compliance features vary by plan. Microsoft publishes entitlement guidance; use the current matrix, not a generic claim that all Business licences behave alike.
A licence savings report should explain what is lost under a downgrade and who accepts that risk. Some customers will choose to retain premium controls because the value is operational resilience, not the monthly unit price.
Calculate the change using real invoices
Show a before-and-after run rate, outstanding commitments, added services, tool fees and implementation work. Avoid a percentage savings claim based only on retail list prices when the organisation may have discounts or annual commitments.
Record approved changes separately from recommendations. A software administrator can implement the decision but should not silently alter contractual subscriptions.
Documented administration controls
- SKUs, units and actual contracted unit costs
- Inactive/duplicate identities and business owners
- Conditional Access, retention and advanced-feature dependencies
- Term/renewal restrictions and commitment liabilities
- Approved change, implementation owner and post-change verification
Identify genuine waste without silently removing security features
A sensible licence review joins three sources: billed subscription quantities, assigned licences and actual user requirements. An unassigned licence is different from an underused entitlement; some users need a premium feature to satisfy security, retention or device-management policy even if they rarely open the relevant app. Ask for the purchase agreement and renewal restrictions before recommending seat removal or a lower tier.
Build a user-by-user dependency table: mailbox size, archive, desktop app requirements, shared use cases, security and compliance controls, frontline eligibility and the consequences of removing a product plan. The change owner must approve each downgrade because licences affect business capability and may interrupt data access.
| Review finding | What to establish | Why it matters |
|---|---|---|
| Unassigned paid seat | Purchase type, reassignment and term | May be reallocated but not immediately refundable |
| User appears inactive | Leave status, account purpose and retention | May hold preserved data or serve an automation |
| Tier is larger than usage | Security, archive and desktop feature dependency | Downgrade could remove required controls |
| Shared mailbox licence | Mailbox features and size requirements | Some shared mailboxes still need licences |
Model the financial effect using real invoices
Calculate baseline subscription expense, proposed assignments, one-off transition work, expected billing changes and the earliest contractual date each change takes effect. Distinguish cash savings from theoretical annualised savings. A licence removed in administration is not automatically a refund from a locked term.
Deliver a change list with expected effect and rollback considerations for the customer's approval. After the provider processes changes, reconcile the invoice and feature access rather than claiming savings from the spreadsheet alone.
Documented administration controls
- Invoice and actual term checked
- Feature and security dependencies documented
- Owner approves each SKU change
- One-off labour and contractual constraints included
- Post-change invoice and user access revalidated
The best optimisation is the one that lowers waste while preserving the features the company actually depends on.
Primary technical references
Check current feature and licence requirements before changing a tenant. A service description is not evidence that a customer has purchased or activated an option.
Commercial next step
Assess tenant licences and administration
Share approximate seat counts and subscription families, not confidential billing credentials. The review can separate possible savings from necessary controls.
Request an administration assessment