Loading...

Microsoft Teams: Collect information with List Form in Workflows

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 […]

The post Microsoft Teams: Collect information with List Form in Workflows appeared first on M365 Admin.

Published on:

Learn more
Need help with this product?

We can help you with Microsoft Teams: Collect information with List Form in Workflows

If you want help implementing, troubleshooting, or improving this product, contact us and we’ll point you in the right direction.

M365 Admin
M365 Admin

by João Ferreira

Share post:

Related posts

Dynamics 365 Contact Center: Quality evaluation – One-Time Evaluation Frequency

Quality evaluation plans now support a Once frequency type for both case evaluations and conversation evaluations. When creating an evaluation...

1 day ago

Microsoft Teams: Phishing Detection in Teams Messaging

Microsoft Teams is introducing AI-powered phishing detection that uses conversation context to identify phishing and social engineering in hig...

1 day ago

Microsoft Purview: Data Loss Prevention-Admin Units Support for Copilot & Cowork DLP

Microsoft Purview Data Loss Prevention is extending Administrative Units support to Microsoft 365 Copilot, Copilot Chat, and Cowork. This enab...

1 day ago

Take action: NTLMv1 hardening changes might affect network connections on devices without Credential Guard

Beginning with the October 2026 security update, Windows 11, versions 26H2, 25H2, and 24H2, along with Windows Server 2025 enforce restriction...

1 day ago

Power Platform – Recreate connections made to the Azure DevOps connector prior to September 2024

We identified that an app, flow, or agent in your environment utilizes a connection to the Azure DevOps connector that was created prior to Se...

1 day ago

Microsoft Purview | Data Loss Prevention: Count of labeled documents condition for Exchange Online

Microsoft Purview DLP introduces a new Exchange Online condition to detect emails with a high count of sensitivity-labeled attachments, enhanc...

1 day ago

Microsoft Teams: Automatic recording and transcription options align with admin policies

Microsoft Teams will update meeting options to show only automatic recording and transcription settings allowed by assigned policies, adding a...

1 day ago

Copilot Studio – Information regarding the end of support for selected AI models

We are announcing the end of support for selected AI models on the Standard and GitHub Copilot harnesses in Copilot Studio. Beginning on each ...

1 day ago

Updates available for Microsoft 365 Apps for all channels

We’ve released updates to the following update channels for Microsoft 365 Apps: Current Channel Monthly Enterprise Channel Semi-Annual E...

1 day ago

Microsoft Planner: AI-generated status reports in Planner Agent

Microsoft Planner now includes AI-generated status reports via Planner Agent in Microsoft 365 Copilot, summarizing plan progress, risks, and n...

1 day ago

Newsletter

Get the latest Dynamics 365 and Power Platform content in your inbox

A curated digest of community blogs, product news, videos, and podcasts — delivered without the noise.

Weekly updates Unsubscribe anytime Fresh community picks
We use your email only for the newsletter and you can unsubscribe at any time.
By subscribing, you agree to the privacy policy.