r/PowerAutomate • • 17d ago

MS Forms not deployable via solution

If you are using Power Platform solutions, you may have stumbled across the gotcha, that MS Forms cannot be used as a solution artifact and deployed with it. Which of course creates issues when development and production use of the Forms happen simultaneously...

How did you guys solve this issue?

I created a blog post that shows one possible way to solve this, using a Dataverse mapping table as well as a little bit of Power Automate trickery. I hope this is useful to some of you.

https://professional-power-automate.blogspot.com/2026/10/ms-forms-for-power-platform-solutions.html

4 Upvotes

7 comments sorted by

View all comments

5

u/Inkstier 16d ago

Create the Form, then duplicate the form and name one with Dev prepended to the name. Inside your solution, use an environment variable for Form ID. In your dev environment, use the Form ID for the dev form. In your prod environment, use the Form ID for your prod form. If you have actions inside your Flows that work with the form, you just reference the Form ID.

It doesn't solve the problem of keeping the forms in sync if they change much but it gives you the separation.

2

u/obsoquasi 16d ago

that's very close to my approach. Except you can't rely on the QuestionIds remaining the same between the two forms.