How to Create a File Approval Workflow from Microsoft Forms Using Power Automate

Posted at 18:02h in Blog, Microsoft 365, Migration by Nithin DG 0 Comments

Why Businesses Are Automating Document Approvals

In today’s fast-moving business environment, organizations cannot afford to rely on slow, paper-based, or manually managed approval processes. Missed approvals, lost documents, compliance gaps, and delayed workflows cost companies thousands of productive hours every year.

Microsoft Forms and Power Automate, two powerful tools within the Microsoft 365 ecosystem, are transforming how organizations handle document submissions and approvals. By combining these platforms, businesses can build intelligent, automated approval workflows that trigger instantly when a form is submitted, route files to the right approvers, send automated notifications, and maintain a complete audit trail, all without writing a single line of code.

Business Benefits of Workflow Automation Using Power Automate

Before diving into the technical setup, it is important to understand why organizations across industries, from healthcare and finance to manufacturing and education, are investing in Microsoft Power Automate approval workflows.

Faster Approvals

Manual approval processes often take days or weeks due to email chains, missed notifications, and unavailable approvers. Automated workflows deliver approval requests instantly and send reminders to ensure nothing falls through the cracks, reducing approval cycle times by up to 80%.

Reduced Manual Work

Power Automate eliminates repetitive tasks such as forwarding emails, copying file links, updating spreadsheets, and sending status updates. Once configured, the workflow handles all of these steps automatically, freeing your team for higher-value work.

Improved Document Tracking

Every submission, approval, rejection, and comment is automatically logged. Managers and compliance teams gain full visibility into where each document stands in the approval process at any given moment.

Better Collaboration

Approval requests routed through Microsoft Teams or Outlook keep all communication centralized within the Microsoft 365 environment. Approvers can review, comment, approve, or reject directly from their inbox or Teams channel without switching between applications.

Increased Compliance and Accountability

Automated workflows ensure that every document follows a predefined approval path. Audit logs capture who approved what, when, and why, making it easy to demonstrate compliance during internal or external reviews.

Streamlined Business Operations

From HR document approvals and purchase requests to contract reviews and compliance submissions, workflow automation using Power Automate creates consistent, reliable business processes that scale as your organization grows.

Understanding Microsoft Forms and Power Automate

What Is Microsoft Forms?

Microsoft Forms is a cloud-based survey, quiz, and form creation tool included in Microsoft 365. It allows users to design custom forms with a variety of question types, including text fields, dropdowns, date pickers, ratings, and critically for this guide, file upload fields. Responses are automatically stored in Microsoft 365 and can be exported to Excel or connected to other services via Power Automate.

For workflow automation purposes, Microsoft Forms serves as the entry point where users submit documents, requests, or data that need to go through an approval process.

What Is Power Automate?

Microsoft Power Automate (formerly Microsoft Flow) is a cloud-based workflow automation platform within the Microsoft Power Platform. It enables users to create automated workflows, called flows, that connect hundreds of apps and services, including Microsoft 365, SharePoint, OneDrive, Outlook, Teams, Dynamics 365, Salesforce, and thousands of third-party applications.

Power Automate supports three types of flows: automated flows triggered by events (like a new form response), instant flows triggered manually, and scheduled flows that run at specified intervals.

How Microsoft Forms and Power Automate Work Together

When a user submits a Microsoft Form, Power Automate detects the new response through a trigger and begins executing a predefined sequence of actions. These actions can include retrieving uploaded files, saving them to SharePoint or OneDrive, sending approval requests to designated approvers, notifying users of decisions, and updating records, all automatically and in real time.

Prerequisites Before Building Your Approval Workflow

Before creating your Microsoft Forms approval workflow in Power Automate, ensure the following requirements are met:

1. Microsoft 365 Licensing Requirements

You will need an active Microsoft 365 subscription. Power Automate is included in the following plans:

Microsoft 365 Business Basic, Standard, or Premium
Microsoft 365 E1, E3, or E5
Microsoft 365 F1 or F3 (Frontline Workers)
Power Automate Per User Plan (for advanced features and premium connectors)

The Approvals connector, used to send and manage approval requests, requires a Power Automate license with access to premium features if your tenant has restrictions.

2. Access Permissions

Microsoft Forms: Creator must have access to Microsoft Forms in their Microsoft 365 tenant.
Power Automate: User must have permission to create and run flows.
SharePoint or OneDrive: User must have site collection or folder access with read and write permissions where uploaded files will be stored.
Approver access: Designated approvers must have Outlook or Microsoft Teams access to receive and respond to approval requests.

3. SharePoint or OneDrive Setup

