Launched MRC 576785

Power Automate: Desktop flows - Measure time and cost savings for desktop flows

This feature introduces built-in rules that calculate time and cost savings for desktop flows based on successful runs. You can define how long a task previously took when performed manually and let the platform compute time saved using flow run data. Cost savings can be estimate

Power Automate 03 Horizon06 Cost & Value

DIGITAL SKILL WORKS LTD / 12 PANES

GA / disclosure July CY2026
Platforms Web

What it is

Power Automate: Desktop flows - Measure time and cost savings for desktop flows is a Microsoft 365 roadmap item published via Microsoft Release Communications. Current status: Launched.

What it does

This feature introduces built-in rules that calculate time and cost savings for desktop flows based on successful runs. You can define how long a task previously took when performed manually and let the platform compute time saved using flow run data. Cost savings can be estimated by applying hourly rates or custom monetary baselines that scale with run volume. Savings accumulate automatically as flows run, making the impact of automation measurable over time. The feature is not enabled automatically. To use it, you configure time-saving and money-saving rules for a desktop flow by specifying manual run duration and cost baselines. Once configured, savings are calculated per successful run and aggregated automatically. The calculations can be disabled by turning off the configured rules, allowing you to control when savings are tracked. Business Value: This feature is designed for teams that want to demonstrate the business impact of desktop automation. It lets you automatically calculate time and cost savings compared to pre-automation processes, without relying on manual tracking or spreadsheets. These insights help you clearly show return on investment, justify automation initiatives, and communicate value to business stakeholders and Centers of Excellence. 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

Map licence or consumption impact to the frozen value case; avoid seat spray.

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 · 06 Cost & Value

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

  • MRC id: 576785
  • Status: Launched
  • Products: Power Automate
  • GA / disclosure: July CY2026
  • Preview: —
  • Platforms: Web
  • Cloud instances: Worldwide (Standard Multi-Tenant)
  • moreInfoUrls: —
  • Open on Microsoft 365 Roadmap

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