Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Copilots and generative AI features aren't available in all regions and languages. In some cases, even where there's some in region capacity, data may still have to move outside of the region for availability reasons or because certain features depend on other capacity or Microsoft services. For this reason and depending on where your environment is hosted and what features you use, you might need to allow data movement across regions to use Copilots and generative AI features. This article explains how to do that.
Note
- Copilots and generative AI features that are generally available are turned on by default. However, you might need to allow data movement across regions to use all Copilot and generative AI features.
- If you don't allow data movement across regions, that doesn't turn off all Copilots and generative AI features. Copilots and generative AI features are allowed as capacity is made available in the region.
- Certain generative AI features are powered by Microsoft 365 services and store data according to Microsoft 365 terms and data residency commitments.
Regions where data is processed for Copilots and generative AI features
When you allow data movement across regions, your inputs (prompts) and outputs (results) might move outside of your region to the location where the generative AI feature is hosted. We don't use your data to train, retrain, or improve Azure OpenAI Service foundation models. Learn more about product-specific Copilot availability in the Copilot international availability report.
The following table lists the regions where your Power Platform or Dynamics 365 environment is hosted and the corresponding regions where the Azure OpenAI service and Bing search service are hosted.
| Region where your Power Platform or Dynamics 365 environment is hosted | Region where Azure OpenAI Service is hosted | Region where data is stored and processed for Bing Search |
|---|---|---|
| United States | In region* | United States |
| Europe** | In European Untion (EU) Data Boundary | United States |
| France Germany Norway Sweden Switzerland** |
In EU Data Boundary | United States |
| Brazil Canada Japan Korea South Africa United Arab Emirates |
United States | United States |
| Asia Singapore |
In region* or United States | United States |
| Australia India |
In region* or United States | United States |
| United Kingdom | In region* or in EU Data Boundary | United States |
| Government cloud (GCC, GCC High) | In region* | United States |
*In region means within the geographical region of your Power Platform or Dynamics 365 environment.
**If your Power Platform and Dynamics 365 environments are hosted in the EU Data Boundary, we use an Azure OpenAI endpoint in the same boundary.
Learn more about EU Data Boundary in What is the EU Data Boundary?.
Turn on data movement, Bing search, Microsoft 365 services, and flex routing
To turn on data movement across regions, Bing search, Microsoft 365 services, and flex routing for Copilots and generative AI features, you must consent to the terms of use in the Power Platform admin center. To grant consent, you must be a Power Platform administrator or Dynamics 365 administrator.
Sign in to the Power Platform admin center.
In the navigation pane, select Manage.
In the Manage pane, select Environments. The Environments page is displayed.
Select the name of your environment. Details about your environment are displayed.
In the Generative AI features card, select Edit. The Generative AI features pane is displayed.
Review the terms of use and select the Move data across regions checkbox.
Note
The Move data across regions checkbox isn't displayed for US and government cloud regions.
When the Move data across regions checkbox is selected, your inputs (prompts) and outputs (results) might move outside of your region to the location where the generative AI feature is hosted, as described in the preceding table.
- Moving data across regions only happens if the required model isn't deployed locally, if capacity is maxed out as overflow, or if there is a reliability-impacting issue with the local model.
- Microsoft doesn't log, store, or retain any input or output data during this process. There is no persistence of the data.
For Core Online Services, allowing data movement across regions with this toggle doesn't impact the commitments made in the Product Terms regarding storage of Customer Data at rest. Learn more in Regions where data is processed for Copilots and generative AI features.
Note
Data movement that occurred while your environment was allowed to move data across regions can't be reversed by clearing the Move data across regions checkbox.
Review the terms of use and select the Bing search checkbox.
When the Bing search feature is turned on, your agent in Microsoft Copilot Studio can use the data sources you provided, but it can use Bing's APIs to index the results better and find the best answer from within your data sources. Learn more in Generative answers.
Note
If the Move data across regions checkbox is displayed in the Generative AI features pane, you must have it already selected in order to select the Bing search checkbox.
Review the terms of use and select the Microsoft 365 services checkbox.
When the Microsoft 365 services feature is turned on, users can use features powered by Microsoft 365 services.
To learn more about how the Microsoft 365 services feature affects Copilot Studio, go to Manage activity data powered by Microsoft 365 services, Review agent activity, and View advanced analytics in Microsoft Viva Insights. For information about data locations, go to Data locations in Copilot Studio.
Note
If the Move data across regions checkbox is displayed in the Generative AI features pane, you must have it already selected in order to select the Microsoft 365 services checkbox.
If your environment is in the European Union Data Boundary (EUDB), the Allow flex routing during periods of peak load checkbox is displayed.
Flex routing lets customers in the EUDB allow large language model (LLM) inferencing to occur outside the EU Data Boundary during periods of peak demand to help maintain a consistent Copilot experience. Inferencing is the processing step when an AI model executes the prompt to produce an output or response, such as summarizing content or answering a question.
No matter where LLM inferencing occurs, data is encrypted in transit and at rest. Data at rest continues to be stored inside the EU Data Boundary, except for limited pseudonymized data which may be stored outside the EU Data Boundary for security and operational purposes. For more information, see Services that transfer a subset of Customer Data, pseudonymized personal data, or Professional Services Data out of the EU Data Boundary on an ongoing basis.
For tenants that are managed through the Microsoft 365 admin center, the default value of the Allow flex routing during periods of peak load setting in the Power Platform admin center is the same as the Microsoft 365 admin center toggle, unless the Move data across regions setting is turned off.
If the Allow flex routing during periods of peak load checkbox is visible but unavailable, it means either the feature is currently turned off in the Microsoft 365 admin center or the Move data across regions setting isn't enabled in the Power Platform admin center.
Flex routing is on for all tenants excluding those customers that are categorized as Enterprise (Commercial and Public Sector) or SME&C Public Sector, but can be changed. All tenant administrators are encouraged to check their tenant's flex routing setting to ensure it aligns with their company's requirements.
- Select the Allow flex routing during periods of peak load checkbox, if desired. This setting allows LLM inferencing and the storage of associated pseudonymized data to occur outside the EU Data Boundary during periods of peak demand.
- If you don’t want to allow flex routing, clear the Allow flex routing during periods of peak load checkbox, which results in all LLM inferencing occuring inside the EU Data Boundary, even during periods of peak demand.
For more information, see Flex routing (EU and EFTA).
Select Save.
Copilots and generative AI features that depend on data movement across regions
The following table lists Copilots and generative AI features that depend on the Move data across regions checkbox.
When the Move data across regions checkbox is selected, these features work at their best, allowing use of other region capacity when needed.
When the Move data across regions checkbox isn't selected, no data is sent outside of the region, so depending on the in region capacities, some of these features won’t work.
More Copilots and generative AI features will be available in the future.
Languages availability
Learn more about the languages that are supported in the Copilot international availability report.
Frequently asked questions (FAQ)
Is it possible to modify the "Move data across regions" checkbox at scale across all my environments?
Yes, you can use the Generative AI settings environment rule to control this at scale. Learn more in Rules.
What features are turned off when you clear the “Move data across regions” checkbox?
The Move data across regions checkbox isn't intended to turn off Copilots and generative AI features. Not all Copilot and generative AI features are governed by this setting. Some features use alternate services and are not subject to the Move data across regions setting.
When you clear the Move data across regions checkbox, it may turn off some features that require data movement. As we add new capacities to new regions, these features may work with in region capacity at some point. Use feature-dedicated controls to turn off unwanted features.
Why do I need to select the “Move data across regions” checkbox if my environment has in region capacity?
Some regions may have limited capacity, or no capacity at all. To ensure availability of Copilots and generative AI features, we may need to move the data outside of the region for processing.
Why does the “Move data across regions” checkbox not appear in some of my environments?
If your environment is in a region that has full in region capacity, the Move data across regions checkbox doesn't appear.