Written by Mike Pearlstein, CISSP, CEO of Fusion Computing Limited. Fusion Computing has run IT and security for Canadian businesses since 2012.
A client questionnaire, a contract clause or an insurance renewal form asks whether your company’s data stays in Canada. The answer has two parts: what Canadian law requires, and where your Microsoft 365 data sits today.
This post gives the law-by-law answer in one table, then shows what Microsoft keeps in Canada and how to check your own tenant.
Key takeaways
- PIPEDA has no rule that data stay in Canada. Schedule 1, clause 4.1.3 keeps an organization responsible for information “transferred to a third party for processing” (Justice Laws Website, 2026).
- If Quebec’s private-sector act applies to your business, it requires a privacy impact assessment “before communicating personal information outside Québec”, and a server in Ontario counts (LégisQuébec, 2026).
- For a tenant signed up in Canada, Microsoft commits to store five kinds of customer data at rest in Canada, “at no additional cost” (Microsoft Learn, 2026).
- Google Workspace offers data regions in the United States and Europe, and no Canadian one (Google Workspace Admin Help, 2026).
Does Canadian business data have to stay in Canada?
For most private businesses, no rule requires it. PIPEDA has no localization rule: under Schedule 1, clause 4.1.3, the business stays responsible for personal information wherever it is processed. Two rules come close. Tax books and records must be kept in Canada unless the CRA accepts a copy made available here, and Nova Scotia public bodies and their service providers must store data in Canada. Quebec and Alberta attach conditions; a contract can require more.
Which of the Canadian data privacy laws applies depends on the province. Alberta, British Columbia and Quebec have private-sector laws deemed substantially similar to PIPEDA (Office of the Privacy Commissioner of Canada, 2020). Even there, PIPEDA still applies to personal information transferred across borders and to federally regulated businesses such as banks. An Ontario business outside health care falls under PIPEDA.
What does PIPEDA say about storing data outside Canada?
PIPEDA permits it. The Office of the Privacy Commissioner of Canada (2009) states that “PIPEDA does not prohibit organizations in Canada from transferring personal information to an organization in another jurisdiction for processing”. The organization remains accountable and must provide comparable protection by contractual or other means.
A transfer for processing is a use of the information, so “additional consent for the transfer is not required” when the purpose is unchanged. Customers should still be told their information may go to another jurisdiction, where “it may be accessed by the courts, law enforcement and national security authorities”.
In 2019 the OPC consulted on a proposal that such transfers “require consent”. On September 23, 2019 it announced that its guidelines “will remain unchanged under the current law”. In Case Summary #2005-313 (OPC, 2005), complaints about outsourcing to a US-based provider were “not well-founded”.
PIPEDA defines no certified hosting status, so a claim of PIPEDA-compliant cloud hosting describes a vendor’s safeguards and contract terms.
Which Canadian laws do require data to stay in Canada?
Two rules come closest to requiring storage in Canada. Nova Scotia’s PIIDPA, section 5, says public bodies and their service providers must keep personal information “stored only in Canada and accessed only in Canada” (Nova Scotia Legislature, 2006). The Canada Revenue Agency (2020) requires tax books and records to be kept in Canada under Income Tax Act section 230. Quebec, Alberta and British Columbia attach conditions to transfers.
| Law | Who it binds | What it requires | Must data stay in Canada? |
|---|---|---|---|
| PIPEDA, Schedule 1, clause 4.1.3 | Private businesses where no substantially similar provincial law applies, such as Ontario; also cross-border transfers and federally regulated businesses | Accountability for transferred data; comparable protection by contractual or other means | No |
| Alberta PIPA, sections 6(2) and 13.1 | Organizations using a service provider outside Canada | Countries and purposes in written policies; notice to individuals | No, but notice and policy duties |
| British Columbia PIPA | Private organizations in British Columbia | No storage rule; OIPC guidance says cross-border risks must be assessed | No |
| Quebec private-sector act, section 17 | Enterprises sending or entrusting personal information outside Quebec | Privacy impact assessment, adequate protection, written agreement | No, but an assessment and written agreement first, for any transfer outside Quebec |
| Nova Scotia PIIDPA, section 5 | Public bodies, including municipalities, and their service providers | Storage and access only in Canada, with listed exceptions | Yes, for public bodies and the service providers they retain |
| British Columbia FOIPPA, section 33.1 | Public bodies in British Columbia | Disclosure outside Canada in accordance with the regulations | No since 2021; regulations and a B.C. supplementary assessment apply |
| Treasury Board Directive on Service and Digital, section 4.3.24 | Federal departments | Canadian facilities evaluated for Protected B, Protected C and classified data | No; an evaluation duty on departments, reaching a supplier only through its contract |
| Income Tax Act, section 230; CRA circular IC05-1R1 | Every business that keeps tax records | Books and records kept in Canada | Yes, or a copy available in Canada, unless the CRA permits otherwise |
This table is general information and does not replace legal advice. PHIPA, Ontario’s health information law, is covered in the clinic post on cross-border PHI and the CLOUD Act.
Client asking where your data lives? Talk it through with Fusion Computing →
Tax records
Paragraph 9 of CRA circular IC05-1R1 states that records “kept outside Canada and accessed electronically from Canada are not considered to be records in Canada”. The same paragraph lets the CRA accept a copy made available in Canada. Written permission from the CRA is the other route.
Quebec’s assessment before a transfer
Section 17 has been in force since September 2023 (Government of Québec, 2023; Commission d’accès à l’information). If Quebec’s private-sector act applies to your business, section 17 binds you: “Before communicating personal information outside Québec, a person carrying on an enterprise must conduct a privacy impact assessment”. The trigger is leaving Quebec, so a server in Ontario counts.
The information may go if the assessment finds it “would receive adequate protection”, under “a written agreement”.
Alberta’s notice for service providers outside Canada
Alberta’s rule took effect on May 1, 2010 (OIPC Alberta, 2010). Section 6(2) of PIPA (Alberta King’s Printer, 2025) covers an organization using “a service provider outside Canada to collect, use, disclose or store personal information”. Its policies must name the countries involved and the purposes authorized.
Section 13.1 adds a notice to individuals, given “before or at the time of collecting or transferring the information”.
Public bodies and the vendors that serve them
Under Nova Scotia’s PIIDPA, a service provider is a person “retained under a contract to perform services for a public body”. Section 13 sets fines of up to CA$500,000 for a corporate service provider.
British Columbia’s FOIPPA amendments received royal assent on November 25, 2021 (Government of B.C., 2022). Section 33.1 now allows disclosure outside Canada “in accordance with the regulations”. The Government of B.C. adds that a supplementary assessment is required when sensitive information is stored outside Canada.
For private organizations, the OIPC for British Columbia (2018) wrote that “PIPA does not restrict storage and access to personal information outside of Canada”. Its January 2026 guidance on AI scribes says organizations “must assess the potential risks of any cross-border disclosures” as part of their security assessment.
Federal work rated Protected B
Section 4.3.24 of the Directive on Service and Digital (Treasury Board of Canada Secretariat, 2025) binds federal departments. Canadian computing facilities must be “identified and evaluated as a principal delivery option” for Protected B, Protected C and classified data. A supplier takes on a residency obligation only through the wording of its own contract.
What does “hosted in Canada” mean for Microsoft 365?
For a tenant signed up in Canada, Microsoft commits to store five kinds of customer data at rest in Canada: Exchange Online mailbox content, SharePoint Online site content and files, OneDrive files, Teams chat messages and stored Copilot interactions. Microsoft’s Canadian datacentres are in Quebec City and Toronto (Microsoft Learn, 2026). The directory, Microsoft Forms and some request processing fall outside that commitment.
The sign-up country decides whether your tenant qualifies, because “This country or region establishes the Default Geography” (Microsoft Learn, 2026). A tenant with a Default Geography of Canada gets the commitment “at no additional cost”.
The commitment covers mail, files, Teams chats and stored Copilot interactions, while the Entra ID directory sits in the North America geo and Forms data in the United States.
Why Canadian firms bring this work to Fusion Computing
CISSP-led, securing IT for Canadian SMBs across Toronto, Hamilton, and Metro Vancouver since 2012.
What the Canadian commitment does not cover
Entra ID maps the tenant location to a geo such as “North America”, which is not a Canada commitment, and “Tenant location can’t be changed after it’s set” (Microsoft Learn, 2025). Microsoft Forms stores data in the United States for tenants outside the EU and Australia (Microsoft Learn Data Location FAQ, 2026). Microsoft also notes that “On occasion, a customer request may be handled by servers in a different region”.
Copilot storage and processing
Microsoft says the content of Copilot interactions and the related semantic index “are stored at rest in the relevant Local Region Geography” (Microsoft Learn, 2026). Processing is on a later timeline. A Microsoft 365 Blog post (2025), updated by an editor’s note on April 3, 2026, says local processing is expected, “with support for Canada to follow in 2027”.
Residency is a separate question from Copilot oversharing inside the tenant.
Advanced Data Residency and Multi-Geo
Advanced Data Residency (ADR) is an add-on, and Canada is eligible (Microsoft Learn, 2026). It adds Defender for Office P1, Exchange Online Protection, Office for the web, Viva Connections and select Purview services. Business Basic, Standard and Premium qualify, and “Customers must cover 100% of paid licenses in the Tenant with ADR add-on licenses”.
ADR is also the only commitment that includes migration services. Multi-Geo is closed to Microsoft 365 Business plans: “Subscriptions for small businesses and education don’t currently qualify for the Multi-Geo add-on” (Microsoft Learn, 2026).
Microsoft documents no Canadian equivalent of the EU Data Boundary (Microsoft Learn, 2026), within which Microsoft commits to “store and process” customer data.
How do you check where your Microsoft 365 data is stored?
The Microsoft 365 admin centre shows it on the Data location card. Microsoft Learn (2026) gives the path as “Settings > Org settings > Organization profile > Data location”. The card lists a Current Geography and a Committed Geography. Under “No Commitment”, Microsoft “stores data where it best enables service delivery”.
- Sign in to the Microsoft 365 admin centre as a Global Administrator and open Settings, then Org settings.
- Select the Organization profile tab, then Data location.
- For each service, read the Current Geography and the Committed Geography.
- List every service that shows “No Commitment” or a Current Geography outside Canada.
- Save a dated screenshot of the card for whoever asked you.
If a service that ADR covers shows a Current Geography outside Canada, ADR is the migration route. It must cover every paid licence, and Planner is not part of it.
Unsure what your Data location card shows? Ask Fusion Computing →
Does keeping data in Canada keep it away from US law?
No. The US CLOUD Act, 18 U.S.C. 2713, applies “regardless of whether such communication, record, or other information is located within or outside of the United States” (Legal Information Institute, Cornell Law School). Residency is where data is stored. Sovereignty is whose law can reach it.
Microsoft’s pledge to Canada (Microsoft On the Issues, 2025) is to “challenge any government demand for Canadian government or commercial customer data … where we have a legal basis for doing so”. The OPC wrote in 2009 that no contract can “override the laws of a foreign jurisdiction”.
What about Google Workspace, AWS and your backup copy?
Google Workspace has no Canadian data region. Google Workspace Admin Help (2026) states: “Your location options are the United States, European Union (labeled Europe in the Google Admin console), or No preference”. Business Starter is outside the supported editions. Google Cloud, AWS and Azure each run Canadian regions.
The Google Workspace vs Microsoft 365 comparison covers the other differences.
- Google Cloud runs regions in Montreal and Toronto (Google Cloud, 2026).
- AWS runs ca-central-1 (Canada Central) and ca-west-1 in Calgary (AWS, 2026). Calgary opened on December 20, 2023 (AWS News Blog, 2023) and must be enabled before use.
- Azure lists Canada Central in Toronto and Canada East in Quebec (Microsoft Learn, 2026).
Ask where your backup sits too. Managed backup creates a second copy with its own location, and every question in the next section applies to it.
What should you ask a cloud vendor about residency?
Five questions settle a vendor’s residency position: where data rests, what the commitment covers, who else handles the data, where it is processed, and whether the contract says so. Ask them of every system that holds client or employee information, including the backup and any AI tool.
- In which country, and which named region, is our data stored at rest?
- Does that commitment cover backups and support data?
- Which sub-processors handle our data, and where is each one?
- Where is our data processed, including by any AI feature?
- Will you write the location commitment into the contract?
Record the answers in a data-residency map of your own systems. Give each system a row for where data rests, where the backup sits, where data is processed and whose law reaches the provider.
Vendor answers on residency not adding up? Review them with Fusion Computing →
About Fusion Computing
Fusion Computing is CISSP-led and works with Canadian businesses with 10 to 150 employees. Fusion Computing runs managed IT services, co-managed IT and managed cybersecurity, and quotes compliance documentation, such as PIPEDA work, as a project. Fusion Computing’s Microsoft 365 backup runs on ConnectWise SaaS Backup powered by Keepit. Each residency commitment in this post belongs to the vendor named.
The free compliance readiness assessment scores your business against PIPEDA in a self-assessment and gives a phased roadmap.
What to do next
Open the Data location card and save what it shows. Check whether Quebec, Alberta, a Nova Scotia public body or a federal contract brings one of the table’s rules into play. Confirm where your tax records and backups sit. Add the outside-Canada notice to your privacy policy. Then build the data-residency map.
Fusion Computing helps Canadian businesses across Toronto and the GTA, Hamilton, and Metro Vancouver with managed IT, cybersecurity, and Microsoft 365.
Frequently Asked Questions
Is my Microsoft 365 data stored in Canada?
If your tenant was signed up with Canada as its country, Microsoft commits to store Exchange Online mailbox content, SharePoint Online site content, OneDrive files, Teams chat messages and stored Copilot interactions at rest in Canada, at no additional cost. The Entra ID directory sits in the North America geo and Microsoft Forms data in the United States. An older tenant can show a different Current Geography, so check the Data location card.
Does PIPEDA require data to be stored in Canada?
No. The Office of the Privacy Commissioner of Canada states there is nothing in PIPEDA that prevents organizations from outsourcing the processing of data. Under Schedule 1, clause 4.1.3, the organization remains responsible for personal information transferred to a third party and must use contractual or other means to provide a comparable level of protection.
Does Quebec Law 25 apply if my servers are in Ontario?
Yes, when the personal information falls under Quebec’s private-sector act. Section 17 requires a privacy impact assessment before personal information is communicated outside Quebec, so the trigger is the provincial border and a server in Ontario counts. The transfer also needs a written agreement. The rule has been in force since September 2023.
Is Google Workspace data stored in Canada?
Google Workspace has no Canadian data region. Google’s Admin Help lists the location options as the United States, the European Union or No preference, and Business Starter is outside the supported editions. Google Cloud is a separate product and does run regions in Montreal and Toronto.
Does Microsoft Copilot process data in Canada?
Stored Copilot interactions and the related semantic index are kept at rest in the tenant’s local region, which for a Canadian tenant is Canada. Processing is a separate matter. Microsoft’s November 2025 announcement of in-country processing, as updated by an editor’s note on April 3, 2026, says support for Canada is expected in 2027.
Can US authorities reach data stored in Canada?
US law can apply to it. The US CLOUD Act, 18 U.S.C. 2713, covers information in a provider’s possession, custody or control regardless of whether it is located within or outside of the United States. Microsoft has pledged to challenge government demands for Canadian customer data where it has a legal basis for doing so.
Do I need to tell customers their data is stored outside Canada?
The Office of the Privacy Commissioner’s guidelines call for it. Organizations should advise customers that their personal information may be sent to another jurisdiction for processing and may be accessed there by courts, law enforcement and national security authorities. Alberta’s PIPA goes further and requires notice at or before collection or transfer when a service provider is outside Canada.
Can I keep my accounting records in a cloud system outside Canada?
Only with a copy made available in Canada or the CRA’s written permission. Section 230 of the Income Tax Act requires books and records to be kept in Canada, and CRA circular IC05-1R1 says records kept outside Canada and accessed electronically from Canada are not considered to be records in Canada.
How do I check where my Microsoft 365 tenant’s data is located?
Sign in to the Microsoft 365 admin centre as a Global Administrator and go to Settings, Org settings, Organization profile, then Data location. The card shows a Current Geography and a Committed Geography. No Commitment means Microsoft stores the data where it best enables service delivery. Advanced Data Residency is the add-on that includes migration services.

