Flow Designer

[MohammedHiM]

Migrating Flow Trigger from Microsoft Forms to ServiceNow Form Submission

Objective

I am refactoring an existing automated cloud flow to change its entry point. The goal is to decouple the flow from Microsoft Forms and instead trigger the automation immediately when a specific form or record is submitted inside ServiceNow.

Current Architecture (As-Is)

• Trigger: Microsoft Forms – When a new response is submitted
• Action 1: Microsoft Forms – Get response details
• Downstream Actions: After submitting the form, approval email will be received, and upon approval , the power automate will be associated and will sends parameter received from the form to the DevOps Pipeline which will run to deploy a VM in Azure.

Target Architecture (To-Be)

• Trigger: ServiceNow – When a record is created
• Downstream Actions: Same as above, but natively utilizing ServiceNow dynamic content tokens instead of Microsoft Forms data.

[DylanBlumenberg]

Hi @MohammedHiM, can you clarify what the question is?

If the goal is to move away from using Microsoft Forms and use a form in ServiceNow, a catalog item or record producer would be your best bet. 

For a catalog item, you would set up the form with the questions you want to ask. Here's a link to the basics of that: Create or edit a catalog item

Then you would then set up a Flow, which would fire when the catalog item form is submitted by a user. Here's a document for that too: Create a flow. The trigger of the flow would be the Service Catalog application trigger. 

Then from there, you would define your downstream actions in the flow. 

[MohammedHiM]

Hi @DylanBlumenberg 
And thanks for your response! 

Let me clarify the requirement a bit more clearly: Currently, we receive Azure VM provisioning requests through a Synaps form, where users provide all required parameters (VM name, location, size, etc.). However, after receiving the request, we manually re-enter the same information into a Microsoft Form, which then triggers a Power Automate flow to start an Azure DevOps pipeline for VM provisioning. The goal is to eliminate the Microsoft Form step entirely. Instead, we want to: Use the Synaps (or ServiceNow) form as the single input source Automatically send the submitted parameters directly to Power Automate Trigger the same existing automation (DevOps pipeline) without manual re-entry So essentially, the requirement is: How can we integrate the ServiceNow (or Synaps) form submission directly with Power Automate (via API or trigger), so that it replaces the current Microsoft Form and continues to drive the existing VM provisioning pipeline?

[MohammedHiM]

Hi @DylanBlumenberg 

Thanks for your response!

Currently, we receive requests to deploy Azure VMs through a Synaps form, which includes the VM's parameters such as name, location, and size. We then manually enter this information into an MS form. Once the MS form is submitted, automation begins by running the DevOps pipeline to provision the VM. We would like to eliminate the MS form step and integrate the Synaps form directly with Power Automate, using the information provided in the Synaps form.