Move a solution from DEV to TEST then PROD : Best pratices

(0) Share

Report

Posted on by ALP2

242

Hi the community,

i need your help about environment strategy.

I have 3 environments :

* Shared DEV environnement type Sandbox - They DeV groupe is environment makers

* TEST environment type production - Microsoft documentation says " Devloppers have environment makers access in the dev environment but only user accesss in test and prod" Establishing an Environment Strategy for Microsoft Power Platform | Microsoft Power Apps

My 1st question is : Who push the solution from DEV environment to TEST Environnment. A service account who has the security role "system administrator" on these environnement ?if i use a service account who has a licence per user for automate and apps, i can use his credentials for connectors instead.

My 2nd queston : What role do you assign to your dev in the TEST environment ? If i assign the role basic user, they can't see their solution ? How can i test my apps and flows ? The workaround is that i share the flow and the apps to the dev users from my service account. Not a best practice i presume.

Thanks for your help

Categories:

Governance & administering

All responses (2)

Answers (1)

Sort by

Verified answer

ChrisPiasecki 6,428 Most Valuable Professional on at

Like
a
(2)

Report
Copy link

Link copied!

Hi @ALP2,

Depends on what type of testing needs to be done and who is testing. If it's a system test environment where your devs and QA analysts perform the testing, then your devs probably will require system admin in order to deploy and troubleshoot.

When it comes to supporting these solutions in a UAT or Production environment, to be effective you often will still need access to the data but shouldn't have access to change components or deploy directly.

We often create a custom security role called "Application Support" which will have access to all the custom tables and other business data. But only read privileges on most of the Customization tab such as Entity, View, Model Driven App, etc, no import customizations, no audit log deletion, etc.

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.
ALP2 242 on at

Like
a
(0)

Report
Copy link

Link copied!

hi, thanks for the very clear explanation. Create a custom role application support is a good idea. I wiil keep it in mind