Data locations in Copilot Studio
Data management in Copilot Studio is comprehensive, offering flexibility and control to organizations while supporting a wide range of international standards and requirements.
This allows businesses to operate globally without compromising on compliance or user experience.
With Copilot Studio, you can deploy your agent to any of the Microsoft Azure datacenters around the world.
You can also configure your environment to suit your development or production needs. For example, you can import and export agents as solutions in the Power Apps portal to support application lifecycle management (ALM) workflows.
Data locations
No matter where customer data is stored, Microsoft doesn't control or limit the locations from which customers or their users can access customer data.
Microsoft might replicate customer data to other regions available within the same geography for data durability.
Learn more about Copilot availability by geography.
Note
If a tenant's location is not listed in the data locations table, data is stored in the United States.
| Azure geographic locations | Azure datacenters (regions) |
|---|---|
| Asia Pacific | Southeast Asia (Singapore), East Asia (Hong Kong Special Administrative Region) |
| Australia | Australia East (New South Wales), Australia Southeast (Victoria) |
| Canada | Canada Central (Toronto), Canada East (Quebec City) |
| Europe | West Europe (Netherlands), North Europe (Ireland) |
| France | France Central (Paris), France South (Marseille) |
| Germany | Germany North (Berlin), Germany West Central (Frankfurt) |
| India | Central India (Pune), South India (Chennai) |
| Japan | Japan East (Tokyo, Saitama), Japan West (Osaka) |
| Norway | Norway East (Oslo), Norway West (Stavanger) |
| South Africa | South Africa North (Johannesburg), South Africa West (Cape Town) |
| South America | Brazil South (Sao Paulo State) (As there is only one region in Brazil, customer data in Brazil South might be replicated to South Central US (Texas) for disaster recovery purposes) |
| South Korea | South Korea Central (Seoul), South Korea South (Busan) |
| Sweden | Sweden Central (Gävle) |
| Switzerland | Switzerland North (Zurich), Switzerland West (Geneva) |
| United Arab Emirates | UAE North (Dubai), UAE Central (Abu Dhabi) |
| United Kingdom | UK South (London), UK West (Cardiff, Durham) |
| United States | East US (Virginia), South Central US (Texas), West US 2 (Washington) |
Customer data
Microsoft ensures that customer data in Copilot Studio remains within the chosen Azure geographic location, with some exceptions:
South America: Data may be replicated to South Central US (Texas) for disaster recovery purposes.
Support and compliance: Data might be transferred to provide customer support, troubleshoot issues, or comply with legal requirements.
Global services: Certain services inherently require global operation and may store data globally. Examples include:
Email Marketing: Configured by customers to send messages globally.
Dynamics 365 Home Page: Stores application details globally for performance.
Microsoft Entra ID: Might store data globally.
Microsoft Entra multifactor authentication: Data might be stored globally.
Microsoft 365 admin center: Collects customer data during onboarding.
Routing Services: These services, such as Azure DNS, provide global routing without processing or storing customer data.
Additionally, certain types of customer data (specifically the application name, application description, and application logo) are stored globally, rather than in the primary storage geographic location.
External services: Customers can configure Copilot Studio to use external services, which may transfer data outside the selected geographic location. Examples include:
Customer Service hand-off: Transfers escalations to human representatives.
Multi-channel configurations: Integrations with platforms like Facebook and Microsoft Teams.
Dynamics 365 Customer Service Insights: Topic suggestions may be processed in a different geographic region.