Copilot licence audit: what to check before renewal
Prepare a Copilot renewal decision using contract terms, assigned access, team tasks and confirmed options.
Article language: English

In this article
The Copilot renewal reminder arrives on time. Knowledge of whose work benefits from a licence can be less orderly. Before accepting another term, bring together the agreement, assigned access and team tasks. Then decide what to retain, change or test. Automatic payment renewal should not renew the purchase justification on the company's behalf.
This article gives no price list. Price and the ability to change scope depend on the offer, purchase channel and commitment. We describe how to prepare a decision so a supplier conversation can concern a specific number of seats and confirmed terms, rather than a general belief that AI ought to help.
Which product and agreement are you renewing?
Record the full product name, plan, organisation account and seller. Microsoft 365 Copilot and GitHub Copilot support different tasks and have separate reporting rules. “Copilot Chat” also requires clarification of sign-in and available features. Do not combine them as one “AI” line in a purchase sheet. If evaluating GitHub Copilot for code, include AI-proposed dependencies (in Polish) in quality trials. That is a different acceptance task from checking content prepared in Microsoft 365. For this separate case, also examine what excluding a file from a coding assistant means (in Polish).
Read the agreement for the renewal date, change-notice deadline, commitment term and payment frequency. Monthly payment does not establish that seat count can be reduced monthly. Confirm this for your order and retain the seller's answer.
Attach the current renewal offer and previous bill. Separate changes in unit price from seat count, taxes, exchange rate and additional usage. Each can affect the invoice; listing them makes it easier to check.
What figures should administration collect?
Prepare counts of purchased, assigned and actively used seats. Check each definition and the reporting period. A person with a licence may not use the feature; an active person may have made only one attempt. These are signals for conversation, not a ready-made list of licences to remove.
The official Microsoft Copilot usage report describes, among other things, users enabled for the service, active users and dates of last activity. The report requires an appropriate administrative role. Record the export date and selected period.
Initially, an aggregate breakdown by team and task is sufficient for review. Grant access to individual data only to the justified extent. Decide who may analyse it and how long the export may be retained.
Does activity mean a licence pays off?
An activity metric in a specific report describes use according to that report’s definition. It does not yet prove output quality or time saved. Assess a use with several real tasks, inputs and acceptance criteria. Choose work the team performs regularly and can check.
A working example is a summary of an internal meeting. Record creation time, correction time, missing agreements and whether the reader can reach the source. Compare with the previous method. This is a proposed trial, not a promise of a particular result.
Include reviewer effort. A quickly created document requiring lengthy correction affects work differently from material ready to use. Also record when the tool cannot find suitable data or files need additional preparation.
What does non-use in a team mean?
Before cancelling, find the reason. Instructions, suitable material access or a task where the feature helps may be missing. A licence may have been assigned to an overly broad role. Alternatively, use may be seasonal and fall outside a short report period.
Talk to the process owner. Ask for two or three activities that were meant to justify the purchase. Establish whether they still occur and whether the tool meets working conditions. If a pilot is needed, finish it before the binding purchase decision deadline.
The result may be moving seats to another team, training some people, reducing scope on the next available date or retaining the present arrangement with a reason. Each decision needs an owner and review date.
How should renewal options be calculated?
Build a model from your own offer. For each option record seats, unit price, term, additional charges and currency. Keep assumptions visible. Compare the same period and tax treatment.
Three useful options are current scope, scope after approved changes and an option still requiring a trial. Label the last clearly. A planned saving is achieved only after the order changes and billing confirms it.
- Check whether the change is possible on the intended date.
- Confirm what happens to data and access after the change.
- Record the cost of preparing the team for the new way of working.
- Establish who submits the instruction and who checks the next invoice.
- Retain the calculation version approved for purchase.
How should questions for the seller be prepared?
Send one list referring to the order number and planned renewal. Request confirmation of the total amount, seats, commitment term and last day to request a change. Ask whether the proposed option requires a new agreement and affects other purchase components.
If the offer includes extra features, ask how they differ from those already paid for. Record which require administrator activation, a separate plan or usage-dependent charges. Keep unconfirmed items in the calculation so they do not disappear between meetings.

