Answered

Center of Excellence (CoE) Push or Import to Production Environment

(0) Share

Report

Posted on by R1449A

If core components are working and I've made modifications to the CoE in the Test Environment, is the best practice to push to Production via pipeline, or to Import the components and redo the modifications from scratch? Also, can I use the same Admin, Maker, and User M365 Groups, and the same Service Account between Test and Production environments?

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,
I think that there is not a universal answer about this. It will depend that the customization that you have made, the tool that your organization uses to deploy solutions, etc
All are valids: pipeline, alm aceleratos, devops, github, include manually.

By other side, if in your test environment you have the variable production = no, you can re-use the groups.
-------------------------------------------------------------------------
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
velegandla 204 Moderator on at

Like (0)

Report

@R1449A

Make sure you follow the guidelines about the customizations guidelines
https://learn.microsoft.com/en-us/power-platform/guidance/coe/modify-components

We use Power Platform pipelines to deploy the customizations. Power Platform needs managed environments. You can use other options such as ADO or export/import managed solutions manually.

Follow the recommendations here for Variables
https://learn.microsoft.com/en-us/power-platform/guidance/coe/setup-core-components#all-environment-variables

Yes, you can use the same service account..
Make sure, you don't do full inventory every time in development environment. If you Tenant is big then you will hit throttling limits.

Exclude the environments from inventory that doesn't need.

====================================================

If this response helped you in any way, please give kudos by clicking the 'Thumbs Up'/'Like' button and/or marking it as an 'Accepted Solution'. This helps others by providing a quick way to identify likely solutions to their issues.

https://www.linkedin.com/in/devendravelegandla/

Was this reply helpful? Yes No
Verified answer

EricRegnier 8,720 Most Valuable Professional on at

Like (0)

Report
Hi @R1449A,

To answer your specific questions:

"If core components are working and I've made modifications to the CoE in the Test Environment, is the best practice to push to Production via pipeline"? No, best practices states to perform changes in a Dev environment, then push those in a new managed solution to the Test and then to Prod (same managed solution). Using a pipeline is best (Azure DevOps, GitHub, or Power Platform Pipelines).

"Import the components and redo the modifications from scratch"? If you mean to re-import the modifications into a Dev environment in an unamanaged solution or redo from scratch in a Dev environment, then redeploy to Test/Prod as managed (as stated in point #1), then yes, this is best.

"Can I use the same Admin, Maker, and User M365 Groups"? Yes, this groups/teams/roles will exists in every environment

"The same Service Account between Test and Production environments"? Technically yes, but best practices states here that its best to use separate account for security reasons and regression reasons. Also best practice is to use service principals. E.g.

You need to make changes to that account and test it without impacting prod.

Or you developers that shouldn't have access to prod but need these account access in dev/test. Everyone who has access to the account credentials will gain access to prod.

Hope this helps!

Was this reply helpful? Yes No