Power Platform Community Forum Thread Details

Hi All, I've been developing on the power platform for my company for quite a while now, I have legacy apps deployed on the default environment that were built before solutions were even a thing, this has had the unfortunate effect of us keeping production apps on the default environment, although in solutions with everything set up as best practice i.e. connection references, environment variables etc.

As part of our ongoing ALM strategy, I'm currently looking at moving any unmanaged solutions off the default environment onto a dev and then production as managed solutions, I'm pretty much there with everything in terms of having everything in solutions separated ready to export, and these are all solutions that the apps use SharePoint as the data source so I'm not having to worry about dataverse tables and dependencies, gladly we developed anything using the dataverse in their own environments.

I say all that to say, there's one thing that's stopping me, most business processes in the solutions use teams approvals generated from flow. When an end user comes to approve, the default selected environment in teams approvals is always your Default environment which is currently great, everything is in one place. But, if you move a solution to say, a production environment, then the end user has to select that environment form a drop down in teams approvals to find the approval. We think this could really confuse our users who are not the best at finding things to begin with, and even if I changed everyone's teams to the production environment, it doesn't save, and defaults back to the default environment if teams restarts. I know we can use outlook to approve, but I'm really trying to promote teams approvals as a one stop shop for approving and finding everything to our directors, and it just isn't obvious to have to select different environments in teams to find approvals when they click on it and the list if blank or at worse has completed legacy approvals scattered between the default environment and various production environments.

Am I missing something here, maybe a best practise, or is there a group policy I can change to have a different defaulted environment in teams approvals, how do you handle this scenario in your company?

Thanks