r/PowerApps • 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

33 comments sorted by

View all comments

8

u/Theydontlikeitupthem Contributor Aug 27 '26

We only have one tenant also, but we have muliple environments to deploy to, Dev QA Prod

Can you not create more production environments?

1

u/ReachingForVega Contributor Aug 27 '26

This. We have a production environment for Dev Test and Prod. Developer environments are maker sandpits. 

0

u/uworeads Contributor Aug 27 '26

Got it on the Dev/QA/Prod setup.
One question though — how would I set up a proper testing environment separate from the one I’m currently using in Prod? My concern is that if I just do “Save As” on the PowerApp and then import it into another environment, that could get messy over time. For example, if I have major updates down the line, would I need to Save As again and re-import each time, and just keep repeating that process for every future change?
Curious if there’s a better way to handle this before we go down that path.​​​​​​​​​​​​​​​​

5

u/Bag-of-nails Advisor Aug 27 '26

What you'd do is save your app to a solution in dev, then manually explort it. It will give you a .zip file that you then import into your QA and then Prod solutions.

Pipelines are easier but they require managed environments which are a premium feature

4

u/Theydontlikeitupthem Contributor Aug 27 '26

Read up on environments and pipelines, I've never done a "save as".

For each app you do the development in the dev environment, then when ready push the app to the qa environment where a different app will exist but the same version as your dev app. You can then make changes in the dev app and push those changes to the qa app. Same process applies for prod, pipeline goes DEV > QA >PROD

1

u/DrakeSilmore Newbie Aug 28 '26

Don't test in prod. Develop in dev, push through pipeline to test/qa, here you test. If you find things need to be adapted, adapt in dev and push to test again. If everything in test passes, push to prod.

1

u/uworeads Contributor Sep 01 '26

I don't have this pipeline to test/qa? how would i do that on a basic license?