web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Automate
Unanswered

Environment strategy

(0) ShareShare
ReportReport
Posted on by 11
My organization is just starting to roll out use of Power Platform. As we do that, we are starting to implement governance around the platform.
 
We are debating on the right number of environments for users (beyond CoE toolkit, platform feature testing, etc.):

On one hand: Default for personal productivity and one production environment for shared.
 
On the other hand: Default for personal productivity and an environment per business unit for sharing.
 
The first option seems simpler and easier, but we’ve not worked with a platform like this before and worry there will be a lot of overhead required by our centralized team.
 
The second option feels like it can get away from us just as easily, but would give us more options for distributing responsibilities to BUs and make “charge back” much simpler (as our cost center is currently stuck with all the expense).
 
What do we need to take into consideration to make this call? Are there any suggestions from the community?
Categories:
I have the same question (0)
  • Verified answer
    ankit_singhal Profile Picture
    590 Super User 2025 Season 2 on at
    Hi,

    As per the process we should have 4 environments. One for development, second for system testing done by QA, 3 for UAT (business testing) and last one production. We have one more Pre deployment where we test all the deployment steps before the production. 
    this process will give you confidence before the production release and we followed CI.CD pipeline approach for the deployment.
     
     
    Note: Please mark verified, if it is useful for you  
  • Mitchell GC Profile Picture
    11 on at
    Ankit,
     
    That aligns with our standard SDLC approach. Thank you!
     
    What kind of overhead does this introduce to the platform support team? How do you mitigate them from becoming a bottleneck for innovation using the platform?
     
    For more context, we have an enterprise license and about a thousand people. Our desired target for active usage a year from now is about a hundred individuals. Our platform admin support group is only 5 people.
  • Mitchell GC Profile Picture
    11 on at
    Ankit,
     
    I'm sorry for the instant follow-up, but I forgot to ask for clarification! 
     
    For the development environment, are you talking about a "Production" type environment that is explicitly used for development work, or "Development" type environment(s)? 
  • ankit_singhal Profile Picture
    590 Super User 2025 Season 2 on at
    Hi ,
     
    We have non prod environment (development env) as Sandbox and only one environment is production. Also, you can deploy your solution in same way on SIT, UAT and production. There is no change in deployment using CI/CD, 

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 522 Super User 2025 Season 2

#2
Tomac Profile Picture

Tomac 364 Moderator

#3
abm abm Profile Picture

abm abm 243 Most Valuable Professional

Last 30 days Overall leaderboard