Others

How to Run Power Automate Teams Messages in Parallel

Muhammad TalhaMuhammad Talha Oct 22, 2026 869 views

Question details

User needs to send Microsoft Teams messages simultaneously without waiting for previous recipients to respond in a Power Automate flow.

How to Run Power Automate Teams Messages in Parallel
Product
Microsoft Power Automate
Device & OS
not provided
Scenario
Automating Microsoft Teams messages based on processing SharePoint list items.
Observed behavior
The Power Automate flow processes SharePoint list items sequentially, causing subsequent Teams messages to delay until the first recipient responds.
Before you start

Ensure you have editing permissions for the Power Automate flow and verify that your Microsoft 365 licensing supports the required API request limits to avoid connector throttling.

Solution 1Recommended

Enable Concurrency Control in the Apply to Each Action

Activate parallel processing to allow the flow to run multiple iterations simultaneously, sending Teams messages without sequential delays.

By default, the 'Apply to each' loop in Power Automate runs sequentially. Enabling concurrency control forces the loop to process multiple items at the same time, significantly reducing the total execution time when waiting for user responses.

1
Open Flow Settings

Navigate to your Power Automate portal, locate your specific flow, and click 'Edit'. Find the 'Apply to each' action that contains your Teams message steps.

2
Access Action Settings

Click the three dots (ellipses) in the top-right corner of the 'Apply to each' action card and select 'Settings' from the dropdown menu.

3
Enable Concurrency Control

Toggle the 'Concurrency Control' switch to the On position. Adjust the Degree of Parallelism slider to your desired number of parallel runs (up to the maximum supported limit of 50).

4
Save and Test

Click 'Done' to apply the settings, then save your flow. Run a manual test to ensure messages are dispatched simultaneously to users.

Enable Concurrency Control in the Apply to Each Action
Important Consideration: Running processes in parallel can affect shared data variables, ordering of operations, and may trigger API throttling limits if the concurrency degree is set too high.
Free Microsoft Office alternative

Enhance Your Productivity with WPS Office

While Power Automate handles complex automated workflows, WPS Office provides a lightweight, entirely free alternative to Microsoft Office for your daily document processing needs. Enjoy high compatibility with all major Microsoft formats without the subscription fees.

  1. 1. Download WPS Office: Visit the official WPS website and download the free installer for your operating system.
  2. 2. Install the software: Run the downloaded executable file and follow the simple on-screen instructions to complete the installation.
  3. 3. Open your documents: Launch WPS Office and easily open your existing Microsoft Office files to start working immediately.
Fully compatible with Microsoft Word, Excel, and PowerPoint formats (.docx, .xlsx, .pptx).Lightweight application that runs smoothly and efficiently on most devices.Free built-in PDF editing, conversion, and annotation tools.Familiar user interface for a seamless and quick migration.
microsoft office alternative - wps office

Frequently Asked Questions

What is the maximum degree of parallelism in Power Automate?

The maximum degree of parallelism you can set in an 'Apply to each' action is currently 50. Setting this to a higher number allows more instances of your loop to run at the exact same time.

Can I turn off concurrency control once it is enabled?

No, once you enable concurrency control and save the flow, it cannot be turned off for that specific 'Apply to each' action. If you need to revert to sequential processing, you must delete the action and recreate it from scratch.

Why are my variables returning incorrect values in parallel runs?

Variables in Power Automate are globally scoped within the entire flow. If multiple parallel branches update the same variable simultaneously, they will overwrite each other, causing unexpected results. Use 'Compose' actions instead of initialized variables inside parallel loops to avoid this data overlap.

Does parallel processing trigger API throttling in Teams or SharePoint?

Yes, if your flow makes multiple API calls concurrently, it may exceed the connector's rate limits (throttling limits) for Teams or SharePoint. Always test thoroughly and adjust the parallelism slider to a safe threshold based on the API limits.