Software licence-seat reconciliation is not just counting the green ticks beside user names in an administration portal. A managed service provider supporting a small business may find that the client pays for more subscriptions than it has current employees, yet some apparently unused accounts protect shared workflows, seasonal responsibilities or retained business information. Conversely, a former employee may continue to hold a premium plan while the identity account is supposed to be disabled. A dependable review separates the technical assignment of each entitlement, the business reason for that assignment and the commercial contract that governs the purchased quantity.
The purpose of reconciliation is to give the authorised client owner a defensible decision before renewal, not to maximise the number of licences removed. This requires fresh records, a clearly defined product and tenant, a distinction between users and service identities, awareness of bundle dependencies and a procedure for verifying changes. A spreadsheet total alone cannot prove savings or security. An MSP should avoid treating an unfamiliar account as surplus or presenting a possible future price reduction as money already saved.
Identify the actual subscription and tenant
Start with the client's legal organisation, software tenant, product family and contract owner. One customer might have licences purchased directly from a vendor, through a reseller and under a separate subsidiary account. The same user may appear in several consoles with similar email identities. Confirm the exact subscription being reviewed rather than combining quantities from unrelated purchasing arrangements. Preserve the renewal date, term and billing authority as observed in the supported commercial source.
Record a snapshot date and a clear scope. A count from the first of the month cannot automatically be compared with a staffing report from a later date as though no starters or leavers occurred between them. A reliable report explains precisely which tenant and licence plans it includes and which are outside the current review.
Separate purchased capacity, assignments and charges
Purchased seats describe a contractual quantity, assigned seats show technical allocation and actual charges reflect the provider's billing rules. Those numbers can differ without an error. A plan might permit an unassigned purchased seat, and reducing assignments may not immediately alter what the client owes. For some plans, a notice period or commitment can constrain a mid-term reduction. Confirm the actual supplier terms and current billing records before forecasting savings.
Use a three-part ledger with purchased, assigned and unresolved quantities. Avoid labelling the difference as wasted expenditure until the client has confirmed need and commercial reduction is genuinely possible. Similarly, a technical assignment error may exist even when there is no overcharge.
Map named users to authorised business roles
Match the current assignment list against the client's approved staff and contractor records, role changes and relevant service functions. An unfamiliar account might belong to an authorised contractor, a shared mailbox or an application integration. Ask the appropriate client owner to confirm uncertain identities instead of stripping access based on naming patterns. A role description should explain why a particular software capability is needed, not merely repeat the licence label.
Protect confidential staff details during the review. Use authorised personnel information and appropriate access to account records. The MSP does not need a copy of every HR record to ask whether a business user still requires the plan; a verified status and business owner may suffice.
Investigate leavers and dormant accounts responsibly
Departures create a common mismatch between current staffing and software entitlements. However, licence release and account security are separate operations. A former employee's identity may need to be disabled, sessions revoked or data retained under an authorised leaver process. Removing a paid plan without considering mailbox, file or application retention can impair lawful access to business records. Do not use a licence clean-up ticket as blanket permission to delete user accounts or data.
Low sign-in activity can be useful evidence but not a definitive redundancy signal. Some employees use specialist software quarterly or for end-of-year work. Confirm legitimate usage patterns with the responsible department rather than establishing arbitrary inactivity thresholds for every client.
Review product bundles and add-on dependencies
Modern SaaS licences can contain multiple service plans, security features or add-ons with prerequisites. A user may need a specific base plan for an additional entitlement to function. Reassigning one visible item might break access in another application. Check the vendor's documented dependencies and the client's existing plan design before suggesting a downgrade. Record uncertain products separately for specialist review.
Where a provider offers device-based, shared or concurrent licensing, the counting model may differ from the normal named-user pattern. Do not impose a simple one-seat-per-person calculation on every product. For Microsoft-based environments, use the current Microsoft 365 licence assignment guidance and current product terms as vendor-specific context, not a universal commercial rule.
Check administrative, service and automation identities
Some business processes depend on non-human identities or shared resources. Determine whether the vendor actually permits the account arrangement and whether the assigned licence is required. A service identity must not be treated as a spare human seat by assumption. If it is no longer justified, identify the technical owner and effects before changing anything. Licence reconciliation is a useful trigger for an identity review, but it does not substitute for one.
Keep privilege and security questions visible. A highly privileged dormant account may warrant urgent access investigation regardless of what the licence costs. Conversely, an unassigned licence does not imply a security risk merely because the quantity exists.
Prepare an exception list with evidence and owners
Classify each discrepancy as confirmed necessary, confirmed candidate for release, uncertain business need, dependency requiring technical assessment or commercial term requiring supplier clarification. Link the specific user or plan using controlled identifiers. Show the source of the observation and the person who can decide. This list is more useful than telling the customer there are twenty inactive seats without identifying which actions would be safe.
Include whether the issue is time-sensitive because of an approaching renewal. A client may need to approve a decision before a provider cut-off, but the MSP should not invent a guaranteed change window or price saving. If a supplier response is pending, make that dependence explicit.
Obtain a client-authorised commercial decision
Present the actual subscription evidence and a proposed action for each confirmed case. The client may decide to retain spare capacity for planned starters, remove a redundant add-on, reassign a seat or change contract quantity at the next permitted renewal. That is a business decision. Technical access to a licence portal does not grant the MSP authority to alter a contractual purchase or a user's employment status.
Record the approved quantities, identity changes if separately authorised, timing and the person accountable for follow-up. Do not interpret a lack of response as approval to remove access. A clear decision trail protects the client from surprising service interruption and protects the provider from disputed savings claims.
Implement changes using supported administration
Release, reassign or change licences through the actual supported vendor process. Verify the target identity, plan and tenant before submission. For bulk updates, use a suitably reviewed selection and confirm what the platform will change; a broad licence removal may also disable dependent capabilities. Keep sensitive credentials out of general tickets. If a request returns an error or timeout, inspect current assignments before repeating the operation.
Do not claim completion from a saved spreadsheet or a clicked admin button. The authoritative administration platform must confirm the actual assignment state. Where a change affects a person's working tools, coordinate with the support owner before disrupting business activity.
Verify user function and commercial outcomes independently
After reassignment, check that the intended recipient can use the relevant service and that removed seats no longer appear assigned. Review the next appropriate billing or renewal record if the change was supposed to affect charges. An assignment count declining immediately is not proof that the next invoice will be lower. Record provider-specific limitations and any expected processing delay.
If an authorised user loses required functionality, treat it as an operational exception with a named recovery path. Do not quietly re-add a licence and ignore why the original decision failed; the affected approval and plan dependency may need correction.
Maintain the record through starter and leaver changes
Use actual starter, mover, leaver and subscription-renewal events to trigger smaller checks during the year. A new staff member may need a seat before arrival, while an approved offboarding must deal with access and data separately. The aim is to reduce uncertainty between reviews, not to subject every routine ticket to an oversized financial audit.
Keep one current source of truth for each entitlement and its commercial owner. Remove outdated spreadsheet assumptions and document when a product's licensing model changed. Repeated discrepancies may signal a broken onboarding handover rather than staff negligence.
Report conclusions without inventing savings
The useful client report identifies confirmed allocations, legitimate pending decisions, changes actually implemented, contractual quantity and verified billing effect where available. Distinguish an estimated opportunity from a realised saving. No generic formula can establish that every surplus assignment is recoverable cost because subscriptions and renewal terms vary.
A successful reconciliation allows the customer to explain why seats are assigned and who authorised any reduction. It also allows the MSP to support affected users without treating financial optimisation as permission to remove access. For further vendor-specific details see Microsoft Learn licence assignments and Microsoft Learn subscriptions and licences. Check current contract terms rather than relying solely on these product guides.
Remove an assigned software licence or reduce purchased subscription seats?
These are separate operational and commercial actions. In Microsoft 365, licence assignment gives an eligible identity access to product capabilities; the number of purchased seats and contractual billing commitment is managed through the applicable subscription. A removed user assignment does not by itself prove the organisation's bill will decrease. Actual rights, notice conditions and renewal windows depend on the customer's agreement and purchasing channel.
| Decision | Change a user's assigned licence | Change purchased subscription quantity |
|---|---|---|
| What changes? | The user's access to capabilities tied to that licence or bundle. | The subscription's commercially purchased seat quantity if the contract permits. |
| Authorisation | Client access owner approves legitimate user need, dependencies and retention. | Client commercial owner approves price, term, renewal and supplier conditions. |
| Main risk | Loss of required apps, mail or dependent services, including historic data considerations. | Unintended renewal commitment or insufficient capacity for active and planned users. |
| Evidence | Exact tenant, current user, plan, new assignment and effective entitlement state. | Current provider order, purchased quantity, effective date and billing record. |
| Completion | Authorised access remains functional and removed assignment no longer appears. | Supplier confirms accepted quantity change and the relevant invoice or renewal reflects it. |
Practical decision: Reconcile purchased, assigned, required and unresolved quantities for the same tenant and date. Do not remove a leaver's licence without checking approved data retention and access controls; an account's security state is distinct from seat reclamation. If the business approves fewer purchased licences, verify the actual supplier adjustment and later commercial effect. Report 'potential reduction' until billing evidence establishes realised savings. Do not interpret an unassigned seat as an automatically refundable charge.
Source A — technical entitlements: Microsoft Learn, Assign licences to users documents Microsoft 365 user assignment and prerequisites. Source B — subscription and commercial boundaries: Microsoft Learn, Subscriptions and licences distinguishes subscription purchases and available licence counts. Both are Microsoft-specific primary sources, not evidence of the customer's current commercial contract or a guaranteed cost saving. The table is an original qualitative operational comparison.
Relevant visual: the existing ARTICLE1 Web API diagram, I.hate.spam.mail.here, Wikimedia Commons, CC0 1.0, illustrates the link between account systems, not actual Microsoft billing or entitlement state. The image remains unchanged.
Frequently asked questions
Does an unused licence always mean the business is wasting money?
No. Purchased spare capacity, contract terms and planned staffing may justify it. Confirm actual need and billing before suggesting savings.
Can a technician remove a leaver's licence without reviewing the account?
Use the authorised leaver and data-retention procedures first. Licence removal and identity security are related but separate changes.
Does low application use prove a seat is redundant?
No. Some business roles are intermittent; ask the authorised service owner before acting.
Does removing an assignment immediately lower the bill?
Not necessarily. Purchased quantities and vendor renewal or commitment rules govern charges.
When does the reconciliation close?
When assignments and unresolved needs are documented, approved changes are verified and commercial outcomes or dependencies have accountable owners.