[CoE Starter Kit - Feature]: Migration Assistant

[Grant-Archibald-MS]

Is your feature request related to a problem? Please describe.

Today there is guidance on Migrating from the default.

Depending if the resources like applications and flows are included within solutions provides a range of choice on how best to migrate the resource to a new environment.

Creating Process

This guidance requires administrators to setup a process combining elements of DLP Policy, inventory and usage date to identify makers who should migrate. Combine with features like Integrated Environment Request or the existing Environment Request of the Coe Starter Kit to create a environment to move the components as part of an environment strategy.

For example this process could like the following:

Analysis

Adding to this process the maker or the new assigned owner of the application needs to classify the application into one of the following use cases to determine what migration work if any should taken.

Migration

Given this analyzed data this then may present a range of options where owner or the creator self migrated, gets assisted migrated or works with the CoE team to migrate the resources

Describe the solution you'd like

Provide tooling that supports this process by:

• Creating a process to use inventory and usage information to create targeted communications to owners of Power Platform resources to move from default or share environments
• Provide the ability to analyze and classify the resources for migration
• Provide tooling that assists with migration from a default or shared environment to a new managed environment
• Assist with automation of tasks to reduce the manual work to migrate resources between environments

Describe alternatives you've considered

No response

Additional context?

No response

AB#2620

[Grant-Archibald-MS]

Consider if the Migration assist should be part of the Innovation Center joining Learning Path, Ideas, Environment Request and Environments so that when users select default or shared environments thay are offered the ability to open the migration assistant to help them move to another environment

[Grant-Archibald-MS]

Factors to consider:

1. Applications and flows may not be solution aware
2. Cloud flows that are not solution aware will need to be added to solution first so that they can be exported between environments
3. Dataverse may not be available in the source environment
4. The maker may not have Automation Tools installed to streamline the process and may need assistance in setup of automation tools
5. Access to Power Automate Management and Power Apps for Admins connectors may be restricted by DLP and as a result alternative means of collecting user level Apps and Flows provided as part of the process
6. Series of steps that could be considered for process

• Admin send email notifying Maker that they need to migrate existing application / flows
• Maker opens the Migration Assistant
• Watch a video on the Migration Process
• See a list of Apps and Flows in the environment that they could migrate
• User selects an app or flow to migrate
• Migration wizard that:
  • Scans the application or Flow
  • Shows Dependencies – Controls, Components …
  • Show Connections
  • Select Development Environment to Move to or Request new Environment
  • User creates connections
  • Perform Migration of importing components
  • Create new solution
• Clean Up the apps, flows, connections

[Grant-Archibald-MS]

The following automation items already exist

Power Shell

• Set-PowerAppAsSolutionAware -EnvironmentName {Environment ID} -AppName {App ID} -SolutionId {Solution ID}
• Set-FlowAsSolutionAware -EnvironmentName {Environment ID} -FlowName {Flow ID} - SolutionId {Solution ID}

pac cli

• pac canvas download to get the msapp

Microsoft 365 CLI

• flow export - CLI for Microsoft 365 (pnp.github.io)