PowerApps-based applications offer robust business logic and workflow features to convert your manual business processes into digital, automated ones. However, transferring ownership of an app in PowerApps is quite tricky and cannot be done natively without a standard transfer ownership method. In this blog, I will provide steps to transfer ownership of an app in PowerApps.
To transfer the ownership of an app in PowerApps, you need to locate and copy the app’s environmental ID and object ID in the app’s Detail section. Then, go into the Azure Active Directory Profile section and locate the user profile and object ID. Once you have found this information, go into Power Automate. Then, you can create a flow that automatically transfers the ownership of an app made in PowerApps to another user.
- Look up Environment/app ID information for an app in PowerApps.
- How to source user profile ID information in Azure Active Directory.
- How to create a Power Automate flow to automatically transfer ownership of an app made in PowerApps.
Here are the steps to automatically transfer the ownership of an app made in PowerApps. Each section shown here is essential for you to create the flow required to transfer ownership of the app. So please make sure you progress through each one to transfer ownership of an app.
PSST, HEY, YOU
Want in on insightful videos, the latest tech developments, and epic exclusive content? Get all this and more as a member of our mailing list.
How to lookup Environment/app ID information for an app in PowerApps
Below, you can look up the ID information for an app you have made in PowerApps. You can find this information in the detail section of an app you have made; it is the path or code of the app which is used to help identify the application itself.
Locate the environment ID
- Firstly, open the PowerApps application in Office 365.
- Now click on the option for “Settings.”
- From there, select the option for “Developer resources.”
- Here you can find the Environment ID to complete the process.
Once you have completed the steps above, you will need to record the information for use in the next steps. Your Environment ID is your primary user ID for the PowerApps application. And you will be able to link any application in the PowerApps program to your profile using the Environment ID. The Environment ID is necessary for the power automated flow we will create later.
Locate the app ID
Now that you have your environment ID, you can find the app ID in the Detail section of your application. The app ID is your primary ID for the app you have created.
Power Automate will use your app ID with the environment ID and user profile ID to generate a flow that automatically transfers the application to that user without you having to carry out extensive processes.
- Firstly, in the PowerApps application, click on “Apps.”
- Choose one of the apps and then connect the three dots next to it.
- Click on the option for “Details.”
- Locate the app ID and copy it to complete the process.
Once you have completed the steps, you will have managed to source the app ID and then copy it for the proceeding steps. Keep this information secure as you need it for the Power Automate flow similar to the environment ID.
How to source user profile ID information in Azure Active Directory
Now that you have all your information from the PowerApps application section, you need to source the information of the new user to who you want to transfer the app. The latest user could be a new colleague or the employer who wishes to attain the application information for referencing reasons.
You can use Azure Active Directory to find all user information, including object and user IDs.
- Firstly, click on the launcher and then click on “Admin” in Office 365.
- from the list of Admin centers, select “Azure Active Directory.”
- From the identity section, select “Users.”
- Select the user you want to transfer the app to.
- Locate and copy the Object ID to complete the process.
Power Automate will use the object ID to locate where the application will need to be transferred.
How to create a Power Automate flow to automatically transfer ownership of an app made in PowerApps
The final step of the process is to create the Power Automate flow that will allow you to transfer the application to the new user. Once you have sourced all the information from the application ID to the user profile ID, you can proceed with the steps ahead.
Unfortunately, there is no other way of transferring the application to a new user from your current user account. So, if the application is still on the old user account and you need to transfer into the new account, you will need to use a Power Automate flow to move the application to the new user.
- In Office 365, use the launcher to locate the Power Automate application.
- From the list of options, click on “Create.”
- Choose the option for “Instant cloud flow.”
- Click on “Manually trigger a flow” and click on “Create.”
- From the list of actions, select “Set App Owners.”
- Fill in the flow information.
- Where do the different IDs go?
- The environment name is the Environment ID you sourced earlier.
- The App ID will go into the section called “PowerApp name.”
- The section where the user object ID will go is the “New PowerApp owner” section.
- Click on “Save” to run the flow and complete the process.
Once you have completed the steps, you will create a flow using the information you have sourced from the app ID to the user’s profile ID. Once the flow begins, Power Automate will transfer the application to the new user.
As illustrated in the post, there is no way to use native functions within the PowerApps program to move an app to a new user. So if you have a user who has left the organization, you will need to use the Power Automate application to move the app to a new user. Once the user leaves, you must make sure that you quickly address the situation of an app being on their account and move as soon as possible to prevent a data breach.
The process is irreversible, and you must make sure that you are aware that the application will be assigned to the user permanently. If there are any issues you come across following the steps, drop a comment below, and we will address them.