Regional settings and data locations for organizations using Copilot Studio


Power Virtual Agents capabilities and features are now part of Microsoft Copilot Studio following significant investments in generative AI and enhanced integrations across Microsoft Copilot.

Some articles and screenshots may refer to Power Virtual Agents while we update documentation and training content.

Copilot Studio supports multiple globalization scenarios, and lets you choose where you want your data to live.

Supported locales and formats

Copilots built with Copilot Studio understand and display content that's locally relevant to the user. Localized handling and formatting are based on the user's browser locale setting, and include the following elements within a chat conversation:

  • Date and time
  • Numbers
  • ZIP or postal code
  • Currency
  • Speed

Copilot Studio supports the following display formatting locales:

  • en-AU
  • en-CA
  • en-GB
  • en-IN
  • en-US

For example, if the user's browser locale setting is en-GB, the copilot knows that a date of 2/3 equates to March 2. If the browser locale setting is en-US, the same date equates to February 3.

Copilot Studio can be deployed into Microsoft Azure datacenters (also referred to as "regions"). You can create a copilot in your tenant's location by default, or you can choose the datacenter you want to use when setting up your environment.

Data locations

Microsoft might replicate customer data to other regions available within the same geography for data durability.

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.

Data is stored in the United States if a copilot author's tenant location isn't listed under the following Data locations table.

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)
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)
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 doesn't transfer customer data outside the selected Azure geographic location for Copilot Studio except when:

  • The geographic location is South America.

  • Microsoft must provide customer support, troubleshoot the service, or comply with legal requirements.

  • Customers use services that are designed to operate globally, including:

    • Email used to send marketing messaging globally, as configured by the customer.

    • The Dynamics 365 home page, which stores application names, descriptions, and logos globally for performance.

    • Microsoft Entra ID (Microsoft Entra ID), which might store Microsoft Entra ID data globally.

    • Azure Multi-Factor Authentication, which might store multi-factor authentication data globally.

    • Customer data collected during the onboarding process by the Microsoft 365 admin center.

    • Services that provide global routing functions and don't process or store customer data. Services providing routing include Azure DNS, which provides domain name services that route to different regions. Other such services include preview, beta, or other pre-release services, which typically store customer data in the United States but might store it globally.

    • 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.

  • Customers configure external services to extend Copilot Studio. Such customer configurations might cause customer data to be transferred outside of the selected geographic location. Examples of customer configurable external services include: