Microsoft Teams: Collect information with List Form in Workflows

Microsoft Teams Workflows will add a new trigger, "A form is submitted," for automating actions based on SharePoint list–backed form responses. Rolling out September–October 2026, it enables posting responses in Teams, uses existing SharePoint governance, requires no admin action, and respects current permissions and policies.

[What and Why:]

We are introducing a new trigger in the Microsoft Teams Workflows app: A form is submitted. This trigger enables organizations to automate actions when users submit responses to forms built on SharePoint lists. Individual form responses can be used as workflow variables, enabling creators to post selected responses to a Teams channel and include additional details as threaded replies.

Forms created with this experience are backed by SharePoint lists, providing organizations with familiar data management, governance, compliance, and export capabilities.

[Rollout Schedule:]

• Targeted Release (Worldwide): Rollout begins in early September 2026 and is expected to complete by late September 2026.
• General Availability (Worldwide): Rollout begins in late September 2026 and is expected to complete by late October 2026.

[Impact on Your Organization:]

Who is affected:

• Users who can create workflows in Teams.

Platforms and services: Microsoft Teams, Teams Workflows, SharePoint Lists.

• Users will see a new trigger, A form is submitted, when creating workflows from scratch in the Teams Workflows app.
• Forms are built on SharePoint lists, and each submitted response is stored as a SharePoint list item.
• The backing SharePoint list can be pinned as a tab in a Teams channel for visibility, tracking, and data export.
• Individual answers from form responses are available as workflow variables and can be used in workflow actions.
• Creators can post one response value as a parent Teams channel message and publish the remainder of the response as threaded replies.
• Existing workflows that use the equivalent trigger in Power Automate are not affected and will continue to operate as they do today.
• Access to form responses follows existing SharePoint site and list permissions.
• Form responses are governed by existing SharePoint retention, compliance, and information governance policies.
• Workflow executions use the connections and permissions of the workflow creator.
• The feature is enabled automatically and follows existing administrative controls and restrictions.
• If your organization restricts SharePoint site or list creation, limits access to the Workflows app, or uses Power Automate Data Loss Prevention (DLP) policies that block the trigger, those controls will continue to apply.

[Action Required / Recommendations:]

No admin action is required. The feature will roll out automatically according to the schedule above.

We recommend that administrators:

• Notify users about the new workflow trigger and associated capabilities.
• Review and update internal documentation related to Teams Workflows and form-based business processes.
• Provide guidance on where users should create forms and backing SharePoint lists so that responses are stored in locations already governed by organizational policies.
• Review existing SharePoint permissions, site provisioning processes, and Power Automate DLP policies to ensure they align with organizational governance requirements.

[Compliance Considerations:]

• Form responses are stored as SharePoint list items in a SharePoint site.
• Access to responses is governed by existing SharePoint site and list permissions.
• Responses are subject to existing SharePoint retention, compliance, and information governance policies.
• No new administrative controls are introduced. Existing SharePoint governance controls, Teams Workflows permissions, and Power Automate DLP policies continue to apply.
• Users can only build and run workflows if they already have permission to create workflows and access the underlying SharePoint resources.