Launched MRC 576824

Power Automate: Cloud flows - Share Process license capacity across workflows

With flow groups, you can share Process license capacity across up to 25 cloud flows, optimizing license allocation and reducing costs for organizations operating higher-volume workflows that don't need their own dedicated capacity. Prerequisites: Power Automate Process licenses

Power Automate 03 Horizon04 Security06 Cost & Value07 Licence

DIGITAL SKILL WORKS LTD / 12 PANES

GA / disclosure July CY2026
Platforms Web

What it is

Power Automate: Cloud flows - Share Process license capacity across workflows is a Microsoft 365 roadmap item published via Microsoft Release Communications. Current status: Launched.

What it does

With flow groups, you can share Process license capacity across up to 25 cloud flows, optimizing license allocation and reducing costs for organizations operating higher-volume workflows that don't need their own dedicated capacity. Prerequisites: Power Automate Process licenses available to the environment Cloud flows stored in solutions Power Automate maker permissions Business Value: Save costs, reduce management effort, and improve resource utilization by efficiently sharing capacity across multiple flows. Enabled for: Enabled for admins/makers/marketers automatically

Why you should care

Board

Track as Horizon signal; decide whether it changes Wave 0 priority or stays on the watchlist.

CISO

Confirm identity, data access, and overshare exposure before enabling for broad cohorts.

CFO

Metering change: set budgets, owners, and reclaim rules before open consumption.

Adoption

Pilot with a named cohort and measure changed work, not vanity clicks.

Suggested action

Wave 0 first: Security → GRC → Cost & Value → Licence → Adoption. Decide: adopt for a named cohort, defer, or reject. If adopting, update licence and adoption plans in the same week.

12 Panes: 03 Horizon · 04 Security · 06 Cost & Value · 07 Licence

Communication needed

  • Security: Assess exposure, Conditional Access, and agent/tool permissions.
  • GRC: Update AI/agent register and evidence path; confirm DPIA triggers if personal data is in scope.
  • FinOps: Forecast seat or credit impact; align to frozen value case.
  • Adoption: Plan cohort messaging, clinics, and success measures.
  • Comms: One story for board and staff — what changes, what does not, who owns risk.

Benefits

  • May improve productivity on a specific Microsoft 365 surface when permissions and data quality allow.
  • Roadmap visibility helps Horizon planning without guessing dates.

Risks

  • Status and dates change; treat MRC as directional, not a contract.
  • Enabling without Steady controls can amplify overshare or cost leakage.

Source

Microsoft Release Communications / Microsoft 365 Roadmap (AI at Work). Content is subject to Microsoft API Terms of Use. Dates and status change; verify in the official roadmap before acting.

Back to roadmap intel