How to Fix Power Automate Not Saving Group Microsoft Forms Responses to SharePoint
Question details
The user needs to resolve an issue where a Power Automate flow successfully saves personal Microsoft Forms responses to SharePoint but fails when attempting to save responses from a Microsoft 365 group form to a group-associated SharePoint list. There are also concerns about maintaining data integrity if the form owner leaves the organization.

- Product
- Power Automate, Microsoft Forms, SharePoint
- Device & OS
- not provided
- Scenario
- Automating data collection by passing submitted responses from a Microsoft 365 group form into a destination SharePoint list.
- Observed behavior
- The flow executes correctly for personal forms but triggers failures or permission errors when using a group form and a group-associated destination list. Relying on an individual's account for the flow connection poses a risk to data continuity.
Ensure you have administrative or owner access to the specific Microsoft 365 group, the group's Microsoft Form, and the destination SharePoint list before modifying the Power Automate flow.
Verify Group Form IDs and Connection Permissions
Ensure that the correct form ID is used in your trigger and that your flow connection has the necessary permissions to access both the group form and the SharePoint list.
A common cause for this failure is that group forms generate different identifier structures compared to personal forms. The flow must explicitly reference the group form's exact ID and use an account connection with adequate group access.
Navigate to your Power Automate dashboard, locate the failing flow, and click 'Edit' to open the configuration settings.
Expand the 'When a new response is submitted' trigger. Ensure you are using the exact form ID generated by the 'Send and collect responses' link for the group form, rather than manually selecting the name from the dropdown.
Expand the SharePoint 'Create item' action. Confirm that the correct 'Site Address' and 'List Name' belonging to the Microsoft 365 group are selected.
Click the three dots (ellipsis) on both the trigger and the SharePoint action to check 'My connections'. Ensure the connected account has active permissions for both the Microsoft 365 group and the SharePoint site.

Consult the Microsoft Power Automate Community
If configuration checks do not resolve the issue, consult specialists in the official community for advanced flow troubleshooting and detailed connection log analysis.
Looking for a Simpler Way to Manage Documents? Try WPS Office
While complex automated flows often require extensive configuration in Microsoft 365, managing your daily documents doesn't have to be complicated. WPS Office provides a free, lightweight, and highly compatible alternative for handling spreadsheets, documents, and presentations with a familiar interface.

Frequently Asked Questions
Why does my Power Automate flow work for personal forms but not group forms?
Personal forms use your direct user account permissions, while group forms require the flow connection to have explicit access to the Microsoft 365 group resources. The flow may fail if the connection lacks group-level permissions or if the wrong Group Form ID is selected in the trigger.
Where do I find the correct form ID for a Microsoft 365 group form?
You can find the accurate form ID in the URL when you click the 'Send and collect responses' button on the group form. It is the long string of characters immediately following 'id=' in the web address.
How can I prevent my automated flows from breaking when an employee leaves?
To avoid data-integrity concerns when a form owner departs, use a dedicated service account to create and manage the Power Automate flows and connections. Additionally, ensure forms and SharePoint lists are owned by a Microsoft 365 group rather than an individual's OneDrive or personal account.




