Before this feature enhancement, you needed to write an OData query if you wanted to filter out data in the Get items, Get files, or List rows SharePoint and Excel actions by a certain rule, such as a column name. With this enhancement, you can use a simplified OData editor without writing complex OData queries. Use the visual editor to build your OData query.

The savings feature provides the following benefits:

• You can set up a saving rule for a cloud flow, a work queue, or a desktop flow.
• The rule specifies how much time and money each child item generates. Child items include cloud flow runs, work queue items, and desktop flow runs.
• You see the aggregated savings in the automation center and in the new Value Hub in Power Platform admin center.

Before this feature, you needed to write complex expressions in your cloud flows in Power Automate to process data or to do conversions, manipulation, or comparison. With this feature, you can create complex expressions or edit your existing expressions simply by submitting natural language prompts to Copilot in Power Automate.

You need Copilot access in your tenant to use this feature. Turning off Copilot also turns off this feature.

When a condition action runs in Power Automate cloud flows, it returns only true or false as the final output. If the condition action doesn't run as expected, especially with complex condition logic that uses multiple dynamic content and expressions, it can be hard to debug the execution process. This feature simplifies the debugging experience for the Condition action after your flow runs. You can see detailed results for each row in a condition action, including the values in dynamic content and expressions, so you can find which part of the condition didn't work as expected.

Troubleshooting Copilot helps users fix errors in their cloud flows. It suggests corrections for issues that come up during authoring and debugging. Users can apply these corrections to fix their flow in the Power Automate designer.

Makers with access to Copilot automatically get this feature turned on.

You don't need technical knowledge to use this feature. When you want to add an action at a specific place, you get an option to describe to inline Copilot what actions you want in natural language. Then, inline Copilot automatically creates these actions for you.

Without contextual Copilot, you need to tell Copilot where you want to add new steps in the chat window. This process can take a lot of time.

This feature is automatically available for makers who have access to Copilot.

You don't need technical knowledge to use this feature. You see the autogenerated summary at the top of the page. You can expand the summary to read more details or select the Download button to save it as a PDF file.

This feature saves you time by automatically creating flow documentation for members who don't have access to the flow. Also, other members might not know how to read a raw flow definition.

Power Automate for desktop now lets you automate browsers without requiring an extension. The Launch browser actions include a new option to choose between extension-based automation and direct browser control. Direct browser control uses native browser drivers for interactions.

An advanced failover setting adds reliability by automatically switching to the next available method if the default method fails at runtime. For example, the setting enables failover from direct control to extension.

This update simplifies deployment, improves automation speed, and reduces points of failure for both individual makers and enterprise IT teams.

Copilot in Power Automate for desktop offers an interface that simplifies the automation creation process. With natural language and Power Fx syntax capabilities, you can create desktop flows by providing instructions in natural English or using Power Fx syntax. This capability eliminates the need for algorithmic or pseudocode knowledge. With Copilot, you can easily generate automations, saving valuable time and resources.

Work queues in Power Automate play an important role in improving the efficiency, scalability, and resiliency of automation. Work queues help you prioritize work.

You can configure Service Level Agreements (SLAs) for work queues with the following settings:

• Type of SLA
  • Time to live (TTL)
  • Business hours
• SLA engine
  • Prioritize work queue items closest to the SLA deadline.
  • Identify work queue items at risk.
  • Monitor the state of SLAs for work queues.

Step over and step out give you more control when debugging desktop flows in Power Automate for Desktop. Step over lets you skip subflows without entering them, so you can focus on the main logic. Step out lets you exit a subflow and return to the parent flow, which is helpful when reviewing nested logic or skipping known sections. You’ll see new icons and tooltips for both actions in the debugger toolbar during a paused run.

This feature is off by default. To turn it on, go to the Tools menu in the designer and enable it. Then, start debugging a flow. The step over and step out buttons appear in the debugger toolbar, and hovering over each shows a tooltip with a short description.

You can now create subflows as public or private in Power Automate for desktop. When you create a private subflow, any variable you add is local to that subflow and you can't access it from outside the subflow. With private subflows, you can set up input and output variables.

The Run subflow action shows input variables as fields for arguments and displays output variables for private subflows. In the variables pane, you can see which variables belong to a subflow and which variables are global. Use filters to quickly find variables.

You can create and assign tags to your desktop flows through the console. When you use this feature, you can search and filter your flows by tags. This feature makes it easier to manage and find specific flows.

You manage tags in the Dataverse environment. Tags aren't limited to desktop flows. In the future, other Power Platform assets can use this functionality.

Power Automate for desktop now supports templates. With these templates, you can start automation projects faster by using prebuilt flow structures that follow best practices.

Choose from several built-in templates, including:

• Generic business process
• Basic exception handling with try/catch logic
• Work queue item producer and consumer templates
• Generic logging frameworks

You can access templates directly from the Power Automate for desktop console. When you create a new flow, you can start from scratch or use a template. You can also import templates into existing flows from within the designer.

Organizations can create custom templates and distribute them centrally. This approach helps align with internal standards, speeds up development, and improves quality.

Power Automate for desktop now lets you assign custom names to actions directly in the flow designer. When you add an action to the designer panel, you can rename the action to something meaningful and descriptive. The custom names appear in runtime logs in the Power Automate portal, so you can more easily trace, monitor, and troubleshoot specific steps in flows. This enhancement promotes best practices in flow design, improves legibility, and benefits complex workflows or collaborative environments where naming consistency is critical.

When you capture a VM image, you can reuse the custom VM image to provision other hosted machines or hosted machine groups. The capture process:

• Snapshot: Captures the VM's disk at a specific point in time.
• Generalization: Removes machine and user-specific information from the VM for reuse.
• Storage in your Azure Compute Gallery: Stores the VM image so Power Automate services can use it.

Record with Copilot in Power Automate for desktop enables you to create desktop automations by sharing your screen and describing the task you want to automate, just as if you were explaining it to someone. Record with Copilot captures your voice, mouse, and keyboard inputs. It processes these inputs and converts them into a desktop flow that you can review, edit, and save before running. With this feature, automation is accessible to everyone, regardless of technical expertise, and the process of creating desktop flows is much faster.