Content reviewed: 12 October 2026

In a larger organisation, a total licence count is not enough. You need to know who makes purchasing decisions, how access is assigned, when commitments renew and how exceptions are reviewed. Licensing governance is an operating process shared by IT, security, HR, procurement and finance.

Connect three records

Core views of the licence portfolio
RecordOwner's question
Job rolesWhich apps and security capabilities does each role actually need?
AssignmentsWhich user or group receives each licence, and did assignment fail?
SubscriptionsHow many seats are committed, and when can the commitment change?

Assign by role and monitor failures

Group-based licensing links licences to defined groups, but it does not remove the need to investigate failures and exceptions. Microsoft's group licensing guidance describes prerequisites, user location, error review and moves between groups. Follow membership changes with checks of actual assignment state.

Set a decision cadence

  1. 01

    Monthly

    Review failed assignments, starters and leavers, and unusual exceptions.

  2. 02

    Before renewal

    Compare committed seats with workforce plans and approve changes before the next term.

  3. 03

    After a product change

    Update role definitions, assignment groups and internal rules.

In New Commerce, confirm whether a change is allowed immediately, at the next billing cycle or at renewal. Microsoft documents eligible term and billing changes. Record the date, decision and reason for each exception.

Give every entitlement an owner and a reason

License governance is an ongoing operating process, not a clean-up exercise just before renewal. Each service needs an IT owner, a business process owner and a documented way to request, change and remove access. A central inventory should connect purchased subscriptions, assigned users or groups, approved exceptions, commitment dates and cost centres. Without that connection, an organisation can have apparently spare seats while still buying licenses for the wrong team. The Microsoft 365 admin centre lists subscriptions and available versus assigned seats, but it does not replace local ownership and approval rules.

Control the whole employee lifecycle

At onboarding, map a role to an approved set of services and confirm the user's location. At a role change, review old entitlements so expensive add-ons do not simply accumulate. At offboarding, resolve retention and continuity of data under company policy before removing a license. Group-based assignment can automate the routine, provided each group has an owner and assignment errors are monitored. Microsoft's documentation notes that nested groups are not supported for this purpose. Moving a user between licensed groups in the wrong order can temporarily interrupt access. Pilot any bulk change with representative users and record a rollback path.

A practical control rhythm
ControlCadenceOwner
Assignment errors and new requestsOngoingIdentity administrator
Exceptions, activity and spare seatsMonthlyIT and team owners
Hiring and role changesQuarterlyHR and Finance
Offers and commitment datesBefore every renewalProcurement and IT

Use activity as a signal, not an automatic removal rule

Assigned seats and active use are different metrics. Microsoft defines activity separately for Exchange, SharePoint, Teams and other products; a quiet month does not prove that a person no longer needs access to an exceptional or security-sensitive process. Review the definitions of active users before interpreting reports. Track licenses without an owner, failed assignments, unapproved add-ons, the gap between purchased and assigned seats, and renewals completed without a confirmed forecast. Each metric should trigger an investigation with a named owner rather than an automatic downgrade.

Keep technical assignment separate from commercial commitment

Removing a license from a user does not necessarily reduce purchased capacity or the supplier commitment. New Commerce permits seat increases, while reductions have time limits that must be managed around purchase and renewal. Keep a calendar shared by IT, Finance and Procurement: expected headcount, renewal date, current seats, last day for a permitted change and the person authorised to approve it. Partner Center's seat-change rules belong beside the technical reports. Close every control cycle with approved changes, proof that they were implemented and a reconciliation of the following invoice.

Give every exception an expiry or review date. Typical examples include a contractor's temporary access, a pilot service or a license retained while data is preserved. Without a boundary, exceptions gradually become permanent cost. For each change, record the approval, technical execution and confirmation that access matches the request. This creates an auditable trail for IT, Finance and security owners, and makes the next renewal a planned decision rather than a reconstruction of old emails.

An available seat is not automatically realised savings

Our hypothetical example: an organisation buys 180 annual seats and assigns 170 after departures. Ten are available for reassignment, but the commitment has not fallen to 170. Finance should record the realised change after a permitted commercial adjustment and invoice reconciliation. Track expected renewal savings separately from realised savings.

Recheck the renewal schedule after a change

Partner Center supports end-of-term scheduled changes for active subscriptions with autorenew enabled. It also says mid-term quantity changes, SKU upgrades, trial conversions, cancellation or disabling autorenew delete saved scheduled changes. A one-off spreadsheet sent to procurement is therefore insufficient.

Our renewal control record
FieldEvidence to retain
ObjectTenant, subscription ID, product and SKU
Current stateQuantity, term, billing and renewal date
PlanTarget quantity/SKU, effective date and approval
Post-change checkActual saved schedule and verification time in Partner Center
OutcomeCompleted change and reconciled invoice

For example, renewal is scheduled to reduce 180 seats to 170. Before renewal, five seats are added. Reread the actual schedule after the quantity change; do not rely on the previously saved 170. Recreate the schedule against the current staffing forecast and record it. This is an editorial workflow example, not a guarantee that every offer permits reductions.

Technical source auditing and commercial renewal control need separate evidence. The Graph guide explains the first; term and billing changes depend on offer eligibility. Close the task after both outcomes are verified.

Frequently asked questions

Is group-based assignment a complete licence audit?

No. It shows the assignment mechanism; an audit must also assess purchased seats, business need, failures and commitments.

Who should own the licence catalogue?

Assign a clear owner across IT and procurement, with a regular approval path involving security and finance.