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.
The EU (European Union) Data Boundary is a geographically defined boundary within which Microsoft committed to store and process customer data and personal data for Microsoft online services including Power Automate.
Power Automate temporarily transfers some pseudonymized personal data from the EU for certain Power Automate cloud flows created before November 2024. Prior to this date, cloud flows created outside of solutions were created in per-user resource groups with resource group names containing the user's object ID being globally replicated. Customers can ensure that pseudonymized personal data resides within the EU Data Boundary for these flows through the use of a migration tool available to Power Platform administrators. This article details the use of this tool.
Prerequisites
- Power Platform administrator access for the environments you wish to check or migrate
- Permissions to run PowerShell as an administrator
- Install and use the Power Platform Administrator PowerShell module for access to the
Get-AdminFlow,Start-EUDBMigration,Cancel-EUDBMigration, andGet-EUDBMigrationStatusPowerShell cmdlets
Plan for migration
To identity which flows need to be migrated and from which environments, run the Get-AdminFlow cmdlet with the flag IncludeEUDBNonCompliantFlows. This command lists all the flows in need of migration from the environments that you have Power Platform administrator permissions.
List flows from across all environments
Get-AdminFlow -IncludeEUDBNonCompliantFlows $true
List flows from a specific environment
Get-AdminFlow -EnvironmentName 00aa00aa-bb11-cc22-dd33-44ee44ee44ee -IncludeEUDBNonCompliantFlows $true
Perform the migration
Once you identify which environments contain flows that need to be migrated, you can proceed to migrate them either individually or environment-by-environment using the Start-EUDBMigration cmdlet. After starting the migration, save the Operation ID that is returned. You can use this with the Get-EUDBMigrationStatus cmdlet to check whether the migration is complete or is still in progress.
During migration
- Users are briefly unable to access, turn on or off, or save cloud flows while they're being migrated, while this error displays: Flow '[...]' is currently undergoing system maintenance. Please try the operation later.
- New runs of instant (manually triggered) cloud flows can't be started.
- Automated and scheduled cloud flows continue to run uninterrupted.
For instant flows that are frequently run, we recommend migrating them individually during off-hours. When performed on the environment level, migration occurs on a rolling basis during off-hours to minimize disruption, based on the Power Platform region of the environment. Environments with thousands of cloud flows might take up to two weeks to completely migrate. Migration doesn't require any action from flow owners, or cause changes to flow definitions or connections.
Example: Starting the migration of all the non-compliant flows in the environment 00aa00aa-bb11-cc22-dd33-44ee44ee44ee
Start-EUDBMigration -EnvironmentName 00aa00aa-bb11-cc22-dd33-44ee44ee44ee
Example: Starting the migration for several specific flows
Start-EUDBMigration -EnvironmentName 00aa00aa-bb11-cc22-dd33-44ee44ee44ee -FlowNames 00001111-aaaa-2222-bbbb-3333cccc4444,11112222-bbbb-3333-cccc-4444dddd5555,22223333-cccc-4444-dddd-5555eeee6666