Microsoft Copilot Data Boundary in Australia: Resource Locations Reference

Microsoft Copilot processes and stores data in specific geographic regions. For Australian organizations, the data boundary for Copilot is the Australia region, which includes data centers in Canberra and Sydney. This boundary determines where your Copilot prompts, responses, and associated Microsoft 365 data reside. Understanding the exact resource locations helps you comply with local data residency requirements and privacy regulations. This article lists the physical and logical resource locations for Copilot in Australia, explains how data flows within the boundary, and clarifies what data stays in-region versus what may leave temporarily.

What the Copilot Data Boundary in Australia Covers

The Copilot data boundary in Australia defines the geographic perimeter within which Copilot processes and stores customer data. This boundary includes two Azure regions: Australia East located in Sydney and Australia Southeast located in Canberra. All Copilot customer data at rest — including prompts, generated responses, and associated metadata — is stored in these two regions.

Microsoft 365 services that Copilot relies on, such as Exchange Online, SharePoint Online, and OneDrive for Business, also maintain their primary data residency in Australia for customers with Australian tenancy. This means that when you use Copilot in Word, Excel, PowerPoint, or Outlook, the underlying data from these services does not leave the Australian boundary.

Copilot uses a combination of Azure OpenAI Service and Microsoft 365 AI infrastructure. The Azure OpenAI Service endpoints used by Copilot are provisioned in the Australia East region. Any fine-tuning or model customization specific to your tenant also occurs within this region.

Data Flow Within the Boundary

When you submit a prompt to Copilot, the request travels from your device to the nearest Microsoft 365 entry point. If that entry point is outside Australia, the request is routed to the Australian data boundary for processing. The Azure OpenAI Service in Australia East processes the prompt and generates a response. That response is stored in Australia East or Australia Southeast depending on the service using it. For example, Copilot in Word stores the response in your OneDrive for Business data, which resides in Australia East for Australian tenants.

Data at Rest vs Data in Transit

Data at rest — prompts, responses, and logs — never leaves the Australian boundary. Data in transit may cross regional boundaries during routing. For instance, if your network routes traffic through a non-Australian point of presence, the encrypted data passes through that node but is not stored. Microsoft guarantees that no customer data is stored outside the Australian boundary during transit.

Steps to Verify Your Copilot Data Residency in Australia

You can confirm that your Microsoft 365 tenant and Copilot data reside in Australia using the Microsoft 365 admin center. The following steps apply to global administrators or users with the Billing Administrator role.

1. Open the Microsoft 365 admin center
   Go to admin.microsoft.com and sign in with your global administrator account.
2. Navigate to Settings > Org settings
   In the left navigation pane, select Settings and then Org settings. This page shows your tenant-wide configurations.
3. Select the Organization profile tab
   Click the Organization profile tab at the top of the page. Look for the Data location section.
4. Check the Data location value
   Under Data location, you see the country or region where your Microsoft 365 data is stored. For Australian tenants, this displays Australia.
5. Verify Copilot-specific data location
   In the same section, find the entry for Copilot. It lists the region as Australia East or Australia Southeast. If this entry is missing, your tenant may not have Copilot provisioned in Australia yet.

You can also use the Microsoft 365 Data Residency service page in the admin center to view a detailed report of data locations for each workload, including Exchange Online, SharePoint Online, OneDrive for Business, and Microsoft Copilot.

If Copilot Data Appears Outside the Australian Boundary

In rare cases, you may notice that some Copilot-related data seems to originate from a non-Australian region. This section covers the most common causes and how to address them.

Copilot Returns References to Non-Australian Data Sources

Copilot can ground responses in data from Microsoft Graph, which includes SharePoint sites and OneDrive files. If your tenant has SharePoint sites in other regions, Copilot may reference that content. The data itself remains in its original region. Copilot does not move data between regions. To prevent this, restrict SharePoint site creation to Australian regions only using the SharePoint admin center.

Transient Processing in Non-Australian Regions

During peak load, Copilot may use Azure OpenAI Service instances in other regions for transient processing. This processing is temporary and no data is stored outside Australia. Microsoft has confirmed that this transient processing is limited to a few seconds and does not constitute data residency. If your compliance policy prohibits any processing outside Australia, contact Microsoft Support to request dedicated capacity in Australia East.

Network Routing Through Non-Australian Points of Presence

Your organization’s network configuration may route Copilot traffic through points of presence outside Australia. This is a network-level issue, not a Copilot data residency issue. To fix this, configure your network to use Microsoft 365 network connectivity principles, including direct egress from Australian ISPs and avoiding VPN or proxy exit points outside Australia.

Copilot Data Boundary in Australia vs Other Regions: Key Differences

Item	Australia Boundary	Other Regions Example (EU)
Azure regions used	Australia East, Australia Southeast	North Europe, West Europe
Data at rest storage	Australia only	EU only
Transient processing	May use non-Australian regions during peak load	May use non-EU regions during peak load
Microsoft 365 data residency	Australia for Exchange, SharePoint, OneDrive	EU for Exchange, SharePoint, OneDrive
Compliance certifications	IRAP, ASD Essential Eight	GDPR, ISO 27001

The table above shows that the Australia data boundary is functionally identical to other regional boundaries in terms of data at rest storage. The key difference is the specific Azure regions and the compliance certifications that apply to Australian government and regulated industries.

You can now confirm that your Copilot data resides in Australian data centers using the Microsoft 365 admin center. If your compliance policy requires strict data residency, review your SharePoint site region settings and network routing. For advanced control, consider using the Microsoft 365 Data Residency service to enable in-region processing for Copilot, which ensures that even transient processing stays within Australia.