Skip to main content
News Analysis

U.S. Big Tech Holds 85% of Canada's Cloud Market: A Practical Guide for Business Owners, IT Buyers and Tech Workers

A new Canadian Anti-Monopoly Project report says Amazon, Microsoft and Google control 85% of Canada's public cloud market — well above the 66% global average. Here is what Canadian businesses, public-sector IT buyers and tech workers should do about it in the next 12 months.

By Refdesk Team

U.S. Big Tech Holds 85% of Canada's Cloud Market: A Practical Guide for Business Owners, IT Buyers and Tech Workers

What This Means for You

If you run a Canadian business, manage technology procurement for a public-sector organization, or work in software in this country, you almost certainly have one or more contracts with Amazon Web Services (AWS), Microsoft Azure, or Google Cloud — and the costs and risks of those contracts are about to become a political and regulatory issue, not just a budget line. A report released June 2, 2026 by the Canadian Anti-Monopoly Project (CAMP) says the three U.S. hyperscalers now hold 85% of Canada's public cloud market — Amazon at 42%, Microsoft at 31% and Google at 12% — versus a 66% global average, and recommends that Ottawa use procurement rules, interoperability standards and competition law to address what it calls a "broken" market.

Based on our analysis of the CAMP report, the federal government's parallel sovereign AI infrastructure announcements, and the procurement signals coming out of the Treasury Board, here is a practical action plan organized by who you are and what decisions are in front of you in the next 12 months.

If You Are a Small or Mid-Sized Business Owner Using Cloud Services:

Run a cost and concentration audit this month:

  • Pull your last 12 months of cloud invoices and break them down by service category (compute, storage, egress/bandwidth, database, AI/ML, support). For most SMBs, three line items quietly dominate the bill: compute (EC2/Azure VMs), data egress (often 8–12¢ per GB after the free tier), and managed databases. If any one of those is more than 30% of your bill, you have an optimization target.
  • Calculate your "switching cost." This is the often-hidden number that lock-in is built on. A useful rule of thumb: if you moved off your current provider tomorrow, you would pay roughly (a) two to four months of engineering time to refactor any provider-specific services, plus (b) data egress fees to move your storage out (a 50 TB dataset on AWS S3 costs roughly US$4,500 to fully egress, plus retrieval fees), plus (c) parallel-run costs while you cut over. For most Canadian SMBs that number lands between $20,000 and $200,000.
  • Identify your provider-specific dependencies. Specifically: AWS Lambda, DynamoDB and Cognito; Azure Functions, Cosmos DB and Entra ID; Google BigQuery, Firestore and Identity Platform. These services are the stickiest part of any hyperscaler stack because they have no like-for-like equivalent at another provider — moving means rewriting code, not just changing a config flag.

Immediate actions to reduce risk and cost:

  • Negotiate egress credits at renewal. As of January 2024, AWS, Microsoft and Google all eliminated egress fees for customers leaving the platform entirely — meaning you can move your data out free of charge, but only on the way out the door. Many account managers will offer egress credits to retain you; ask.
  • Move cold storage off the hyperscaler. Backblaze B2, Wasabi and Canadian providers like OVHcloud's Beauharnois region offer object storage at one-quarter to one-third of S3/Azure Blob list price, with no egress fees inside their networks. For backup, archive and compliance retention, this is the single fastest 60–80% cost reduction available.
  • Buy compute on a one- or three-year commitment, not on demand. AWS Savings Plans and Azure Reserved Instances cut steady-state compute costs by 40–70%. The trade-off is contractual lock-in, so size your commitment to your baseline (always-on) usage, not your peaks.
  • Reserve a "movable" 20% of your workload on portable infrastructure: containers running on Kubernetes, infrastructure managed by Terraform, applications using PostgreSQL or MySQL instead of provider-specific databases. This is your insurance policy against price shocks, outages, and the regulatory changes the CAMP report is calling for.

For data residency and sovereignty:

  • Pin your data location in writing. Every hyperscaler offers Canadian regions (AWS Calgary ca-west-1 and Central ca-central-1, Azure Canada Central and East, Google Cloud northamerica-northeast1 Montréal and northamerica-northeast2 Toronto). Make sure your storage, databases and backups are all explicitly pinned to those regions, not the U.S. defaults that some SDKs still pick up.
  • Understand that physical location ≠ legal residency. Under the U.S. CLOUD Act, U.S.-headquartered providers can be compelled to hand over data stored in their Canadian regions to U.S. law enforcement. If you handle data subject to PIPEDA, the Personal Health Information Protection Act (Ontario), or provincial public-sector privacy laws, you may need contractual data-sovereignty assurances, a sovereign cloud provider, or on-premises infrastructure for sensitive workloads.

If You Are a Public-Sector IT Buyer (Federal, Provincial, Municipal, Health, Education):

