Power Automate trigger and action for forms in SharePoint (Preview)

Power Automate introduces preview triggers and actions for SharePoint forms, enabling workflow automation on form submissions starting May 2026. Features include "Form submitted" trigger and "Get form metadata" action, supporting dynamic form handling and scalable automation while respecting existing SharePoint permissions.

[Introduction]

We're introducing new Power Automate capabilities for forms in SharePoint, enabling customers to automate workflows based on form submissions. These features are in Preview and may evolve before full General Availability.

This update includes:

• A new trigger: Form submitted
• A new action: Get form metadata 

[When this will happen:]

• Public preview: We will begin rolling out in early May 2026 and expect to complete by late May 2026.
• This post will be updated with General Availability dates in the future.

[How this will affect your organization:]

Who is affected:

• Power Automate users building flows with SharePoint forms
• SharePoint site owners and creators using forms experiences
• Administrators managing Power Automate and SharePoint

What will happen:

• The Form submitted trigger in Power Automate starts flows when a form is submitted from SharePoint list, file upload, or document generation experiences.
• The Get form metadata action retrieves the form structure, including fields, schema, and configuration, and enables flows to dynamically read form structure.
  • Flows can use form metadata (such as field names, types, required status, and defaults) to dynamically map responses without manual configuration, reducing fragility caused by dependency on fixed field IDs.
• These capabilities enable scalable automation scenarios such as approvals, notifications, integrations with other systems, routing, and orchestration based on form submissions.
• Document generation scenarios require enrollment in AI in SharePoint Public Preview.
• Existing SharePoint permissions are respected, and no additional configuration is required.

[What you can do to prepare:]

• No action is required. 
• Ensure Power Automate is enabled in your tenant.
• Review permissions for SharePoint sites (SharePoint site settings > site permissions) as flows will respect existing SharePoint access controls.
• Communicate updates to flow makers.
• Enroll in AI in SharePoint Public Preview if using document generation.

Learn more: Generate structured documents in a SharePoint document library - SharePoint in Microsoft 365 | Microsoft Learn 

[Compliance considerations:]

Question	Explanation
Does the change alter how existing customer data is processed, stored, or accessed?	Flows can dynamically read form structure and responses using the Get form metadata action. This operates within existing SharePoint permissions and does not introduce new storage locations.
Does the change introduce or significantly modify AI/ML or agent capabilities that interact with customer data?	Document generation (DocGen forms) is part of AI in SharePoint Public Preview and may involve AI-assisted form experiences for enrolled tenants.
Does the change include an admin control and can it be controlled through Entra ID group membership?	Availability depends on Power Automate and SharePoint service enablement and access policies, which can be governed through tenant controls.
Does the change allow a user to enable or disable the feature themselves?	Users can create or not use flows leveraging these triggers/actions within the bounds of tenant policies.