Send Microsoft Forms Responses to Excel with Power Automate

You already have a Microsoft Form. You already have an Excel tracker. The awkward bit is getting each new response into that existing workbook without downloading another file or pasting rows by hand.

Power Automate can do that with three connector steps:

1. When a new response is submitted
2. Get response details
3. Add a row into a table

This is a one-way append workflow. It is not a two-way sync between Forms and Excel, and changing a row in Excel does not change the original Forms response.

Fact-checked against Microsoft Learn on 7 August 2026.

First: do you need a flow at all?

Microsoft Forms can provide an Excel workbook for responses. Use that native response workbook when it already gives you the file, ownership and reporting model you need.

Build the Power Automate flow when you need responses in a different, existing table—for example, a team-owned tracker in SharePoint—or when the same submission must also start an approval, create a task or update another system.

Do not create a second copy of the data merely because a tutorial told you to. Every extra store creates another owner, another permission boundary and another place for the numbers to disagree.

What this build does

The flow listens for new submissions to one Microsoft Form, retrieves the answers and appends one row to an Excel table stored in OneDrive for Business or SharePoint.

Microsoft documents that the Forms connector has one trigger—When a new response is submitted—and one action—Get response details. The Excel Online (Business) connector supplies the Add a row into a table action.

The Excel connector can work with files in OneDrive for Business, SharePoint sites and Microsoft 365 Groups. A workbook surfaced through a Teams channel is normally stored in the Team's connected SharePoint site.

1. Design the destination table

Create the workbook in the location the team will own long term. Avoid putting a shared operational workbook in one employee's personal OneDrive unless that ownership is deliberate.

Add a table with one column for each value you want to store. A useful support-request example might contain:

Excel column	Source
ResponseId	Forms trigger
SubmittedAt	Flow timestamp or response data
ResponderEmail	Forms response details, when identities are collected
Department	Form question
RequestType	Form question
RequestDetails	Form question
FlowRunId	Power Automate expression, optional for troubleshooting

Select the range and create an actual Excel Table. Merely typing headers into cells is not enough; the connector writes to a table object.

Give the table a stable name such as FormResponses. You can rename a table in current Excel for the web or desktop Excel through the table-design controls available in that client. You do not need the desktop-only workaround claimed in the old version of this article.

Save and close the workbook before configuring the flow. Keeping it open is not always fatal, but avoiding competing edits removes one obvious source of setup trouble.

Add a response ID

Store the Forms response ID in its own column. It gives you a practical key for tracing a row back to the submission and helps you detect duplicates after a retry or manual repair.

Do not assume the visible row number is a durable business identifier.

2. Create the automated cloud flow

Open Power Automate, select Create, then create an Automated cloud flow.

Choose the Microsoft Forms trigger When a new response is submitted and select the form.

If a Microsoft 365 group owns the form, it may not appear in the Form Id dropdown. Microsoft says to open the form, copy the form ID from its URL and enter it as a custom value.

If another team owns the form and it is missing, check Shared with me in Forms and confirm the long-term ownership. A flow attached to one departing employee's form is a support ticket waiting to happen.

3. Retrieve the answers

Add the Microsoft Forms action Get response details.

Set:

• Form Id to the same form.
• Response Id to the Response Id dynamic value from the trigger.

The trigger tells the flow that a submission exists. Get response details retrieves the actual answers so later actions can use them as dynamic content.

Run a test submission before you map the Excel action. It is easier to recognise the correct dynamic values when the flow has seen a representative response.

4. Append the row to Excel

Add Excel Online (Business) → Add a row into a table.

Choose:

1. The file location: OneDrive for Business, SharePoint site or Microsoft 365 Group.
2. The document library.
3. The workbook.
4. The FormResponses table.

Power Automate should now show one input for each table column. Map the fields deliberately:

Excel column	Dynamic value
ResponseId	Response Id
SubmittedAt	The timestamp you have chosen
ResponderEmail	Responder's email, if the form records identity
Department	Department answer
RequestType	Request type answer
RequestDetails	Request details answer

Names change when form questions change. After editing a question or table column, reopen the Excel action and confirm the mapping rather than assuming Power Automate repaired it.

5. Test the behaviour, not just the green tick

