From the Microsoft edition of October 31, 2026
Canada spent over $440M on Microsoft licences, including M365 Copilot, in a year; Shared Services Canada says it cannot track licence usage, and departments report more than 70,000 unused licences (Oct 19)
Government of Canada (Shared Services Canada and departments) · National government (licence management; SLED transfer) · Canada
- Publisher
- Toronto Sun
- Original publication
- 2026-10-19
- Source retrieved
- 2026-11-01
- Event date
- 2026-04-27
What happened
The Toronto Sun reports that a response to an order-paper question from MP Adam Chambers shows the federal government spent more than $440M on Microsoft licences between March 2025 and March 2026. The products covered include Windows, Microsoft 365, SQL Server, GitHub, Visual Studio, Teams and M365 Copilot. Shared Services Canada spent $407.8M, including $289.1M for 648,443 Microsoft 365 licences. SSC said it 'does not have the ability to track or monitor license usage', and Public Safety Canada also said it could not track unused licences. The paper's analysis found more than 70,000 unused licences across reporting departments, while some departments said spare licences were intentional (seasonal or census staff).
Why it matters
Not SLED and not AI-specific. Included as a transferable warning: as SLED buyers layer per-user Copilot add-ons onto enterprise agreements, a central buyer that cannot see utilisation cannot manage AI licence spend.
Evidence and measured results
Newspaper analysis of an official parliamentary return. The Copilot share of spend and of unused licences is not broken out.
Limitations and uncertainty
Federal, non-US government; the figures are Canadian dollars as reported. Copilot is one of many products, with its share unknown. The unused-licence count is the newspaper's own aggregation of departmental responses. Some idle licences are deliberate.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-01; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Large public buyers cannot show whether Microsoft licences, including AI add-ons, are used.
- Stakeholders
- Central IT / shared services
- Department CIOs
- Finance and audit offices
- Legislators
- Discovery questions
- Can you report Copilot licence activity by department today?
- Who owns reclaiming idle seats?
- Which spares are intentional?
- How often is utilisation reviewed against cost?
- Value hypothesis
- Utilisation reporting and reclamation may reduce idle AI licence spend and support audit scrutiny.
- Potential engagement
- A licence-utilisation dashboard and reclamation process covering Copilot add-ons.
- Unsupported claims
- That Copilot licences specifically were wasted
- Any savings estimate for SLED buyers
- US applicability without adjustment
Pre-sales engineering
Role takeaway
- Fit
- Shared-services or central-buyer models in state government and university systems.
- Architecture and integration
- Join Microsoft 365 assignment and usage reports with cost and department data.
- Prerequisites
- Admin report access
- Department mapping of licences
- Cost data per SKU
- Constraints
- Delegated assignment
- Intentional spares
- Non-US context
- Security
- Restrict report access appropriately; usage data can reveal individual activity.
- Proof of value
- Monthly idle-seat report by department
- Pilot automated reclamation on one department
Delivery
Role takeaway
- Work
- Recurring licence utilisation review and reclamation, with tighter cycles for AI add-ons.
- Dependencies
- Department licence owners
- Finance reporting
- HR joiner/leaver data
- Ownership
- Central IT owns reporting; departments own reassignment decisions.
- Skills and adoption
- Training licence owners to read usage reports.
- Governance checkpoints
- Monthly utilisation report
- Quarterly idle-seat review
- Annual true-up with finance
- Acceptance criteria
- Proposed: idle Copilot seats reviewed every 90 days
- Proposed: documented justification for every retained spare
- Risks
- Political scrutiny of waste
- Reclaiming seats from active users by mistake
- Incomplete departmental reporting
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Licence telemetry must be collected per department when purchasing is centralised but assignment is delegated.
Governance
Who approves, reviews and stays accountable for outcomes?
Centralised purchasing combined with delegated assignment and no usage tracking leaves no one accountable for waste.
Security and privacy
What data, permissions and controls need testing?
Not addressed.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Not addressed.
Procurement
What should contracts, pricing and exit terms secure?
Buyers should require utilisation reporting as part of any Microsoft add-on purchase, especially high-cost per-user AI licences.
Operating model
Which teams own the service once it runs?
Shared-services models need a clear owner for reclaiming and reassigning licences.
Publication history
- 2026-10-31Microsoft · Issue 039 resources
Stable resource ID: canada-federal-microsoft-licences-440m-ssc-cannot-track-usage-70000-unused-20261019