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.
When you build an app with Copilot Studio and deploy it to Copilot Managed Runtime, the published app is stored in your Power Platform environment's geography. While you're building an app in Copilot Studio, Copilot Studio also stores and processes app-building data in a geography based on the maker's user profile and tenant, not on the environment.
How the app building geography is determined
The Copilot Studio app building feature determines the app-building data location and processing from the maker's sign-in token, in this order:
- The user's preferred data location. Available only in Multi-Geo tenants.
- The user's Country or region (the
countryattribute in Microsoft Entra ID). This value is included in the token whenever it's a two-letter value. When it's present, the tenant's country or region isn't checked. Copilot Studio doesn't read the user's usage location. If the two-letter value isn't a recognized country code, the app-building session doesn't start and the maker sees a "service unavailable" error. Copilot Studio doesn't fall back to a default geography in this case. - The tenant's country or region, selected when the Microsoft Entra tenant was created. This value is used only when neither of the previous values is in the token: no preferred data location is set, and the user's Country or region is empty or isn't a two-letter value (for example, a spelled-out name such as France).
Only administrators can change these settings.
Important
- The resulting geography can differ from the geography of the Power Platform environment being used. When it does, app-building data might be stored and processed outside the environment's geography.
- Keep app-building data in the expected geography.
To keep app-building data in the same geography as your Power Platform environment, make sure each maker's profile resolves to that geography:
Multi-Geo tenants: Set each maker's preferred data location to the geography of the environments they build in. This setting takes priority over Country or region.
All other tenants: Set each maker's Country or region to the correct two-letter country code (for example,
FRorDE) for the environment's geography.- Any two-letter value overrides the tenant's country or region. For example, a value of
USon a maker who builds in an EU environment places their app-building data outside the EU. - An unrecognized two-letter value stops app building. Makers can't start a session until the value is corrected.
- A spelled-out name, such as "France", is ignored, and the tenant's country or region is used instead.
- Setting usage location alone has no effect on where app-building data is placed.
- Any two-letter value overrides the tenant's country or region. For example, a value of
Tenant's country or region: This value is used only as a last resort, when a maker has no preferred data location and no two-letter Country or region. If it doesn't match your environments' geography, set every maker's Country or region explicitly.
Environment placement: Create environments in the geography where your makers' profiles resolve, or update the makers' profiles to match the environments they use.
EU Data Boundary customers
To bring your app-building data within the EU Data Boundary, ensure both of the following conditions are true:
Your tenant and all Power Platform environments within are in the "European Union (EU) and European Free Trade Association (EFTA)" Macro Region Geography, and you maintain a billing address in an EU Data Boundary country.
The Europe and United Kingdom (UK) and Europe, UK, Middle East, Africa geographies aren't part of the EU Data Boundary.
The maker's profile resolves to the EU or EFTA:
- If Multi-geo customer and Preferred Data Location holds a valid three-letter PDL value that references an EU or EFTA country.
- If Country or region holds a two-letter value, it must be the code of an EU or EFTA country. The tenant's country or region is ignored in this case.
- If Country or region is empty or isn't a two-letter value, the tenant's country or region must be in the EU or EFTA.
Check and update settings
The following table shows where administrators check or change each setting.
| Setting | How to check or change it |
|---|---|
| Preferred data location (Multi-Geo tenants only) | Cloud-only users: use Microsoft Graph PowerShell. To verify, in the Microsoft 365 admin center, select Users > Active users, select the user, and then select Account. Users synced from on-premises Active Directory: set the value in Active Directory and sync it with Microsoft Entra Connect. |
User's country or region (country) |
Cloud-only users: in the Microsoft Entra admin center, select Entra ID > Users, select the user, select Edit properties > Contact information, and then set Country or region. You can also use Microsoft Graph PowerShell. Users synced from on-premises Active Directory: set the country attribute in Active Directory and let it sync. Always use the correct two-letter country code. |
| Tenant's country or region | In the Microsoft 365 admin center, select Settings > Org settings > Organization profile. |
| Environment geography | In the Power Platform admin center, select Manage > Environments, and then check the Region column. |
Set a user's preferred data location with PowerShell
Connect-MgGraph -Scopes "User.ReadWrite.All"
Update-MgUser -UserId "<user UPN>" -PreferredDataLocation "<geo code>"
Set a user's Country or region with PowerShell
Connect-MgGraph -Scopes "User.ReadWrite.All"
Update-MgUser -UserId "<user UPN>" -Country "FR"
Review makers' Country or region values
Connect-MgGraph -Scopes "User.Read.All"
Get-MgUser -All -Property UserPrincipalName,Country |
Select-Object UserPrincipalName,Country
Check each maker for:
- Incorrect codes, which override the tenant's country or region.
- Unrecognized codes, which stop app building.
- Empty or non-two-letter values, which fall back to the tenant's country or region.
Note
If your organization uses custom claims mapping for the ctry claim, check with your identity team before relying on the guidance in this article.
Related information
- Optional claims reference
- What is the EU Data Boundary?
- EU Data Boundary for Microsoft 365
- Microsoft 365 Multi-Geo availability
- Choose the right Microsoft 365 Data Residency solution
- User testing in Multi-Geo
- Microsoft Entra Connect Sync: Configure preferred data location for Microsoft 365 resources
- Add or update a user's profile information and settings in the Microsoft Entra admin center
- Update-MgUser
- Choose the region when setting up an environment
- Power Platform and Dynamics 365 macro region geography