Microsoft MVP (Business Application & Data Platform) | Microsoft Certified Trainer (MCT) | Microsoft SharePoint & Power Platform Practice Lead | Power BI Specialist | Blogger | YouTuber | Trainer
Microsoft Forms file uploads can be processed in Power Automate by retrieving the submitted response, parsing the upload details, and fetching the actual file content. This pattern matters to form owners and flow makers who need to email an uploaded document or send it to another destination. Dhruvin Shah [MVP] demonstrates the workflow for both personal and group forms.
A file-upload answer in a Forms response is not itself the file content. In the demonstrated flow, the answer arrives as a JSON array containing file information such as its name, ID, and link. The flow parses that information, retrieves the content from the file's storage location, and then passes the content to an action such as sending an email.
The important distinction is whether the form is personal or belongs to a Microsoft 365 group. In the demonstration, a personal form's upload is retrieved with OneDrive for Business. After the form is moved to a group, its file is retrieved from the group's SharePoint site instead. Changing the form's ownership context therefore means the file-content step in the flow needs to change too.
This is a practical pattern for people who build Power Automate cloud flows around Forms responses. The demonstration uses a form with a file-upload question, the Forms trigger and response-details action, a Compose action to inspect output, Parse JSON, a file-content action, and Send an email (V2). It tests with an uploaded file and sends that file as an email attachment.
The demonstration does not specify required licenses, tenant settings, regional availability, or prerequisites beyond access to the form, Power Automate, and the relevant storage location. It also does not establish a rollout or preview status; this is a workflow tutorial, not an announcement of a new feature. Confirm that the account running the flow can access the form and the OneDrive or SharePoint location it needs.
For a group form, the demonstrated flow needs two changes. If the group form is missing from the Form Id dropdown, enter a custom value using the form ID. The demonstration copies the ID from the form's URL; it does not give a detailed rule for extracting the value from every URL format.
Next, replace OneDrive for Business' Get file content with SharePoint's Get file content using path. Select the SharePoint site associated with the group form and map the file link from the parsed response to the file-path field, as shown in the demonstration. Use the new action's file-content output in the email attachment. Test a fresh group-form response to check that each step succeeds.
The example focuses on retrieving an upload and delivering it by email. It briefly mentions other possible destinations, including a SharePoint list or library and Dataverse, but does not demonstrate their configuration. Those destinations require their own actions and field mappings; the email setup should not be assumed to cover them.
The video tests a form configured for one file, while the flow design accounts for the possibility of multiple files by using an array and an automatic loop. It does not show how to handle an empty upload answer, failed file retrieval, or multiple attachments in one email. The exact JSON schema is based on the test response, so inspect the output from your own form rather than assuming every upload question returns an identical sample.
Licensing, tenant-wide availability, permissions administration, and a Microsoft-supported troubleshooting procedure are not covered in the demonstration. No official Microsoft documentation URL was supplied with the source material, so these details are not independently verified here.
Use When a new response is submitted and Get response details, then parse the file-upload answer and retrieve its content with the appropriate OneDrive or SharePoint action.
The demonstration shows that the group's file is stored in its SharePoint location, so the personal-form OneDrive file-content action no longer fits. It replaces that action with SharePoint Get file content using path.
The demonstration uses a custom value for the Form Id, copied from the form's URL. It does not specify a URL-extraction rule that applies to every URL format.
The supplied demonstration does not state licensing requirements. Check your organization's licensing and access before building the flow.