Cloud Flow or Desktop Flow? The Decision in 5 Questions
Cloud flow or desktop flow? Here is how to decide in Power Automate when a legacy ERP without an API is involved.
Copilot in Power Automate for Desktop creates, extends, and repairs desktop flows from a prompt, still with limitations around region and language.
Anyone who regularly works with Power Automate for Desktop knows this: a new flow often starts with a blank canvas and the question of which action should come first, which connector fits, and how to nest conditions and loops cleanly. This is exactly where Copilot in Power Automate for Desktop comes in: you describe in your own words what should be automated, and Copilot translates the description into concrete actions in the flow designer.
This article uses the official Microsoft documentation to show what Copilot in Power Automate for Desktop can actually do, where the feature reaches its limits, and how you can put it to sensible use in your daily work. Important up front: a large part of the Copilot features is still in preview and is currently limited to certain regions and account types, which you should factor in before relying on it.
According to the official documentation on Copilot in Power Automate for Desktop Copilot accompanies you throughout the entire flow creation process and covers three central scenarios:
Important: Copilot does not replace careful flow planning. You remain responsible for reviewing every generated action before it runs in production, as Microsoft explicitly emphasizes in the documentation.
To create a new flow, open the chat field either on the console's home page or via the Copilot side panel in the designer, and enter your prompt. Copilot processes the input, then automatically opens the designer and shows you, in the side panel, a list of the generated actions sorted by function group. In the designer's main area, Copilot additionally marks the generated section with two comments, one at the beginning and one at the end, so you can spot the AI-generated steps at a glance and review them specifically.
If Copilot recognizes the intent to automate browser or interface tasks, it inserts a placeholder at that point. You fill this placeholder by starting the recorder and capturing the actual clicks and inputs, or alternatively delete it and build the UI actions manually.
The quality of the result strongly depends on the prompt. Microsoft recommends in the documentation phrasing it as concretely as possible. Instead of "send email with Excel file", a prompt like "Send an email from the account accounting@contoso.com with the subject 'Contoso sales data' to sales@contoso.com and attach the Excel file at C:\contoso\contoso.xlsx" leads much more reliably to the desired result, because required parameters such as the file path are supplied directly, and actions are therefore less often flagged as faulty.
Besides pure flow creation, Copilot in Power Automate for Desktop brings three other capabilities that are worth using in everyday work.
With "Record with Copilot" you share your screen and narrate the process out loud while performing it, similar to explaining it to a colleague. According to the documentation on Record with Copilot an AI model evaluates video, narration, and mouse or keyboard input together, and also derives logic such as conditions and loops from it, which the classic recorder cannot do on its own. According to Microsoft, the recording is transmitted encrypted, kept for a maximum of 24 hours for processing, and then deleted; it is also not used to train the AI model.
If you need to understand a flow that is unfamiliar or hasn't been touched in a while, the "Summarize actions and subflows" skill helps. You refer to a line number or a subflow name, for example with "Summarize subflow 'main' in a few sentences", and Copilot delivers a compact explanation. This saves time especially during handovers or troubleshooting in flows that have grown over time.
If a UI or browser action fails because a selector no longer finds the target element, Copilot can, according to the documentation on repair at runtime automatically re-identify the matching element. You then decide whether to apply the suggestion permanently for all future runs, apply it only for the current run, or repair it manually. For unattended runs, this feature works through the automation center and is tied to managed environments.
Before you build Copilot into your process, it's worth taking a look at the current limitations according to the FAQ on Copilot in Power Automate for Desktop:
These limits are no reason to forgo Copilot; they simply show that you're currently best off using the feature as a quick draft for a first pass, not as a fully automatic replacement for a well thought-out flow architecture. You retain control, because every generated action stays visible in the designer and can be adjusted before execution.
Copilot in Power Automate for Desktop takes the tedious groundwork off your hands when drafting a flow for the first time, and also helps with understanding existing automations and repairing error-prone selectors. Especially for teams that are new to Power Automate for Desktop, this noticeably lowers the entry barrier, because you don't have to search for every action individually in the library. Still, it remains important to review every generated step and to take the preview notices for the respective region seriously.
If you want to introduce Power Automate for Desktop in your company or make existing flows more robust, NordFlux supports you with fixed-price projects around Power Automate automation, including advice on licensing and governance.
No, a large part of the features, including flow creation via prompt, Record with Copilot, and repair at runtime, is currently in preview according to Microsoft. Preview features are explicitly not intended for production use and may function in a limited way, which is why you should test generated flows especially thoroughly before deploying them in production.
Partially. According to the documentation, the generative answers to product questions as well as the summarizing of actions and subflows are also available in European environments, including Germany. Flow creation and extension using natural language, as well as Record with Copilot, on the other hand, are currently limited to environments in the USA.
Copilot covers only a subset of all available actions, including Clipboard, Compression, Conditions, Database, Date/Time, Email, Excel, File, Folder, HTTP, Loops, Message boxes, Mouse and keyboard, Outlook, PDF, Script, System, Text, Variables, Word, and XML. For actions outside these groups, you still need to work manually in the designer.
According to Microsoft, the screen recording is transmitted encrypted to the cloud, processed there solely for creating the flow, and then deleted, at the latest after 24 hours. The recordings are not used to train the underlying AI models. Even so, you should make sure that no sensitive information is visible on screen during the recording.
Yes. As a Power Platform administrator, you can disable the generative answers via the Copilot-supported help setting in the Power Platform Admin Center. For the other Copilot features, according to the documentation you should contact Microsoft Support, who can disable the feature at the tenant level.
Founder of NordFlux. Spent four years automating processes at enterprise scale at Dräger, and now brings that depth to the mid-market — pragmatic and with full data sovereignty.
Certifications
Cloud flow or desktop flow? Here is how to decide in Power Automate when a legacy ERP without an API is involved.
The Recorder in Power Automate Desktop captures clicks as flow actions. What it can do, how UIA and MSAA work, and where it hits its limits.
Why selectors break in Power Automate Desktop, how to build them robustly, and how to use Wait actions for real wait times instead of fixed pauses.
Copilot speeds up creating and repairing desktop flows through prompts, but it doesn't replace review by experience, especially with complex interfaces. We use Copilot where it genuinely saves time and take on quality assurance and ongoing operation of your flows. That way AI support stays a tool, not a risk.