The procurement landscape is shifting fast:

  • The federal Enabling Large-Scale Sovereign AI Data Centres initiative announced May 11, 2026 with TELUS will deliver three B.C. AI data centres totalling more than 150 MW by 2032, backed by 98% renewable energy. The first Kamloops facility comes online later this year. If you are issuing AI infrastructure RFPs in 2026 and 2027, expect Ottawa to push hard for sovereign-cloud options and Canadian-controlled providers to appear on the GC Cloud Brokering Service.
  • Build interoperability into every contract you issue. The CAMP report's central recommendation is that procurement rules should require interoperable or substitutable technologies in contracts to lower switching costs. You can do that today, on your own: require open standards (S3 API, PostgreSQL, OCI containers, OpenTelemetry), require an exit plan as a contractual deliverable, and cap proprietary-service use to a defined percentage of the workload.
  • Stress-test the data-handling clauses in any U.S.-vendor contract. Procurement experts advise that, at minimum, your contract should specify (a) data residency in a named Canadian region, (b) a contractual right to be notified of any foreign government data request, (c) audit rights, and (d) defined exit terms including the format and timeline of data return.

Practical scenario: A 200-bed Ontario hospital migrating its imaging archive should be looking at total cost of ownership, not just monthly storage cost. A 200 TB imaging archive on a hyperscaler at standard rates runs roughly $4,600/month in storage plus an estimated $18,000–$25,000/year in egress when radiologists pull studies. The same archive on a Canadian sovereign provider or on a hybrid setup (hot tier on hyperscaler, cold tier on OVHcloud or Equinix Metal in Toronto/Montréal) typically cuts the all-in cost by 25–40% while meeting PHIPA's data-residency expectations.

