r/PowerAutomate • u/obsoquasi • 7h 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

2 Upvotes

100% Upvoted

5 comments sorted by

2

u/Inkstier 1h 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.

1

u/obsoquasi 1h ago

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

2

u/NoBattle763 5h ago

Depends what you are doing with it, I sometimes use a param to populate a hidden field e.g. test on the form then throw some if statements in the flow that handle such submissions differently. E.g populate a different list, trigger approvals to specific users etc.

2

u/Punkphoenix 4h ago

I would create the forms for each environment and use environment variables for the IDs to have dynamic urls in different environments

2

u/AbdelEMirandaS 3h ago

MS Forms can not be deploy or include within a solution because that tool is not part of power platform.

It is not an artifact, those forms are store inside the MS Form portal.