Files uploaded through Microsoft Forms are initially stored in the form creator’s OneDrive. To integrate with SharePoint for centralized storage, set up a dedicated document library or folder structure before building your flow. Recommended approach:

Create a SharePoint document library named Document Approvals or similar.
Create subfolders for different departments or document types (HR, Finance, Legal).
Setappropriate permissionlevels for approvers and submitters.

4. File Upload Configuration in Microsoft Forms

Enable file uploads in your Microsoft Form by adding a File Upload question type. Note the following important settings:

File upload questions are only available to users within your organization (Microsoft 365 tenants).
You can limit file types (PDF, DOCX, XLSX, images, etc.) and file size (maximum 1 GB per file, maximum 10 files per submission).
Uploaded files are automatically stored in the form creator’s OneDrive under Apps > Microsoft Forms > [Form Name].

5. Power Automate Environment Access

Ensure you have access to the Power Automate portal at make.powerautomate.com. Confirm your environment settings (default environment vs. a custom environment) and that you have permission to create and share flows in that environment.

Step-by-Step Guide: Creating a File Approval Workflow

Step 1: Create a Microsoft Form with File Upload Functionality

Go to forms.office.com and sign in with your Microsoft 365 account.
Click New Form and give it a descriptive name (e.g., Document Approval Request)

Add relevant form fields based on your use case. Recommended fields include:

◦ Submitter Name (Text field)

◦ Department (Dropdown)

◦ Document Type (Dropdown: Invoice, Contract, HR Form, etc.)

◦ Request Description or Comments (Long text field)

◦ Date Needed (Date picker)

◦ Upload Document (File Upload field)

Click the File Upload question type and configure file restrictions.
Preview the form and verify the file upload question works correctly.
Copy the Form ID from the URL (you will need it in Power Automate). The Form ID appears after forms.office.com/Pages/ResponsePage.aspx?id=

Step 2: Configure File Storage in OneDrive or SharePoint

When a form is submitted with a file, that file is saved in the form owner’s OneDrive automatically under the following:

OneDrive > Apps > Microsoft Forms > [Your Form Name] > Question

For enterprise workflows, copy or move these files to a SharePoint document library for centralized management. In your Power Automate flow (Step 3 onwards), you will add an action to copy files from OneDrive to SharePoint automatically. Plan your SharePoint folder structure before proceeding.

Step 3: Create an Automated Cloud Flow in Power Automate

Go to make.powerautomate.com and sign in.
Click Create in the left navigation pane.
Select Automated cloud flow.
Name your flow (e.g., Document Approval Workflow – MS Forms).
In the search box, type “Microsoft Forms” and select the trigger “When a new response is submitted.”
Click Create.

Step 4: Configure the Form Trigger

In the When a new response issubmittedtrigger, select the Form ID you created in Step 1 from the dropdown.
Click New Step.

Search for Microsoft Forms and select the action Get response details.
Set the Form ID and Response ID (select the dynamic value Response ID from the trigger).

This action retrieves all field values from the submitted form, including the file upload link, which you will use in subsequent steps.

Step 5: Retrieve the Uploaded File Dynamically

Uploaded files in Microsoft Forms are stored as links in the response. To work with the actual file in Power Automate:

Add a new action and search for OneDrive for Business.
Select “Get file content using path.”

In the File Path field, use the dynamic content from the file upload question in the form response (this will be a URL or path in the form owner’s OneDrive).
Optionally, add a SharePoint Create file action to copy the file to a centralized SharePoint document library for record-keeping.

Step 6: Set Up the Approval Action

Click New Step and search for Approvals.
Select the Start and wait for an approval action.
Choose the approval type:

◦ Approve/Reject – First to respond: Approval is complete when any one assigned approver responds.

◦ Approve/Reject – Everyone must approve: All assigned approvers must approve for the request to be approved.

◦ Custom responses: Define custom response options (e.g., Approve, Reject, Request More Info).

Fill in the approval request details:

◦ Title: Use dynamic content such as Document Approval Request: [Document Type] from [Submitter Name]

◦ Assigned to: Enter the email address(es) of the approver(s). You can use dynamic content or hardcode specific approvers.

◦ Details: Include submitter name, department, document type, description, and a link to the uploaded file in SharePoint or OneDrive.

◦ Item link: Provide a direct URL to the uploaded document so approvers can review it before deciding.

Step 7: Send Approval Requests Through Outlook or Microsoft Teams

Power Automate’s Approvals connector automatically delivers approval requests via email (Outlook) and optionally through the Microsoft Teams Approvals app. To ensure approvers receive requests in Teams:

Ensure approvers have Microsoft Teams installed and the Approvals app enabled.
Approvers will receive both an email notification and a Teams notification automatically when the flow triggers the approval action.
For Teams-only notifications, add a Post an Adaptive Card and wait for a response action from the Microsoft Teams connector as an alternative to the standard Approvals connector.

Step 8: Configure Approval Conditions (Approve/Reject Logic)

After the approval action, add a condition control to branch your workflow based on the outcome:

Click New Step and select Condition.
Set the condition: Outcome (from the Approvals action dynamic content) is equal to Approve.
In the Yes branch (Approved), add actions for:

◦ Sending an approval confirmation email to the submitter via Outlook.

◦ Moving the file to an Approved Documents folder in SharePoint.

◦ Updating a SharePoint list or Excel table with the approval status and date.

In the No branch (Rejected), add actions for:

◦ Sending a rejection notification email with the approver’s comments.

◦ Moving the file to a Rejected Documents folder.

◦ Logging the rejection reason and date.

Step 9: Send Automated Notifications to Users

In both the Approved and Rejected branches, use the Send an email (V2) action from the Office 365 Outlook connector to notify the submitter:

Use dynamic content to personalize the email with the submitter’s name, document type, and approval decision.
Include the approver’s comments or rejection reason in the email body.
Add a link to the document in SharePoint for reference.
For Teams-integrated workflows, add a Post a message in a chat or channel action to notify relevant team members or channels.

Step 10: Save Approval Status and Audit History

To maintain a complete audit trail of all approvals, add one of the following tracking mechanisms:

SharePoint List: Create a SharePoint list called Approval Log with columns for Submitter Name, Document Type, Submission Date, Approver, Decision, Comments, and Document Link. Use the Create item action to add a record after each approval or rejection.
Excel Table in OneDrive: Use the Add a row into a table action from the Excel Online (Business) connector to log each approval record.
Dataverse: For enterprise-grade tracking and reporting, use Microsoft Dataverse (part of Power Platform) to store approval records for use in Power BI dashboards.

Step 11: Test and Validate the Workflow

Before deploying your flow to end users, thoroughly test it:

Submit a test form response with a sample file attachment.
Monitor the flow run in Power Automate under My Flows > [Your Flow] > Run History.
Verify that the approval request is received in Outlook and Teams.
Test both the Approve and Reject outcomes.
Confirm that notification emails are sent correctly.
Check that the SharePoint list or Excel log is updated accurately.
Test edge cases such as large file sizes, missing file attachments, and multiple approvers.

Real-World Business Use Cases

The Microsoft Forms approval workflow using Power Automate can be applied across virtually every industry and department. Here are the most common and impactful use cases:

Approval Workflow Table

Use Case	Form Fields	Approval Owner	Integration
HR Document Approvals	Employee name, document type, effective date, signed form upload	HR Manager / HRBP	SharePoint HR Library
Invoice Approval Workflow	Vendor name, invoice number, amount, PO reference, invoice PDF	Finance Manager / CFO	Accounts Payable SharePoint
Purchase Request Approvals	Requester, item description, cost, vendor, budget code	Department Head	Procurement Tracker List
Contract Review Process	Contract type, parties involved, value, legal notes, contract file	Legal Counsel / COO	Legal Document Library
Employee Onboarding Forms	New hire name, start date, IT requirements, HR forms bundle	HR & IT Manager	Onboarding SharePoint Site
Compliance Document Submissions	Document category, regulatory reference, submission date, file	Compliance Officer	Compliance Records Library

Automate Your Approval Process with Microsoft Power Automate

Eliminate manual approvals, reduce delays, and streamline document workflows with Microsoft Forms and Power Automate automation solutions tailored for your business.

Choosing the Right Approval Type for Your Business

Power Automate offers several approval models. Selecting the right one depends on your organizational hierarchy, risk tolerance, and process complexity.

Approval Types Table

Approval Type	Description, When to Use & Best For
Basic Approval (Single Approver)	A single approver receives the request and their decision is final. Use for low-risk, high-volume approvals like internal document reviews or routine purchase requests under a set threshold. Best for: Small teams, straightforward approvals, time-sensitive requests.
Multi-Level Sequential Approval	Requests are sent to approvers in a defined sequence. Each level must approve before it moves to the next. Use for high-value or high-risk decisions such as capital expenditures, executive contract approvals, or regulatory submissions. Best for: Finance, Legal, Executive approvals.
Parallel Approval (Multiple Approvers)	All designated approvers receive the request simultaneously. The flow branches based on whether all must approve or just the first to respond. Use for cross-departmental reviews where input from multiple teams is needed concurrently. Best for: Project approvals, policy changes, cross-functional sign-off.
Custom Approval Workflow	Supports custom response options beyond Approve and Reject, such as Request More Information, Escalate, or Approve with Conditions. Use for complex business processes that require nuanced decision-making. Best for: Enterprise workflows, regulated industries, document lifecycle management.