If You Are a Tech Worker or Engineering Leader in Canada:

  • Your AWS, Azure and GCP certifications are not at risk — those skills will remain in demand for years no matter what the regulatory landscape looks like. But your career-resilience floor in 2026 is built on portable skills: Kubernetes (CKA), Terraform/OpenTofu, Linux, Postgres, and observability tooling that runs anywhere.
  • The Canadian AI/sovereign-cloud build-out is creating jobs. TELUS estimates over 1,000 construction jobs and hundreds of long-term technology and operations roles from its B.C. data centre cluster alone. If you are within commuting distance of Kamloops, Mount Pleasant (Vancouver), Beauharnois (Québec) or any of the federal sovereign-AI sites, those roles will be posted through 2027 and 2028.
  • If you're a founder or CTO, watch the Treasury Board's Government of Canada Cloud Brokering Service and the Government Electronic Directory Services tenders. New procurement vehicles for Canadian sovereign cloud providers are being shaped this year. Smaller Canadian-controlled providers (CIRA's .CA Sovereign Cloud, OVHcloud Beauharnois, ThinkOn, and others) are likely to be more competitive on federal RFPs than they have ever been.

For All Canadians Concerned About Digital Sovereignty:

  • Your personal data is also part of this market. Every time you use a Canadian bank, e-commerce site, or government portal, you are touching infrastructure that is, statistically, 85% likely to be hosted on a U.S. hyperscaler. There is nothing you can do to fully opt out, but you can prefer Canadian-hosted services where they exist for things like email (e.g., Hover Mail, ProtonMail in Switzerland) and file storage (e.g., Sync.com, headquartered in Toronto).
  • Engage with the federal AI strategy consultation. Innovation, Science and Economic Development Canada is finalizing the national AI strategy this year, and the procurement and competition pieces are directly downstream of the kind of feedback being submitted now.

The News: What Happened

According to the Lethbridge Herald and other Canadian Press dispatches dated June 2, 2026, the Canadian Anti-Monopoly Project (CAMP) released a report concluding that Amazon, Microsoft and Google together hold roughly 85% of Canada's public cloud market — Amazon at 42%, Microsoft at 31%, and Google at 12% — well above the approximately 66% combined global share those three companies hold worldwide.

As reported by CBC News, the CAMP report calls Canada's cloud computing market "broken" and warns that subsidizing domestic alternatives without interoperability requirements could leave Canadians "buying into maplewashed dependencies" rather than producing genuine competition. The report describes cloud computing as "core infrastructure" comparable to electricity or telecommunications, and says that "dependence on a handful of U.S. hyperscalers is a sovereign risk as well as a competition problem."

According to The Globe and Mail, the report acknowledges that hyperscalers' dominance reflects "decades of engineering investment and operational expertise that no other class of provider currently replicates at scale," but argues that this entrenched advantage is precisely why competition policy intervention is now warranted. CAMP policy analyst Curtis McCord is quoted as saying competition should be treated as "essential from the very outset" in any sovereign-cloud strategy.

CBC News reports that Canada's Competition Bureau confirmed it is not currently conducting any studies on cloud computing in Canada. The CAMP report's release was timed to land ahead of the federal government's anticipated national AI strategy launch — a draft of which CBC News obtained and reported on this week, outlining six pillars and a goal of boosting Canadian business adoption of AI from 12% today to more than 50% by 2030.

Analysis: Why This Matters

Based on our analysis of the procurement landscape, recent federal announcements, and the structural economics of cloud computing, the CAMP report's significance is less about its market-share numbers (those have been widely cited for years) and more about its policy framing. By labelling cloud infrastructure a "sovereign risk" and naming "maplewashed dependencies" as a failure mode, the report makes it harder for Ottawa to fund a single Canadian champion without also addressing interoperability — the lack of which is what makes cloud markets sticky in the first place.

There is a real tension in the federal government's posture. On one hand, the Innovation Minister's May 11 announcement with TELUS is precisely the kind of "fund a domestic champion" move CAMP warns against — a multi-billion-dollar AI data centre cluster anchored by one publicly-listed Canadian telecom. On the other hand, the draft AI strategy obtained by CBC News mentions interoperability and SME readiness as explicit goals. The next year will reveal which instinct wins inside Treasury Board.

For Canadian businesses, the practical takeaway is that cloud lock-in is no longer just an architecture issue — it is also a sovereignty, procurement and political-risk issue, and one that will start showing up in customer questionnaires, RFPs, and (eventually) regulatory disclosures. Building optionality into your stack is no longer optional for organizations that touch government, health, finance, or critical-infrastructure data.

Historical Context:

The CAMP report follows a series of cloud-concentration reviews in other jurisdictions: the U.K.'s Competition and Markets Authority opened a market investigation into AWS and Azure in 2023, the U.S. Federal Trade Commission launched a similar study, and the European Commission has been pushing the Data Act and Gaia-X interoperability initiatives since 2020. Until now, Canada has been an outlier in not formally investigating its cloud market, even as the federal Office of the Auditor General has flagged concentration risks in past reports.

What Happens Next:

Watch for three things over the next 90 days:

  1. A formal Innovation Minister or Industry Minister response to the CAMP report — the report is specifically pitched at the timing of the national AI strategy launch.
  2. Treasury Board procurement-rule updates that may require interoperability and exit-plan language in new federal cloud contracts.
  3. A Competition Bureau market study announcement — currently the Bureau has said it is not studying the cloud market, but political pressure following the CAMP report is likely to change that.

Your Action Plan

Immediate (This Week):

  • Pull your last 12 months of cloud invoices and calculate cost concentration by service
  • Identify your three most provider-specific dependencies
  • Confirm your data is pinned to a Canadian region in writing
  • Read the CAMP report executive summary (canadiananti-monopolyproject.ca)

Short-term (This Quarter):

  • Negotiate egress credits or a multi-year discount at next renewal
  • Move cold storage and backups off the hyperscaler to a Canadian or independent provider
  • Add an exit-plan clause and Canadian-region requirement to any new vendor contracts
  • Audit your contracts for CLOUD Act exposure if you handle health, financial or government data

Long-term (This Year):

  • Containerize one production workload to prove portability
  • Standardize on open APIs (S3, Postgres, OCI) for new builds
  • Train at least one team member in Kubernetes and Terraform for portability
  • Submit feedback to the national AI strategy consultation if your sector is affected

Other Perspectives

Canadian Anti-Monopoly Project (Report Authors):

According to The Globe and Mail and CBC News, CAMP argues that Canada's cloud market is "broken," that 85% concentration in three U.S. firms is a sovereign and competition risk, and that subsidies to domestic providers without interoperability requirements will create "maplewashed dependencies."

Federal Government:

The Minister of Artificial Intelligence and Digital Innovation announced on May 11, 2026 a partnership with TELUS to build three B.C. AI data centres totalling more than 150 MW by 2032. According to CBC News, the draft national AI strategy obtained this week names sovereign compute as one of six pillars and targets 50% Canadian business AI adoption by 2030.

Competition Bureau:

CBC News reports the Competition Bureau has confirmed that it is not currently studying cloud computing in Canada.

Hyperscaler Position:

AWS, Microsoft and Google have publicly emphasized their Canadian data-centre investments, Canadian region availability, and roles supporting Canadian customers. As of January 2024, all three providers eliminated egress fees for customers fully exiting their platforms, addressing one specific switching-cost criticism while leaving in-flow and intra-cloud egress pricing largely unchanged.

Canadian Cloud Providers:

Smaller Canadian-controlled providers — including OVHcloud (Beauharnois, QC), ThinkOn, CIRA's .CA Sovereign Cloud, and Equinix Metal Toronto/Montréal — argue that sovereign procurement and interoperability requirements would let them compete on price and compliance even where they cannot match the hyperscalers' service breadth.

Note: Including multiple perspectives doesn't imply all views are equally valid, but ensures readers can make informed judgments.

Corrections Policy

We strive for accuracy. If you find an error in this analysis, please email us at [email protected]. We will promptly investigate and correct any factual inaccuracies.

Updates:

  • No corrections to date (as of June 2, 2026)

Sources