Best Practice guidance: 1 solution with multiple business units / departments with ALM

(0) Share

Report

Posted on by aaroh_bits

416

Hi All,

The client is on E5 and E3 licenses.
All Standard Connectors
They will be having at least 25 apps/flow ranging from Operations, Facilities, Sales, Marketing, Security, IT, etc as per their demand.
Each department has its unique own app and flows.
Question 1: What should be the best practice when it comes to Solutions when you have multiple apps/flows?
apps and flows for departments / Business Units. This article does not give clarity on that. https://learn.microsoft.com/en-us/power-platform/alm/solution-concepts-alm
Question 2: Do I create 1 solution = 1 department / Business Unit which will have its own security roles and permissions?
The challenge is each department will have its own apps and flows. So managing multiple apps will be a challenge.

OR

should I create multiple business units/departments within a single solution as follows?

Please share your valuable inputs

@ChrisPiasecki , @iAm_ManCat , @AlbertoCastro , @Pstork1 @ANB

Categories:

Governance & administering

I have the same question (0)

All responses (3)

Answers (1)

AlbertoCastro 1,201 Most Valuable Professional on at

Like (0)

Report

Hi,
the concept of Business Units is to apply security to level data in Dataverse, not to organize the solutions. In your case, I think that the best option could be to have one environment by each department
-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Regards
Alberto

Was this reply helpful? Yes No
Verified answer

Pstork1 68,707 Most Valuable Professional on at

Like (2)

Report

As @AlbertoCastro said, Solutions are not used for security. Apps still need to be shared and the data source permissions still need to be assigned. Dataverse is the only DB that uses business units to assign roles for security. Since they are using standard connectors it doesn't apply.

The best practice is to have related Apps/flows in the same Solution. Unrelated apps/flows can be in the same Solution if that makes deployment easier, but its not required. So if a department has its own set of apps and flows that aren't used by other departments then put them in the same solution. If multiple departments use the same apps/flows then group them together in a solution. There is no one best way to organize. The one rule would be to keep related apps/flows together so they can be deployed together along with environment variables and connection references, etc.

Was this reply helpful? Yes No
aaroh_bits 416 on at

Like (0)

Report

Thanks a lot @AlbertoCastro and @Pstork1 for valuable insights,

Was this reply helpful? Yes No