Save the flow and submit a response that exercises the awkward fields: long text, punctuation, optional answers and any choice labelled “Other”.

Then check four places:

1. The Forms response exists.
2. The flow run succeeded.
3. Get response details returned the expected answers.
4. The correct workbook contains one correctly mapped row.

Submit a second response. A single success does not reveal duplicate handling, stale connections or a table mapping that only worked for one answer shape.

Excel is the fragile part of this design

The Excel Online (Business) connector is useful, but Microsoft documents limits that matter once this becomes an operational process:

• The supported workbook size is 25 MB.
• A file can remain locked for update or deletion for up to six minutes after connector use.
• Simultaneous modifications from Excel clients, Power Automate, Power Apps or other connectors are not supported and can cause merge conflicts or inconsistent data.
• An apparently successful row operation can take up to 30 seconds to become visible.
• Throttling can occur, including when the workbook's operation queue is busy.

That makes Excel a poor destination for high-volume, multi-writer or transaction-sensitive workloads.

Use a SharePoint list, Dataverse or another proper data store when several processes need to write concurrently, the file is approaching the connector limit, or the records drive a business process that cannot tolerate ambiguous writes.

Excel can still be the reporting surface. It does not have to be the database.

Common problems and honest fixes

The workbook or table does not appear

Confirm the file is stored in a supported OneDrive for Business, SharePoint or Microsoft 365 Group location. Open the workbook and verify that the destination is an Excel table, not a normal cell range.

If you renamed or moved the file after building the flow, reselect it in the action.

The form does not appear in Form Id

For a group-owned form, copy the form ID from the form's URL and add it as a custom value. For a form owned elsewhere, check the Forms Shared with me tab and sort out ownership before treating the flow as production-ready.

New form questions do not appear as dynamic content

Save the form, refresh or recreate the Get response details action, and run a fresh test submission. Then reopen the Excel action and remap the affected columns.

Do not delete a production action casually. Record the existing mapping first.

The flow succeeds but the row is not visible immediately

Microsoft says row changes can take up to 30 seconds to appear. Wait briefly and refresh the workbook before building a duplicate retry path.

Rows fail or data becomes inconsistent under load

Check whether somebody has the workbook open, another flow writes to it, or several runs overlap. Microsoft does not support concurrent writes to one workbook.

Reducing concurrency may ease a small workload. Moving the records to SharePoint or Dataverse is the sturdier answer for a process that naturally has concurrent writers.

Dates look wrong

Time-zone handling is a design decision. Microsoft notes that form submission timestamps use UTC by default in flow scenarios. Decide whether Excel should store UTC, a named local time or both, and make the conversion explicit.

The flow has started producing duplicate rows

Use the stored ResponseId to identify duplicates. Before adding elaborate “find then insert” logic to Excel, consider whether the workbook is still the right backend—the connector's concurrency limits make robust idempotency harder than it would be in a data store with unique keys.

Production checklist

• The form and workbook have durable team ownership.
• The workbook is in a supported business location.
• The destination is a named Excel table.
• Response ID is stored.
• Every mapped field has been tested with realistic data.
• Form-question changes have an owner and a remapping check.
• No other client or flow writes to the workbook concurrently.
• Flow failures have a monitored owner.
• The workbook remains comfortably below 25 MB.
• The process has a defined point at which it moves from Excel to SharePoint or Dataverse.

If the same form needs approvals or another destination, extend the flow after the response is captured. For reusable flow-building patterns, see how to copy and paste Power Automate actions safely.

If your form accepts files rather than simple answers, the storage and attachment steps are different. This Outlook attachments to SharePoint guide shows the same principle: retrieve the actual file content before you store it.

Keep your flows maintainable

The Power Automate Builders Space brings current flow patterns, limits and troubleshooting together without pretending every green tick is a production system.

Microsoft sources used

• Common ways to use Microsoft Forms in a flow
• Overview of flows with Microsoft Forms
• Add a group-owned form to a flow
• Troubleshoot Forms in Power Automate
• Excel Online (Business) connector and limits
• Use flows with Excel

Source boundary: Microsoft documents the connector steps and limits. This guide does not claim immediate delivery, two-way synchronisation or suitability for high-volume concurrent writes. Test the complete flow in your own Microsoft 365 environment.