Power Platform Architecture help

[yohannes_adeba]

Hello.

I'm working as a consultant for Recruitment related data in an organization that has a license for office 365. To make improvements I've designed a SharePoint list that records all recruitment attributes and shared the board view of it with recruiters so they update their specific cards. Also I used different manual and scheduled PowerAutomate Flows that link with this List. In addition, I have got a PowerApps and Power-BI application that uses this list as a source. This is working well until now for the past one-plus years.

Now the case is here.

there is another ongoing Project(outsourced) that has a mission to automate all HR activities including recruitment which I already have worked on. The project uses Azure for its cloud computing.

1. Assume that the application I made using SharePoint-list, PowerAutomate, PowerApps, and PowerBI is good; To avoid duplication of development, can all components I used(SharePoint-list, BI, flow, PowerApps) be transferred to the Project team and let the APP continue working from that without interruption?

The goal of this is to avoid dependency on me since all are in my Microsoft account and reduce the consequences of me leaving the company or being unavailable. 

2. Assume my app needs improvement and the project must develop another application, Can the project (developers in the project )create a backup of my application on their cloud system so it can be used when needed? 

3. What are the recommendations for Apps(built using different tools) that are linked to single users but are very important for the organization? How do we solve issues that might arise with the resignation/unavailability of the system developer?

Thank you for the usual support.

[Pstork1 · Accepted solution]

1) The Power Platform doesn't run in Azure, but it is available from the cloud. So there isn't really any way to "Transfer the components to the Project". Assuming the people working the project are in the same Azure AD as the SharePoint tenant and that they have Office or Power App licenses you can make them co-owners of the app, etc., which will basically do the same thing.

2) If they are co-owners they can edit the app themselves or save a copy and edit that copy.  But again, there is no creating a backup of your app on their cloud system.

3) The common best practice to keep apps running when a user leaves the company is to build the app using a "Service Account". That account being an account created specifically for creating Power Platform apps.  The account is just a regular account with a license.  But it would be one that would never be disabled or deleted when a person leaves.

[yohannes_adeba]

Thank you so much for the swift response. This is very clear and well-noted. I think the 3rd option is the best in my case.