Canada’s effort to make federal purchasing more Canadian is running into one of its toughest tests: the technology that keeps the military operating. An analysis of federal procurement disclosures found that the Department of National Defence has signed $67.7 million worth of new 2026 contracts with Microsoft, Amazon, Google and their Canadian subsidiaries, more than double the $30.3 million identified for 2025.
The numbers create an uncomfortable contrast with Ottawa’s push to strengthen domestic suppliers and reduce strategic dependence on foreign technology. Yet they do not establish that National Defence has broken the government’s Buy Canadian rules. The contracts span software, consulting and equipment services, many may fall outside the policy’s thresholds, and Canadian subsidiaries of foreign companies can qualify as Canadian suppliers. The result is a much more complicated story about procurement, military readiness and digital sovereignty.
The Numbers Behind the $67.7-Million Headline
The $67.7-million figure comes from an analysis by The Maple of contracts disclosed through the federal government’s proactive procurement database. According to that analysis, National Defence signed approximately $52.7 million in new contracts during 2026 with Microsoft and its Canadian subsidiary, another $12.4 million with Amazon and Canadian Amazon entities, and roughly $2.6 million with Google. Together, those contracts more than doubled the $30.3 million recorded with the same technology companies in 2025.
Those figures need to be understood carefully. Ottawa’s disclosure system generally publishes individual contracts worth more than $10,000, and the amounts shown are contract values rather than necessarily money already paid to a supplier. Federal guidance also cautions that published values can represent maximum potential amounts and may include options or task-authorization arrangements that are not ultimately exercised. Contract information is published quarterly and can appear four or five months after an award, meaning the publicly visible 2026 picture may still change as additional records are released.
Microsoft Accounts for Most of the Increase
Microsoft stands out sharply within the $67.7-million total. The Maple calculated that approximately $52.7 million of National Defence’s newly signed contracts with the three U.S. technology giants went to Microsoft or Microsoft Canada. That makes the company by far the largest of the three suppliers examined. Amazon-related contracts accounted for roughly $12.4 million, while Google-related contracts made up approximately $2.6 million.
Individual federal records illustrate how these relationships can be structured. One National Defence contract signed with Microsoft Canada in February 2026 had a total value of about $2.37 million and covered the rental of computer equipment associated with production and operations. The disclosure classified it as non-competitive and cited exclusive rights. Other, much smaller Microsoft contracts have similar descriptions. Amazon Web Services Canada also received multiple contracts during the year for information-technology consultants and equipment-related services, including several awards worth hundreds of thousands of dollars. The result is not one giant $67.7-million purchase, but a collection of contracts spread across different requirements and procurement vehicles.
These Contracts Cover More Than Cloud Computing
It would be inaccurate to describe the entire $67.7 million as new cloud spending. The contracts identified in the federal database cover a broader range of technology requirements, including software licensing and maintenance, information-technology consulting and rental of computer equipment. The Maple reported that it could not determine how many of the contracts were specifically connected with cloud services, and said National Defence did not provide additional clarification before publication.
That distinction matters because National Defence already operates within a large technology ecosystem that includes cloud platforms, conventional software licensing, technical support and specialized computing infrastructure. Federal records show, for example, Amazon Web Services Canada receiving contracts for both IT consultants and equipment-related services, while Microsoft records include software licensing and equipment rentals. Some contracts were recorded as sole-sourced because of exclusive rights. For a military organization managing existing systems, replacing a particular supplier can therefore mean much more than purchasing a different product. Software compatibility, security accreditation, support arrangements and existing infrastructure can all influence whether another vendor is realistically interchangeable.
Why ‘Buy Canadian’ Does Not Automatically Exclude U.S.-Owned Firms
Ottawa’s Buy Canadian framework does not simply ask whether a corporation’s ultimate parent company is Canadian. Under the federal definition, a supplier can qualify as Canadian when it has a permanent place of business in Canada, is registered and pays taxes here, maintains a Canadian address and employees or day-to-day operations, and performs sufficient value-added activity domestically. That means a Canadian subsidiary of an American multinational can potentially satisfy the government’s definition even though its parent corporation is based in the United States.
The rules also have financial and procedural boundaries. The strategic procurement policy initially applied to competitive procurements worth at least $25 million when it took effect on December 16, 2025. Ottawa lowered that threshold to $5 million on June 15, 2026. The $67.7 million reported for Microsoft, Amazon and Google is an aggregate of many contracts, so it should not be treated as though National Defence issued one procurement above the threshold. Existing standing offers and supply arrangements can also be covered only upon renewal. Consequently, the new contracts create questions about dependency and policy outcomes without automatically demonstrating non-compliance.
Ottawa’s Procurement Promise Is Colliding With Contracting Reality
The federal government introduced the core Buy Canadian measures in December 2025 as part of a broader attempt to make public purchasing support domestic companies, workers and supply chains. Canadian suppliers can receive advantages during evaluations, while bids can also receive additional consideration for Canadian content such as domestic manufacturing, research and development. By June 2026, the government had lowered the threshold for strategic procurements from $25 million to $5 million, significantly widening the policy’s reach.
At the same time, recent reporting illustrates how difficult it is to measure progress simply by looking at the address attached to a contractor. A Toronto Star analysis of federal procurement data estimated that U.S.-controlled corporations received about $7.8 billion in federal contracts during the first 16 months of Mark Carney’s government, even though most contracts in the underlying federal database were recorded as going to companies located in Canada. The gap largely reflects multinational subsidiaries. It highlights a central policy question Ottawa has yet to fully resolve: whether “Canadian” should primarily describe where economic activity occurs or who ultimately controls the company receiving the contract.
Defence Remains One of Canada’s Most Foreign-Dependent Buying Areas
National Defence is where a rapid transition away from foreign suppliers becomes particularly difficult. Public Services and Procurement Canada told a parliamentary committee that between April 2025 and February 2026 it awarded approximately $9.3 billion in contracts and amendments to suppliers located outside Canada while acting as a common service provider. Defence-related purchases represented about $8.9 billion, or 96 per cent, of that amount. Complex military equipment, software and support networks have been built through international supply chains over decades.
Ottawa itself acknowledges the problem. Canada’s Defence Industrial Strategy, released in February 2026, sets a goal of raising the share of defence acquisitions awarded to Canadian firms to 70 per cent within a decade. Its “Build–Partner–Buy” model calls for building capabilities domestically where Canada has strength, partnering with trusted allies when necessary and buying foreign equipment when domestic or partnership options are not practical. That wording is significant. The strategy is designed to reduce dependence over time rather than require National Defence to immediately stop purchasing foreign technology regardless of operational consequences.
The Cloud Question Is Really a Sovereignty Question
The debate becomes more sensitive when the technology supports military operations. Government information released in 2025 showed that federal departments and agencies had spent almost $1.3 billion since 2021 on cloud services from Microsoft, Amazon and Google. More than $1 billion of that total went to Microsoft. National Defence reported using Amazon Web Services for several “mission-critical” applications supporting areas such as Royal Canadian Air Force aircraft coordination and maintenance and Canadian Army situational-awareness tools.
Microsoft Azure was also identified as supporting the military pay platform and Army operational-planning tools, while Google Cloud provided artificial-intelligence capabilities including language processing. The concern therefore extends beyond whether procurement dollars ultimately benefit a Canadian or American shareholder. Canada has to consider what happens when essential military and government systems become dependent on infrastructure controlled by companies subject to another country’s laws. Ottawa’s own digital-sovereignty framework says storing data in Canada does not necessarily remove foreign jurisdiction when the service provider itself remains subject to foreign legal obligations.
Canada’s Cloud Market Leaves Ottawa With Few Comparable Alternatives
Reducing dependence becomes harder when the market itself is highly concentrated. A June 2026 report from the Canadian Anti-Monopoly Project estimated that Amazon Web Services, Microsoft Azure and Google collectively control approximately 85 per cent of Canada’s public-cloud market. The study estimated Amazon’s share at 42 per cent, Microsoft’s at 31 per cent and Google’s at 12 per cent. Those companies have spent years developing global networks that can rapidly provide computing capacity, storage, cybersecurity tools and sophisticated platform services.
That scale helps explain why simply directing federal buyers to choose a different company is difficult. Large government users need redundancy, security accreditation, technical support and the ability to expand capacity rapidly. The same report warned that proprietary technologies and switching costs can deepen vendor lock-in once organizations build applications around a particular provider. Ottawa can attempt to create Canadian alternatives, but domestic suppliers must ultimately deliver technology capable of meeting government requirements. Buy Canadian procurement can create demand for those businesses, yet procurement rules alone cannot instantly manufacture an alternative hyperscale cloud ecosystem.
Security and Interoperability Complicate a Fast Exit
National Defence’s reliance on the major cloud companies is not new. Its 2022–23 results report said the department had established Azure, Amazon Web Services and Google environments capable of processing workloads up to the Protected B level. At that point, more than 70 applications were operating within Azure, more than 50 within AWS and more than 10 in Google. Defence planning documents have since described an RCAF data platform hosted in an AWS environment and work designed to improve digital interoperability with the United States military.
The security case for established providers has also continued evolving. In September 2026, AWS announced that it had become the first cloud provider whose approved services could be used by all NATO member countries for workloads classified at the NATO RESTRICTED level. That does not eliminate concerns about foreign control, but it demonstrates the other side of Ottawa’s decision. National Defence is balancing economic sovereignty against cybersecurity, operational readiness, alliance interoperability and the risks created by migrating critical systems away from established platforms too quickly.
The Next Test Is Whether Ottawa Can Build Real Canadian Capacity
The most important question may therefore be what replaces the current dependence, rather than whether every American-linked contract disappears immediately. Shared Services Canada says it is developing sovereign hosting options, including a private cloud environment under Canadian jurisdiction, while working with Canadian vendors to expand domestic cloud capacity. It has also said its sovereign-cloud procurement is intended to prioritize Canadian-owned and controlled providers and reduce strategic dependence on foreign technology.
That effort is moving beyond planning. CanadaBuys currently lists a Shared Services Canada “Sovereign Cloud Invitation to Qualify” that opened in September 2026 and is scheduled to close on October 20. If Ottawa can develop credible domestic providers while demanding greater interoperability from all vendors, National Defence could gradually gain more room to shift sensitive workloads without sacrificing capability. Until then, the $67.7 million in new contracts captures the central contradiction facing Canadian procurement: the government wants greater technological sovereignty, but the systems it relies on today remain deeply intertwined with U.S. companies that are difficult to replace quickly.
