Power Automate Desktop Flows Add Built-In ROI Savings Tracking: How Time and Cost Rules Work

Tracked under Microsoft AI at Work roadmap ID 576785 (and previously communicated to administrators via Message Center post MC1383792), the "Measure time and cost savings for desktop flows" capability is listed as Launched for the Web platform in the Worldwide (Standard Multi-Tenant) cloud instance. While the roadmap entry carries an October 16, 2026 publication timestamp and notes a general availability target of July 2026, Microsoft Learn’s 2026 Release Wave 1 documentation pinpoints the specific general availability date as July 16, 2026 (following earlier June 2026 admin briefings ). Note that as of October 2026, Microsoft has archived its standalone release-plan pages on Microsoft Learn—last updating this entry on August 27, 2026—and transitioned ongoing roadmap tracking to the AI at Work roadmap.

How Desktop Flow Savings Rules Work​

If you are worried about Power Automate suddenly inventing phantom financial metrics across your tenant, take a breath. Although the capability itself is enabled automatically at the platform level for administrators, makers, marketers, and analysts, savings tracking is strictly opt-in per desktop flow. No calculations occur until a user deliberately configures rules for a specific automation.

When you decide to track a desktop flow, the platform relies on user-defined baselines coupled with actual execution telemetry. Rather than guessing what a script does, Power Automate asks you to define the pre-automation reality:

• Time-Saving Rules: You specify how long the task previously took when a human performed it manually. As the desktop flow executes, the platform uses flow run data to compute the time saved across successful runs.
• Money-Saving Rules: You can estimate financial impact in one of two ways: by applying an hourly rate to convert saved time into currency, or by establishing a custom monetary baseline per run that scales alongside execution volume.
• Automatic Aggregation: Once those rules are switched on, Power Automate calculates the savings for every successful run and aggregates the totals automatically over time.
• On-Demand Control: If a process changes, a flow enters maintenance, or your reporting requirements shift, you can disable the calculations at any time simply by turning off the configured rules for that desktop flow.

Section Summary: Power Automate’s desktop flow savings tracker is a launched, opt-in feature that multiplies maker-defined manual duration and cost baselines against successful desktop flow executions to aggregate time and financial savings automatically.

Cloud Flows vs. Desktop Flows: Mind the Documentation Gap​

To understand where this update fits in the broader Power Platform ecosystem, it helps to look at how Microsoft has been building out its value-tracking architecture. In its 2025 Release Wave 1 plans on Microsoft Learn, Microsoft outlined a broader vision to quantify time and money savings across cloud flow runs, work queue items, and desktop flow runs, surfacing aggregated insights in the Automation Center and the Power Platform admin center’s Value Hub.

However, veteran administrators know that a shared vision does not always mean identical technical plumbing on day one. Microsoft’s primary documentation page for "Savings in Power Automate" on Microsoft Learn (last updated in November 2025) specifically details how saving rules work for cloud flows. While it offers a useful look at Microsoft’s design philosophy, admins must be careful not to blindly copy-paste cloud flow constraints onto desktop flows without verifying how the desktop implementation behaves in their environment.

For context and comparison, here is what Microsoft Learn explicitly documents for cloud flows:

• Environment and Solution Limits: In cloud flows, saving rules can only be attached to solution-based cloud flows, and environments using Dataverse for Teams cannot use the feature.
• Test Run Exclusions and Latency: Successful test runs do not generate savings in cloud flows, and periodic background aggregation means it can take up to one hour for a successful cloud flow run to appear in the savings total.
• The Rounding Quirk: In cloud flows, hourly-rate money rules require the time-saving rule to be enabled, and the resulting currency calculation rounds to whole numbers without saving decimals. Microsoft Learn gives a candid example: if a cloud flow saves 1 hour and 15 minutes per run at an hourly rate of $1/hour, the mathematically correct $1.25 saving is rounded and recorded as $1.
• Security Roles and Governance: Viewing and editing cloud flow saving rules requires security role privileges on the Saving Rule and Flow Aggregation tables (which the standard Environment Maker role includes), and environment administrators can block money rules at the environment level.

Why does this boundary matter? Because Microsoft’s release-plan entry for desktop flows confirms the high-level mechanics—time rules, hourly rates, custom monetary baselines, and per-successful-run aggregation —without explicitly confirming whether the cloud flow rounding behavior, table privilege requirements, or one-hour aggregation delay apply identically to desktop flows. When configuring your first desktop flow rules in the portal, test a single flow first to observe how your specific tenant handles decimal values and reporting latency.

Section Summary: While Microsoft’s earlier cloud flow savings documentation reveals granular mechanics like whole-dollar rounding and Dataverse table permissions, those rules are explicitly written for cloud flows; administrators should treat them as architectural context rather than guaranteed desktop flow specifications.

The ROI Reality Check: Estimates Are Not Audited Cash​

Let’s put on our skeptical IT auditor hats for a moment. Why is Microsoft so eager to bake ROI calculators directly into Power Automate? The answer is simple: renewal season. When enterprise software budgets come under the microscope, platforms that can generate a glossy dashboard showing "5,000 hours and $250,000 saved" have a much easier time justifying their licensing footprint to the Chief Financial Officer.

There is nothing inherently wrong with that—in fact, CoE teams desperately need native telemetry so they can stop wasting hours maintaining tracking spreadsheets. However, based on general industry practices for RPA governance, there is a massive difference between a configured baseline estimate and realized net savings.

Because Power Automate calculates savings by multiplying successful runs against whatever baseline the maker types into the rule, the output is only as honest as the input. Keep these practical realities in mind before taking your dashboard totals to an executive board meeting:

1. Garbage In, Gospel Out: If an enthusiastic maker claims a manual invoice entry task used to take 20 minutes—when in reality an experienced clerk did it in four minutes—Power Automate will happily multiply that 20-minute exaggeration across thousands of runs.
2. Gross vs. Net Time: A manual baseline should represent the human labor actually eliminated. Furthermore, the built-in rules track gross savings per successful run; they do not subtract the hours your developers spent building the desktop flow, fixing broken UI selectors after an application update, or handling failed runs that required human intervention.
3. Soft Dollars vs. Hard Dollars: Saving five minutes of an employee's time 100 times a week frees up capacity for higher-value work, which is a genuine productivity win. It does not, however, automatically reduce the company's payroll expenses by that hourly rate.

Practical Rollout Guide for Automation Leads​

To get genuine, defensible value out of desktop flow savings rules, treat the configuration as a governed process rather than a free-for-all:

• Standardize Your Baselines: Don't let individual makers guess how long a task takes. Time the manual process with a stopwatch across multiple runs before turning on the automation, and document how you arrived at that duration.
• Agree on Hourly Rates: Work with Finance or HR to establish standardized, blended hourly rates for different business units so one department isn't valuing clerical automation at $150 an hour while another uses $25.
• Audit Rule Configurations Regularly: If your Center of Excellence relies on aggregated savings to prioritize support or justify infrastructure, review the configured time and money baselines periodically to ensure processes haven't changed.
• Communicate the Assumptions: When presenting Power Automate savings reports to leadership, explicitly state the manual baseline durations and cost rates used to generate the numbers. Transparency builds far more credibility with stakeholders than an unexplained magic number.

Section Summary: Because desktop flow savings are calculated from user-entered baselines rather than independently audited financial ledgers, CoE leads should standardize how manual durations and hourly rates are measured to ensure ROI reports remain credible.