Canada’s Federal Cloud Procurement Draws Sovereignty and Lock-In Scrutiny

Ottawa’s cloud procurement framework is drawing renewed scrutiny after Kaylie Tiessen, chief economist at the Canadian Shield Institute for Public Policy, questioned the range of services available from Canadian providers. In a LinkedIn post, Tiessen said ThinkOn is the only Canadian cloud services provider on the federal government’s approved list. She argued that the procurement picture sits uneasily with increasing federal emphasis on sovereign cloud.

Tiessen said Microsoft is approved to provide about 750 service types, ServiceNow just over 600, Oracle about 110, and ThinkOn 49. She pointed to ThinkOn, Micrologic, and eStruxture as examples of Canadian providers that could play a larger role in government cloud procurement. Her argument focuses on access to public procurement alongside broader questions about where infrastructure is located and who controls it.

Shared Services Canada’s 3 February 2026 evaluation of cloud services provides independent context, although it does not verify Tiessen’s current service-count comparison. The evaluation says SSC established framework agreements with eight public cloud providers and found Microsoft Azure was the most-used provider between fiscal years 2019–2020 and 2022–2023. It records approximately $204 million in Microsoft consumption over that period, compared with about $49.5 million for Amazon Web Services and $44.4 million for Salesforce. The evaluation also found that some departments experienced vendor lock-in after investing time and resources with a provider and recommended greater attention to procurement thresholds and exit strategies.

The federal government has also begun addressing that concentration. Shared Services Canada said in 2026 that it had launched a procurement process for Sovereign Canadian Cloud capabilities that prioritises Canadian-owned and controlled cloud providers, while its parliamentary briefing materials describe reducing vendor concentration and strengthening domestic digital capacity as policy objectives. That effort does not change the composition of the existing approved-services catalogue cited by Tiessen, but it shows that the government has separately identified supplier concentration as a sovereignty concern.

The Canadian Shield Institute develops the sovereignty argument across two June 2026 publications. Back to Basics: Using Existing Powers to Assert Digital Sovereignty, published on 18 June 2026, examines competition policy, public-interest regulation, trade policy, blocking statutes, and technical protections as complementary tools for reducing lock-in and supporting Canadian firms. Its Sovereign Compute: Options for Canada’s Digital Infrastructure report argues that locating data centres in Canada is not sufficient without governance covering data use, intellectual property, standards, procurement, trade, and control of infrastructure.

Mike Gifford, Open Standards and Practices Lead at CivicActions and a Drupal core accessibility maintainer, wrote in a LinkedIn comment that he suspects the Government of Canada procures most of its digital infrastructure from US firms. He argued that purchasing through Canadian subsidiaries or resellers does not make the underlying technology Canadian. For Drupal and other open-source teams working on public services, SSC’s own findings make portability and exit planning procurement concerns rather than questions of hosting location alone.