You’re offline. This is a read only version of the page.
Hello, I'm trying to define an environment strategy and would appreciate help on suggestions.
Right now I am leaning toward having a dev-test-prod for each geo location instead of creating environments for each department, that is a lot to maintain. My plan is also to deploy via power pipelines and using a service principal, is this recommended? I still would like users to have access to prod to monitor how their solutions are working, for this they would just need basic user access right?
I would try to answer below questions before you approach what needs to done.
Current State
1) Who is developing solutions? where are they located (state/country)?
2) How many applications were built using Power Platform? This includes all Power Platform components (Apps/flows/solutions/bots etc).
3) What type of data sources are the people connecting to?
4) To find the current state, you can install starter kit and learn about the ecosystem.
Environment Strategy
5) Who should create environments? Is it Automated?
6) Who will manage the environments?
7) Does the data need to be segregated by region or department levels?
😎 Do you have Admin training for business users who is responsible manage the environments?
9) Is there any process for migrating the most commonly used solutions from the default environment?
10) Do you allow Dataverse to be added for every environment or only a few environments?
11) What are the criteria for creating environments using Dataverse?
The answers would vary depends on number of users, location of the users etc.
I am leaning toward having a dev-test-prod for each geo location instead of creating environments for each department,
This depends on who manages the environments.
Are you going to allow citizen developers to manage the envs?
It seems you wanted to manage everything? If yes, its not a bad strategy.
What happens if you wanted to develop business critical applications, Highly confidential data and Global apps?
In this case you might dedicated dev-test-prod environments.
Also, you need to think of using data gateways if you are connecting to on-premises data sources.
My plan is also to deploy via power pipelines and using a service principal, is this recommended?
Yes, you can do that.
You can also use Power Platform pipeline. Though it needs managed environments.
Below decision tree should help you to decide which one is a better tool.
I still would like users to have access to prod to monitor how their solutions are working, for this they would just need basic user access right?
So you want end users to Monitor the solutions health.
I wouldn't do this in Prod, if you still need it then i would use APP Insights in Azure and manage it that way.
Also create guidelines on exception handling for apps/flows and maintain the solutions that way.
Again, you need to approach this based on Business Impact, data classification and Number of people using the apps(Personal, department wide, local or Global).
Hope that helps.
====================================================
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/
Share
Report
77
All responses (
Answers (
