Power Automate Flow Groups Let You Pool License Capacity Across 25 Flows

New Power Automate flow groups let admins share one Process license's capacity across 25 flows, cutting per-flow licensing costs.

AI & AUTOMATION

8/10/20263 min read

white concrete building during daytime
white concrete building during daytime

Microsoft has started rolling out flow groups in Power Automate, a licensing feature detailed in the "What's new in Power Platform: July/August 2026 feature update" post published to the Microsoft Power Platform Blog on August 6. Flow groups let organizations pool the capacity of a single Process license, 250,000 actions per day, across up to 25 solution-aware cloud flows instead of buying a dedicated license for every individual automation. For IT admins who have watched Power Automate license costs creep up as more teams build flows, this is a direct lever to pull.

The mechanics are straightforward. A flow group is a container that shares one Process license's daily action allowance across the flows assigned to it. Rather than provisioning a separate license per flow, an admin can group related automations, say, all the flows supporting a single HR onboarding process or a finance approval chain, and let them draw from the same pool. Microsoft recommends grouping flows with moderate, predictable usage, in the range of 5,000 to 50,000 actions per day each, since flows that individually spike toward the 250,000 ceiling get less benefit from sharing. The feature only applies to solution-aware cloud flows, meaning flows built and shipped inside a Power Platform solution rather than personal, non-solution flows created outside that structure.

Setup lives under More > Flow groups in the Power Automate portal, where admins can create a group, add eligible flows, and monitor combined capacity usage in one view. Notably, flow groups began rolling out automatically in July 2026 as part of the broader feature wave, and no admin action is required to enable the capability itself, it simply appears in tenants as the rollout reaches them. That means the only manual work is deciding which flows to consolidate and actually building the groups, not flipping on some hidden toggle first.

The timing is worth flagging alongside two other licensing changes Microsoft has pushed through this summer. The standalone Power Automate mobile app for iOS and Android is being deprecated on August 31, with Microsoft pulling it from both app stores and pointing users toward Teams, the Power Automate web portal, and the Power Apps mobile app instead. Combined with flow groups, the pattern is consistent: Microsoft is consolidating how organizations license and access Power Automate, trimming standalone surfaces while giving admins more granular tools to manage cost on the automation platform itself.

For admins managing a Power Automate environment, the practical move now is an audit. Pull a list of solution-aware cloud flows and their daily action counts, either from the admin center's capacity reports or the flow group monitoring view once it appears in your tenant, and flag which ones sit comfortably below the 50,000-action range. Those are the strongest candidates for grouping. Flows tied to the same business process are natural first candidates too, since consolidating them into one group also simplifies which team owns the associated license. If your organization has been buying a Process license per flow as a default policy, this is a reasonable point to revisit that policy before your next renewal cycle.

One caveat worth testing before committing: because a flow group shares one capacity pool, a single flow that spikes unexpectedly can eat into headroom the rest of the group is depending on. Microsoft's own guidance to stick with moderate, predictable-usage flows is really a warning about that shared-pool risk, not just a sizing suggestion. Admins should monitor group-level usage for the first few weeks after consolidating rather than assuming the pooled capacity will behave the same as separately licensed flows. Flow groups won't change how Power Automate flows are built, but they do change how they're licensed, and that's a budget conversation worth having now rather than at renewal time.

Connect

Stay updated with latest Microsoft blog news

© 2025. All rights reserved.