This article provides information about transferring your Power Apps and Automate solutions to the nhs.net environment and the steps that you will need to take.
Power Apps and Automate Transition Overview
As part of the transition to the nhs.net environment, there are actions you need to complete if you have any Power Apps (applications) or Automate (flows) hosted in your legacy environment that you would like to use after the transition.
Power Apps and Automate Flows will not be automatically transferred to the nhs.net. Therefore, it is important to complete the self-transfer steps to nhs.net for apps and flows you need, as some of the data sources (M365) will become read-only in the legacy environment and your app/flow will no longer work.
The steps below shows the key checkpoints for your Power Apps and Automate self-transfer journey. This page contains more information about each of these checkpoints:
- Determine apps and flows you want to transfer to nhs.net
- Understand and record apps and flows components (connections, custom connectors, gateways and tables)
- Check for nhs.net settings
- Export Power Apps applications, Power Automate flows and any Custom Dataverse tables from the legacy environment
- Import Power Apps applications, Power Automate flows and any Custom Dataverse tables into the nhs.net environment
- Post import activities: utilising App & Flow checkers and reconnecting data sources