How to Post Microsoft Forms Responses to Teams with Power Automate

To post Microsoft Forms responses to Teams, create an automated cloud flow in Power Automate with the Forms trigger When a new response is submitted, add Get response details, then add the Teams action Post message in a chat or channel and drop the answers into the message. The same flow can add a task with Add a to-do (V3) and a tracking row with the SharePoint action Create item.

In the video, one flow does all three jobs for a four-question request form I was running at the time. Each response posts to the General channel of a team, adds a task to an In tray list in my Microsoft To Do, and creates an item in a Microsoft List with a sent column defaulting to No, so I can see who I’ve followed up. It took six or seven minutes to build.

Before you start

• A work or school account. The Microsoft Forms connector only works with organisational accounts.
• The form’s ID if it’s a group form. Group forms don’t appear in the trigger’s drop-down. Open the form for editing and copy the part of the address after FormId=.
• A standard channel. The Teams connector can’t currently post a message or card to a private channel, so use a standard channel or a group chat.
• Where your list lives. A list under My lists in Microsoft Lists sits in your OneDrive, so your OneDrive address is the site.

Forms, Teams, To Do and SharePoint are all standard connectors, so no premium Power Automate licence is needed.

How do you build the flow?

1. Create the flow. In Power Automate, select Create > Automated cloud flow and choose the Microsoft Forms trigger When a new response is submitted. Pick your form in Form Id, or paste the ID for a group form.
2. Get the answers. Add the Microsoft Forms action Get response details. Choose the same form in Form Id and put Response Id from the trigger in Response Id. If Power Automate wraps it in an Apply to each, leave it; the trigger returns a list of responses.
3. Post to Teams. Add the Microsoft Teams action Post message in a chat or channel. Set Post as to Flow bot or User, Post in to Channel, then choose the Team and Channel. In the message, type a label for each answer and insert the matching dynamic content.
4. Add a task. Add the Microsoft To-Do (Business) action Add a to-do (V3). Choose the To-do List and enter a Title with the responder’s name in it. Importance, Status, Content, Due Date and Reminder Date-Time are optional.
5. Log it in a list. Add the SharePoint action Create item. In Site Address, choose the site, or select Enter custom value and paste your OneDrive address for a personal list. Pick the List Name and fill its columns with dynamic content.
6. Test it. Save the flow, submit a response and open the flow’s run history. In my test the run succeeded, with the message in the General channel, the task in In tray and the item in the list.

When I recorded this in 2022, Post as also offered Power Virtual Agents, now part of Copilot Studio. The To Do action I used has since become Add a to-do (V3), and older Teams actions such as Post a message (V3) are deprecated.

How do you post a Forms response to Teams as an adaptive card?

An adaptive card gives the answers a title, labels and colour, which is easier to pick out in a busy channel than a block of text.

Watch the video

1. Design the card in the Adaptive Cards Designer: a title, then a bold label and a text block for each answer, with placeholder text where the answers will go.
2. Copy the card’s JSON from the designer.
3. In the flow, use Post card in a chat or channel instead of the message action, choose the team and channel, and paste the JSON into the card field.
4. Replace each placeholder in the JSON with the matching dynamic content from Get response details.

In the 2020 video the action was Post your own adaptive card as the Flow bot to a channel, now deprecated. My IT request form came through as a card with a large red title, the issue type and the description, and the team could reply in the thread underneath.

Check what Forms already does before you build a flow

For one person who just needs to know a response came in, Forms already does the job. More form settings > Response receipts > Get email notification of each response emails you every time, with a link to the result. I’d only build a flow when a team needs to see the response, or when it has to create a task or a row someone will update.

In the 2022 video I posted as User, which puts your name on every post as if you wrote it. Flow bot makes it clear the post is automated. Either way, the flow runs under the connection owner’s account, so build anything a team relies on with an account that keeps its access when people change roles.

Everything in a Teams post is visible to everyone in the channel. If the form asks for anything personal, like a phone number or a medical reason for leave, I’d post the responder’s name and a link to the list item, and keep the details in the list, where you control the permissions.

Then decide who owns the follow-up. Add a to-do puts the task in one person’s To Do, which suited me because I was the only one following up. For a team, I’d skip To Do and give the list an Assigned to column and a status, on the team’s SharePoint site rather than under My lists. Creating and querying a Microsoft List with Copilot in SharePoint covers the list side.

Files from an upload question are saved in OneDrive or the group’s SharePoint site, covered in where Microsoft Forms file uploads go. For sharing the form itself, see creating a QR code for a Microsoft form.

Frequently asked questions

Why doesn’t my form show up in Power Automate? Group forms don’t appear in the Form Id drop-down of When a new response is submitted. Open the form for editing, copy the part of the browser address after FormId= and paste it into Form Id as a custom value. The Forms connector also only works with work or school accounts.

Should the flow post as Flow bot or as me? Flow bot makes it clear the post is automated, while User shows your name on every post. Flow bot is only available in commercial tenants, so in GCC, GCC High or DoD tenants you post as User.

Why does my flow fail with “Request Entity too large”? Teams messages posted by a flow are capped at about 28 KB, including formatting, links and tables. Long answers push past it, so post a summary and a link to the list item, and keep the full text in the list.