The short version: Microsoft doesn't state where a New Zealand tenant's Copilot Studio data sits, as at 23 September 2026. Its data-location table lists Australia but not New Zealand, defaulting an unlisted tenant to the United States. Power Platform's own region rules place most non-Australian tenants outside Australia by default, with an exception available. The only definitive answer for one specific tenant is the Region column for that environment in the Power Platform admin centre.
What Microsoft's Copilot Studio page lists
As at 23 September 2026, Microsoft's data-locations page for Copilot Studio names 18 Azure geographies: Asia, Australia, Canada, Europe, France, Germany, India, Japan, Norway, Singapore, South Africa, South America, South Korea, Sweden, Switzerland, United Arab Emirates, United Kingdom and United States. Australia's own row lists Australia East (New South Wales) and Australia Southeast (Victoria) as its datacentres. New Zealand doesn't appear anywhere in the table, and it isn't folded into the Australia row either. The page's own fallback rule reads: "If a tenant's location isn't listed in the data locations table, data is stored in the United States."
| Question | What Microsoft's page says | Source |
|---|---|---|
| Does New Zealand have a listed geography? | No. 18 geographies are listed; New Zealand isn't one | Data locations in Copilot Studio |
| What happens if a tenant's location isn't listed? | "Data is stored in the United States" | Data locations in Copilot Studio |
| Does Microsoft say this US fallback applies to NZ specifically? | No. Microsoft names New Zealand on none of its region pages | Data locations in Copilot Studio |
That last row matters more than it looks. Copilot Studio's own data-location page and Power Platform's environment-region system are two separate pieces of Microsoft documentation, and Microsoft doesn't explicitly say how the Copilot Studio fallback interacts with the region an NZ tenant's actual Power Platform environment is running in. Treat the US fallback as one documented rule, not the final word on where an NZ tenant's agent data sits.
How Power Platform assigns a tenant's region
A Copilot Studio agent lives inside a Power Platform environment, and that environment's region is governed by Power Platform's own rules, not Copilot Studio's data-location page in isolation. Two things are true here as at 23 September 2026. First, Power Platform's regions-overview page states plainly: for a tenant whose Microsoft Entra home location is anywhere other than India or Australia, it can create a database in "any region except India and Australia," though "you can get an exception for Australia." Second, Microsoft's newer macro-region system groups Asia-Pacific as Singapore, Australia, India, Japan and South Korea together, notes that "Australia and India geographies have tax restrictions," and without Advanced Data Residency (ADR) turned on for every Microsoft 365 seat in the tenant, the platform auto-assigns a specific datacentre within that macro region "based on capacity, product availability, and performance considerations," not a fixed, guaranteed one.
Existing environments aren't swept up by rule changes after the fact: Microsoft states that environments "continue to retain their selected datacenter region" once created. That's why a long-running NZ tenant's environment can sit in Australia today even though a brand-new NZ tenant, without an exception, generally can't choose Australia for a new one.
The honest answer: check the Region column
Given two separate rule sets and no sentence anywhere naming New Zealand, the only way to answer this for a real client is to look. In the Power Platform admin centre, under Manage > Environments, the Region column shows the actual datacentre region assigned to that specific environment. For NZ tenants with environments created in past years, that column commonly reads Australia, a legacy of Australia being the practical default before the current tax-restriction rule tightened who can choose it going forward. A newer environment created without ADR could land anywhere in the Asia-Pacific macro region instead, Singapore, Australia, India, Japan or South Korea, decided by Microsoft's own capacity algorithm rather than a choice anyone in the business made. Check that column before promising a client an answer about where their agent's data sits.
What leaves the region for generative answers
Copilot Studio's generative AI features, the ones built on Azure OpenAI Service and Bing Search, are available in environments created for the United States and other supported geographic locations. Whatever region an NZ tenant's environment actually sits in, per the Region column above, using generative features from a location Microsoft hasn't listed as supported moves data across a regional boundary, and a Power Platform administrator has to explicitly enable that movement, a setting that can't be reversed by later disabling it.
One more carve-out worth knowing: agent activity data, including conversation logs, is stored in the geographic region of the end user's Exchange mailbox rather than the agent's own environment geography, which can put that specific data somewhere different again.
The EU data boundary, for comparison
Microsoft offers a named EU Data Boundary commitment, but it only applies when a tenant carries an EU or EFTA billing address and every one of its environments is created inside a geography within the EU Data Boundary. There's no equivalent named boundary for New Zealand or the wider Asia-Pacific region, and no NZ-specific commitment to check against. For an NZ firm, the practical takeaway is the same one this whole post makes: don't promise a client Australasian or NZ-local data residency for Copilot Studio from a general rule alone, check the actual environment's Region column first. Residency is a separate question from cost; what the client's agent would actually cost to run is covered in the Copilot Studio pricing breakdown.
What it means for a firm under 20 staff
Most NZ firms under 20 staff building an internal agent have no regulatory requirement forcing the data to stay onshore, so wherever the environment sits is rarely a blocker on its own. Where it does matter is a client contract, tender or industry code that specifically requires data to stay in Australia or New Zealand. As at 23 September 2026, the honest process is: check the Region column for the specific environment first, since a long-running NZ tenant may already sit in Australia; if it needs to be Australia and currently isn't, the exception path runs through Advanced Data Residency rather than a Copilot Studio setting. Nothing here is a Copilot Studio-specific fix, because the region an agent's data sits in is decided at the Power Platform environment level, not inside Copilot Studio itself.
Common questions
Does New Zealand have its own data region for Copilot Studio or Power Platform?
No. Neither Copilot Studio's data-location table nor Power Platform's region and macro-region documentation names New Zealand anywhere, as at 23 September 2026.
Where does an NZ tenant's Copilot Studio data actually get stored?
Microsoft doesn't say by name. The only reliable answer for a specific tenant is the Region column for that environment in the Power Platform admin centre (Manage > Environments). Many NZ tenants with environments created in past years show Australia there; a newer environment created without Advanced Data Residency lands somewhere in the Asia-Pacific macro region, Singapore, Australia, India, Japan or South Korea, chosen by Microsoft's own capacity algorithm.
Can an NZ business get its Power Platform environment placed in Australia?
Not by default. Microsoft's region rules block a tenant whose home location isn't Australia or India from creating a new environment in Australia, though an exception for Australia is available. An environment created before this rule tightened keeps whatever region it was originally assigned, regardless of the current rule.
Need this in writing for a client or a tender?
Free 30-minute call. Tell me what the contract requires and I'll check the tenant's actual Region setting with you rather than guess.