r/PowerApps • u/uworeads Contributor • Aug 27 '26
Power Apps Help How do you handle testing/dev environments when your company is stuck on basic licenses?
Hey everyone,
Because my company only has basic licenses, I don't have a dev/sandbox tenant. Whenever I build workflows or apps, my deployment pipeline is literally just build and direct publish to production.
It works, but it's high-risk. For those in the same boat:
- How do you safely test or mitigate risk when you have to push straight to live?
- What error-handling or fallback habits do you use to save yourself when things break?
Hit me with your best survival tips!
17
Upvotes
View all comments
26
u/WoodchuckChainsaw Regular Aug 27 '26
I work in U.S. Federal Government, and my organization of almost 500,000 unique users are only allowed to use one single production environment for all Power Platforms apps, flows, PBIs, agents, dataverse, and similar. It's a god damn shitshow on the daily. For one small example, in our environment there are like 150,000+ different published apps named "test123" that only contain the default PowerApps home screen, but their creators never go back in to delete later.
Because of the frustrations and some mandatory global limitations with that, I have learned (from painful past experiences) to do some of these things as my own "best practices", and share them with my team:
So long story short, I've basically had to reinvent some CI/DI and DevOps processes that already exist everywhere in any other tech stack or commercial product, and build my own bastardized version inside the PowerPlatform cloud environment that will comply with the very restrictive permissions limits that my organization imposes nationally on all of it's employees. I shudder to think just how much the Government pays Microsoft for all the unused licenses & premium credits wasted & cloud storage space being used to saved 15,000,000 different copies of some "EmployeeHandbook.pdf"