Finally, request a summary that can be attached to the purchase decision. After issuing an instruction, check its acceptance in the portal or order confirmation. Sending a change request alone does not prove renewal will occur at the new scope.
How should one licence group's card be prepared?
Divide the review by tasks that can be assessed together. Proposal teams, meeting leads and spreadsheet analysts may need different trials. Record seats, main use, observation period, process owner and the decision awaiting renewal. Separately mark people still onboarding and seasonal uses.
Include the previous term's purchase rationale. If it was not recorded, state the gap. Do not reconstruct it from a feature list. Ask users to show an authorised example task and result. Comparing such cards supports discussion of actual roles rather than drawing organisation-wide conclusions from one average.
If additional accounts or extensions are suspected, use the approach to identifying Shadow AI (in Polish). The article is written for law firms, but separating the tool name, account and use is useful elsewhere. Access and analysis scope must still fit your situation.
How do you read the report without confusing activity with work outcome?
Microsoft's documentation relates an active user to a specified action with Copilot. The metric alone does not describe the usefulness of the content. Microsoft also distinguishes usage reporting from audit logs; independently summed events from different places may produce different counts. The definitions were checked on 27 October 2026 in the report documentation linked above.
Keep the same period, product scope and group when comparing. Note organisational changes, work breaks and the access activation date. If one report covers the whole period while another includes only people currently assigned access, scope may explain the difference. Record it for investigation before using the count in a calculation.
Assess task results separately: completeness, accuracy, ability to reach the source and correction time. When data is reported as incorrectly read, the AI data-flow register (in Polish) can help establish what material the feature could access and who approved its availability.
How do you compare options without inventing savings?
In a working example the calculation has 12, 8 and 5 seats. These are fictional numbers illustrating the method, not information about a client. Enter the price from your own offer and the same commitment period for each. The eight-seat option may require moving tasks, while five may depend on a trial not yet conducted. Keep these dependencies next to the amount.
Add the work needed for change: preparing instructions, checking exports, training and process handover. If a value is unknown, mark it missing and assign an estimate owner. A blank cell should not automatically mean zero. Separately show sunk cost, future commitment and the amount changeable at renewal.
Write a conditional decision literally: choose the scope if a trial meets the agreed criterion before the purchase deadline. If the deadline comes first, another feasible option is needed. Keep this in the decision register (in Polish), with the offer and confirmation that the instruction was executed.
Before approval, ask another person to read the calculation without your commentary. They should identify the chosen seat count, confirmed amount, execution date and assumptions awaiting a trial. If they mistake a working option for an order, improve labels and statuses. Distinguishing offer data from estimates lets the team later reconstruct the basis for approval. Also record when the change should appear in billing.
What should be checked after the first bill of the new term?
Compare the approved card with the order, assignments and invoice. Check the people whose tasks were to move to other tools: do they have access, instructions and a way to hand on the result? A smaller purchase line alone does not prove work was transferred correctly.
Schedule a short post-change review suited to the process rhythm. Revisit the same tasks and record difficulties. If the team bypasses missing licences with private accounts, the plan needs correction. Renewal then closes one decision and leaves a verifiable basis for the next.
Separate a sales claim from a verified product property when comparing renewal options. AI supplier evaluation before purchase (in Polish) helps structure comparable questions and evidence. Separately confirm retention and deletion (in Polish): ending a licence, removing access and deleting information are different actions that need named owners.
Use AI work-time measurement including corrections (in Polish) in a licence decision. A faster draft may require longer review. Compare similar tasks and accepted results rather than assigning the same saving to every launch.
What decision is worth signing before renewal?
Prepare a short card: what is renewed, how many seats, for whom, at the offered amount and for what term. Attach task-based reasons, open risks and the next review date. Name the approver, person implementing the change and evidence of supplier acceptance.
If the review reveals overlapping tools, extend it to an inventory of AI services (in Polish). If the issue is material available to a model, start with knowledge architecture (in Polish). For purchases involving many accounts and processes, the Audit service can help.
For an unconfirmed use, prepare a pilot with evaluation criteria (in Polish). Collect contracts and exports using the AI audit materials list (in Polish), with dates and source owners.








