One Power Automate process licence can now cover up to 25 flows
Reviewed by Helen Jones
Microsoft has made Flow groups generally available in Power Automate as part of the July/August 2026 Power Platform update published on 6 August. One process licence, which includes 250,000 actions per day, can now be shared across up to 25 solution-aware cloud flows instead of buying capacity per flow. Builders create a group under More > Flow groups, add eligible flows, and watch shared capacity from the group view. If one flow needs more headroom, a process licence can still be assigned directly to that flow for dedicated capacity. The change applies only to solution-aware cloud flows, with a hard cap of 25 flows per group. Related licensing dashboard improvements are also listed in the same release window.
Before this, each process-licensed cloud flow that moved SharePoint files, refreshed reporting packs, or pushed Lists data often needed its own licence even when daily action use was modest. That made small reporting automation sets look expensive and pushed people back toward manual Excel routines or unlicensed personal flows that nobody could govern. What changed is not magic automation. It is packing density for moderate, solution-aware flows. Teams that already keep report automations inside solutions can pool capacity and see group-level usage. High-volume export or refresh jobs still burn through the shared pool and should stay on dedicated licences, so the real gain is cleaner cost control rather than fewer broken numbers.
Analysis
Treat this as a licence consolidation opportunity, not a reason to add more Automate. List your solution-aware reporting flows, put the moderate SharePoint, Lists, and pack-delivery jobs into one flow group under a single process licence, and leave any heavy refresh or bulk-export flow on its own licence so a spike cannot starve the rest.
Source note
Pulse published by Collab365 Spaces, reviewed by Helen Jones on . Cite as "One Power Automate process licence can now cover up to 25 flows", Collab365 Spaces. 2 sources referenced.