Drag and Drop Question A company is migrating to a new Microsoft 365 tenant. You create an expense management canvas app and cloud flow in the old Microsoft 365 tenant. You need to move the latest…

The correct answer is Export the app as a package.; Import the app.; Share the app with a user in the new tenant. To migrate the latest version of a Power Apps canvas app and cloud flow between Microsoft 365 tenants, you must first publish all changes, then export the app as a package, and finally import the package into the new tenant.

Design and manage business solutions

Question

Drag and Drop Question A company is migrating to a new Microsoft 365 tenant. You create an expense management canvas app and cloud flow in the old Microsoft 365 tenant. You need to move the latest version of the canvas app and cloud flow to the new tenant. Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order. Answer:

Exhibit

Answer Area

Drag items

Export the app as a package.Create a copy of the app in the cloud.Import the app.Share the app with a user in the new tenant.

Correct arrangement

Export the app as a package.
Import the app.
Share the app with a user in the new tenant.

Explanation

To migrate the latest version of a Power Apps canvas app and cloud flow between Microsoft 365 tenants, you must first publish all changes, then export the app as a package, and finally import the package into the new tenant.

Approach. The scenario requires moving the latest version of a canvas app and cloud flow to a new tenant. This implies a cross-tenant migration process. The correct sequence of actions for this is:

Publish all changes. - Before exporting, it's crucial to ensure that all recent modifications to the canvas app and cloud flow are saved and published. This guarantees that the 'latest version' requirement is met and that the exported package contains all desired changes.
Export the app as a package. - To move an app and its associated components (like cloud flows) between tenants or environments, they must be exported as a deployable package (a .zip file, often referred to as a solution package in the Power Platform context, though Power Apps can be exported directly). This package bundles all necessary components.
Import the app. - Once the package is exported from the source tenant, it can be downloaded and then uploaded and imported into the target tenant. This action deploys the app and its associated flows into the new environment. This sequence ensures the complete and up-to-date migration of the app and flow.

Common mistakes.

common_mistake. -"Create a copy of the app in the cloud." is incorrect because this action creates a duplicate of the app within the same tenant or environment, not for cross-tenant migration. It doesn't generate a portable package. -"Share the app with a user in the new tenant." is incorrect because sharing an app grants access to users within an existing environment where the app is already deployed. You cannot directly share an app across different tenants as a method of migration; the app itself must first be moved and deployed in the new tenant. -Exporting before publishing would be a mistake because it might not include the very latest changes, failing the requirement to move the 'latest version'. -Importing before exporting is impossible as there would be no package to import.

Concept tested. Power Apps and Power Automate application lifecycle management (ALM), specifically the process of migrating canvas apps and cloud flows between different Microsoft 365 tenants or environments using export and import functionalities, and understanding the importance of publishing changes for version control.

Topics

#Power Apps#Power Automate#Solution Management#ALM#Tenant Migration

Community Discussion

No community discussion yet for this question.

Full PL-100 Practice