Solution for migrating Canvas Apps and their related resources like Flows between environments. Solution includes simple Canvas App with supporting Cloud Flows and Custom Connector to do the migration. This migration automates Power Platform legacy export/import functionality.

As this sollution uses Custom Connector, all the users need to have standalone Power Apps license Power Apps Premium or Power Apps per App

Solution uses Power Platform BAP API to export and import packages, so we need to create Microsoft Entra ID application registration for the user authentication. Follow the steps below to register new Entra ID application. Depending of your tenant settings, you might need Global Administrator permissions to be able to register new application.

1. Open the application blade in Microsoft Entra portal Entra ID App Registrations

2. Click New registration

   

3. Provide a name for the app and click Register

   

4. Copy Application (client) ID and Directory (tenant) ID from the Overview page to notepad for example

   

5. Browse to Certificates & Secrets blade anc click + New client secret

   

6. Define description for the secret and select expiration time

   

7. Copy client secret value to notepad

   

8. Browse to API permissions blade and click + Add a permission

   

9. Select APIs my organization uses, then search for PowerApps and select PowerApps Service

   

10. Select Delegated permissions, then select User permission and click Add permissions

    

11. (optional) Grant admin consent for the application. If you do not do this then all users need to grant consent in the first use of the Canvas App migration tool

    

This Power Platform solution installs Custom Connector

1. Open the environment to where you want to install the solution

2. Select Solutions from the menu and click Import solution

   

3. Click Browse and select the MigrateCanvasAppsPrerequisites_x_x_x_x_managed.zip solution then click Next

   

4. Fill-in Client ID and Tenant ID you copied to notepad and click Import. NOTE! Current version support now only plaintext client secret which need to be set after solution import

   

5. After solution is imported, select Custom Connectors from the menu and click the pencil icon of the Migrate Canvas Apps custom connector to open it in edit mode

   

7. Select 2. Security and click Edit

   

8. Copy-paste the Client Secret and click Update connector

   

9. When connector is updated, scroll down to bottom of the page and copy Redirect URL

   

10. Move back to Entra ID application registration we did in the first step and in the Overview page click Add Redirect URI

    

11. Click +Add a platform

12. Select Web

    

13. Paste URL to the Redirect URIs field and click Configure

    

14. Go back to custom connector configuration, select 5. Test and click

    

15. Create new connection by cliking Create and login with your account

    

16. (optional) You can test the connector by defining EnvironmentID and use the following body with your own application ID which you can find from the Canvas App details page. If you get response 200 and can see the application details in the response body, then custom connector is configured correctly

    {
       "baseResourceIds": [
          "/providers/Microsoft.PowerApps/apps/REPLACE-WITH-YOUR-APPID"
       ]
    }
    

    

1. Browse to Solutions of the environment and click Import solution

   

2. Click Browse and select the MigrateCanvasApps_x_x_x_x_managed.zip solution then click Next

   

3. Verify that all the connection are created. If not then click three dots next to connector to create new connection

   

4. Solution import takes couple minutes

• App migration status is saved to Migration Job Dataverse table and users need to have read-write permissions to this table. Solution contains own security role Canvas Apps Migration Users which grant Create, Read and Write permissions to the table, so add this security role to app app users

• You might need to share also grant run-only user permissions to all solution flows.

  Select user(s) or group(s) and define Provided by run-only user for all the connections of the flow

  
  

1. Run the Migrate Canvas Apps app

   

2. Consent all connection by clicking Allow

   

3. Select source environment

   

4. Select the app you want to migrate. This will run GetPacjageResources flow to fetch all related resources of the app like flows and connections

   

5. Select target environment

   

6. If there are flows included in the app having any connections, then you need to create all the connections before migration.

   You can create new connection(s) or select existing connection(s). Connection creation opens to new browser tab for target environment. If you want to create all connections click Create All which opens own browser tab for each connection.

   

   NOTE! Browser pop-up blocker might block opening new browser tab. If that is the case then one option is to open target environment in make.powerapps.com and manually create connections

8. After connections are created, click Refresh to fetch connections. You can still select connection you want using the dropdown control if there are multiple connections

   

9. Click Migrate to start the app migration. It takes few minutes depending how many related resources there are in the app

   

11. If migration was succefull then click Next Step to move to the next step of the process

    

11. Select the migrated app from the list. If the app is not listed then click refresh icon to fetch your apps from target environment.

    NOTE! sometimes it can take little while for the migrated app to be visible here

    

12. Now you should see all the permissions (if any) of the app in source environment. You can remove permissions if needed or do not share the app in target environment at all. Make the necessary changes and click Share App or click Next Step if you do not want to share the app for now

    

    If you shared the app then when sharing is completed you should see the green success icon for each permission like below

    

13. In this step you have following options

    • Rename app in source environment by appending "(MIGRATED)" to the end of the app display name

    • Remove all the other permissions except your own

    • Remove the old version from source environment

      
      

14. In last step you can send an email notification to all the users and groups about the migration (group members are not extracted, so email is send to group address). Email contains app link to the new app in target environment