Best Practices for Building Scalable and Secure Approval Workflows

Naming Conventions

Use clear, consistent flow names (e.g., [Dept]–[Process]-Approval-Flow-v1).
Give SharePoint lists and libraries purpose-driven names.
Use meaningful approval titles for quick understanding.

Error Handling

Configure run-after settings to manage failures gracefully.
Use the Terminate action in error branches for proper logging.
Send failure alerts to administrators for quick issue resolution.

Approval Hierarchy Management

Store approver details in SharePoint lists instead of hardcoding.
Use dynamic lookups to route approvals by department, type, or amount.

Security and Permissions

Apply least-privilege access for submitters and approvers.
Enable SharePoint audit logging for tracking activity.
Use Microsoft Entra ID groups to manage approver access.

File Retention

Define retention policies using Microsoft 365 Compliance Center.
Move uploaded files to SharePoint immediately instead of storing them in personal OneDrive accounts.

Workflow Optimization

Set approval timeouts with reminders or escalation rules.
Use parallel approvals to reduce processing time.
Monitor flow analytics to identify bottlenecks.
Export backup copies before making major flow changes.

Common Issues and Troubleshooting Guide

File Upload Errors

Issue:File upload questions are not appearing or not working in the form.
Solution: File upload is only available for organizational accounts. Ensure the form is not set to Anyone can respond. Verify the form creator has sufficient OneDrive storage available.
Issue:Power Automate cannot find the uploaded file path.
Solution: The file field in Get response details returns a URL. Use a Compose action with the expression: replace(outputs(‘Get_response_details’)? [‘body/r[field_id]’], ‘https://[tenant]-my.sharepoint.com‘, ”) to extract the relative file path.

Workflow Permission Issues

Issue: The flow fails when trying to create a file in SharePoint.
Solution: Verify that the flow connection account (the Microsoft 365 user account used to connect the SharePoint connector in Power Automate) has Contribute permission on the target SharePoint document library.
Issue: Approvers cannot see the document link in the approval email.
Solution: Ensure that the SharePoint document library sharing settings allow at least read access to the approvers. Check that external sharing is enabled if approvers are outside the organization.

Approval Emails Not Triggering

Issue:The flow runs but no approval email is received.
Solution: Check the approver’s email address for typos. Verify the Approvals connector has the correct connection. Check the approver’s junk or spam folder. Confirm the approver has a valid Power Automate license.

Flow Timeout Problems

Issue:The flow times out before the approver responds.
Solution: Power Automate flows have a maximum run duration of 30 days. For approval flows that may take longer, use the Approval Action with a definedtimeoutand add a reminder branch using Parallel Branch + a Delay action to send reminders before the timeout is reached.

SharePoint Integration Issues

Issue:Files are being created with incorrect names or in wrong folders.
Solution: Use dynamic content carefully when setting the file name and destination path. Sanitize file names using thereplace() expression to remove special characters that SharePoint does not allow (e.g., #, %, &).

Power Automate Connector Limitations

Issue: The Microsoft Forms connector only returns 5,000 responses.
Solution: For high-volume forms, consider using a SharePoint list as the data store and triggering the flow from a SharePoint list item creation instead of directly from Forms.

FAQ: Microsoft Forms Approval Workflow Using Power Automate

Can external users upload files through Microsoft Forms?

File upload functionality is generally limited to internal authenticated users within Microsoft 365 tenants.

How do I track approval history?

Approval history can be stored in:

SharePoint lists

Dataverse

SQL databases

Excel logs

Can Microsoft Forms upload files directly to SharePoint?

Yes. Group Forms typically store uploaded files in SharePoint document libraries.

Ready to Streamline Your Document Approvals?

Building a file approval workflow using Microsoft Forms and Power Automate is one of the fastest ways to eliminate manual bottlenecks, improve accountability, and modernize your business operations. Whether you are automating HR document approvals, invoice processing, purchase requests, or contract reviews, the Microsoft Power Platform gives you the tools to build scalable, secure, and intelligent workflows without writing complex code.

However, getting the most out of Power Automate requires more than following a tutorial. Enterprise-grade workflows demand careful planning around approval hierarchy design, security configuration, error handling, SharePoint architecture, licensing optimization, and integration with your existing Microsoft 365 environment.