Daily-It

개발, AI, 인프라, 자동화와 일상 IT 제품 후기를 직접 써보며 정리하는 기술 블로그입니다.

Power Automate vs Power Automate Desktop: Choosing Between Cloud Automation and Desktop RPA

Summary

Power Automate and Power Automate Desktop have similar names, but they serve different purposes. Power Automate is a tool that connects cloud services and apps to automate workflows, and Power Automate Desktop is an RPA tool that automates desktop tasks running on Windows PCs. In this article, based on official documents as of 2026, we will summarize the differences between the two, licensing and implementation methods, and cases of frequent confusion in production.

Table of Contents

Background

When you first encounter Power Automate, the first thing that confuses you is the name. You can see Power Automate on the Microsoft 365 screen, and there is a separate app called Power Automate Desktop on Windows. Because they are both automation tools, they feel like the same product, but in reality, what they automate and where it runs are different.

To put it simply, it can be divided as follows:

  • Web services, Microsoft 365, Teams, SharePoint, Outlook, and automation of approval processes: Power Automate cloud flows
  • Opening Excel on my PC, clicking on an old program, and copying values ​​from a web page: Power Automate Desktop desktop flow

In some cases, only one of the two is used, but in production, the cloud flow often calls the desktop flow and used together.

The Difference at a Glance

Category Power Automate Power Automate Desktop
Main use Cloud Workflow Automation Windows Desktop RPA Automation
execution location Microsoft Cloud Your PC or registered machine
representative audience Outlook, Teams, SharePoint, Dataverse, SaaS connectors Excel app, browser, ERP, legacy programs, files/folders
flow type Automated, Instant, Scheduled cloud flow Desktop flow
Installation required Usually used in browsers Requires Windows app installation
Advantages Stable service integration, strong in triggers/approvals/notifications Strong in UI clicks and legacy program automation
Cautions Connector/License/Request Limits PC health, login sessions, runtime, network impact

When to Use Power Automate

Power Automate is ideal for connecting cloud services.

For example, this task:

  • Send notifications to Teams when Outlook mail arrives
  • Saving Forms Responses to a SharePoint List
  • Send approval requests and log results
  • Call an API at regular intervals and save the results
  • Run follow-up actions once a file is uploaded to OneDrive or SharePoint

The key is trigger and connectorno see. Flows can run in the Microsoft cloud without users having to turn on their PCs. However, you need to make sure that the connector you use is standard or premium, that it is not subject to request volume limits, and that your organization’s policies allow it.

When to Use Power Automate Desktop

Power Automate Desktop is a Windows app that creates and runs desktop flows. Microsoft official documentation describes Desktop flows as an RPA feature in Power Automate.

It is suitable for the following situations:

  • When an old in-house program does not have an API
  • When you open an Excel file and need to read or save specific cells
  • When you need to copy data from a web page and enter it into another program.
  • When you need to automate rule-based tasks where people click repeatedly
  • When you need to deal directly with terminals, browsers, folders, files, and UI elements

Power Automate Desktop is greatly affected by the state of your PC. There are more reasons for failure than cloud flows due to screen resolution, login session, program window location, permissions, proxies, and firewalls.

Licensing and Execution Model

The most common sticking point in Power Automate is licensing rather than the feature itself.

Some cloud flows can be created with the default permissions included with Microsoft 365. However, if you require premium connectors, Dataverse, RPA, unattended execution, or advanced request volume, you may need a separate Power Automate license.

Desktop flow also differs depending on the execution method.

How it runs Description Cautions
Attended RPA Runs under human supervision on the PC where the user is logged in Affected by user’s session and screen state
Unattended RPA Run on registered machines even when unattended Separate license and machine setup required
Cloud flow + Desktop flow Cloud flow calls desktop flow Requires machine runtime, network, and permission settings

Exact licensing depends on your organization agreement, Microsoft 365 plan, and Power Automate Premium/Process license. So, you shouldn’t judge that “it’s free” just by looking at the article or video. Before actual application, you need to check the license in the admin center and the connector you want to use.

Common Confusion and Fixes

Case 1. Power Automate Desktop is installed but does not run in the cloud

It can feel like you just install the Power Automate Desktop app and all your automation will run right in the cloud. However, to run desktop flows in the cloud, your machine registration, runtime, account, and license must match.

The first thing to check is:

Power Automate machine runtime 설치 여부
머신 등록 상태
실행 계정 권한
Attended/Unattended 라이선스
회사 네트워크에서 필요한 엔드포인트 허용 여부

Microsoft’s Troubleshooting Desktop Flow Runtime article notes that diagnostic tools can help identify cloud runtime connection and machine registration issues.

Case 2. When both Microsoft Store version and MSI version are installed

The official installation documentation describes both Microsoft Store installation and MSI installation, but Installing both versions together on the same computer is not supportedand guide you.

Symptoms may be vague.

앱은 실행되는데 런타임 연결이 이상함
업데이트가 꼬임
머신 등록 또는 실행이 실패함

In this case, first clean up the installation status.

설정 → 앱 → 설치된 앱 → Power Automate 확인
Microsoft Store 버전인지 MSI 버전인지 확인
둘 중 하나만 남기고 제거

For general user PCs, the Microsoft Store version with automatic updates is convenient, but for environments that require machine runtime and central management, MSI installation may be more appropriate.

Case 3. I thought it was free, but I got blocked on the premium connector.

This is a common mistake in Power Automate. Common connectors in Microsoft 365, such as Outlook, Teams, and SharePoint, are relatively easy to access, but some connectors, Dataverse, on-premises data, and advanced RPA implementations may require licensing.

The recommended order of confirmation is as follows:

1. 사용하려는 커넥터가 Standard인지 Premium인지 확인
2. 내 계정에 어떤 Power Automate 라이선스가 있는지 확인
3. 조직 DLP 정책에서 해당 커넥터 조합을 허용하는지 확인
4. 요청량 제한에 걸리지 않는지 확인

If you don’t have administrator privileges, it’s difficult to fix it yourself. In this case, it is quicker to check licenses and policies with your administrator before designing the flow.

Case 4. Desktop flow works on my PC, but fails when run as a server.

Desktop flow has a strong tendency to automate human screen operations. Therefore, it is difficult to guarantee that the flow recorded on my PC will be successful on other machines.

The main causes are:

  • screen resolution difference
  • App version differences
  • No login session
  • Permission differences
  • Change pop-up location
  • Network proxy/firewall
  • Change UI element name

When possible, we recommend using actions based on UI elements rather than coordinate clicks, and standardizing the resolution and app version of the running machine. When it comes to long-term operational automation, unattended RPA and machine management should be considered from the beginning.

Case 5. When the flow slows down or turns off from one day onwards

Power Automate has request volume and throughput limits. Microsoft documentation explains that request limits may vary depending on your license and performance profile, and that flows may be slowed down or turned off if they consistently exceed the limits.

In this case, don’t just look at the error message, but check the following:

실행 기록의 실패 시점
하루 실행 횟수
커넥터 호출 횟수
반복문 안에서 API를 너무 많이 호출하는지
같은 흐름에 너무 많은 일을 몰아넣었는지

The solution isn’t just raising licenses. Splitting up the flow, reducing unnecessary repetitive calls, or making trigger conditions more specific often come first.

Best Practices

When designing automation for the first time, you should first decide “where it will be executed” rather than “what can be made of it.”

  • Power Automate cloud flow for data movement between cloud services
  • If you need to manipulate Windows screens, use Power Automate Desktop
  • If a cloud event needs to start a PC task, cloud flow + desktop flow
  • For long-term operations, design licensing, request volume, monitoring, and failure notifications from the beginning.

Desktop flow can be easily broken later, especially if you only rely on recording. If possible, UI elements should be reliably captured, and exception handling, retries, and log storage should be included.

Common Mistakes

Understanding Power Automate Desktop as only a free version of Power Automate

Power Automate Desktop is a desktop automation tool, not just a free version of Power Automate. The implementation and licensing terms are different.

Want to directly control PC programs with cloud flows

Cloud flows run in the cloud. Desktop flow is required to click on specific windows or manipulate legacy programs on your local PC.

Check your license later

In practice, this is the most dangerous. If you have everything built and are blocked by premium connectors or Unattended RPA licenses, you may need to redesign the design.

Creating desktop flow only based on personal PC

When it comes to operational automation, you need to think in terms of execution machines, not individual PCs. Screen locks, reboots, user sessions, permissions, and even updates need to be considered.

Conclusion

The difference between Power Automate and Power Automate Desktop is not simply between the web version and the installable app. The key is Cloud automation or desktop RPA?no see.

If you are working on connecting Microsoft 365 services and SaaS, Power Automate cloud flow is the right choice, and if you need to automate repetitive human clicking and input on a Windows PC, Power Automate Desktop is the right choice. It is possible to use the two together, but in that case, the license, machine runtime, network, and execution account must be viewed together.

If you are introducing it for the first time, you can judge it in the order below.

1. 자동화 대상이 클라우드 서비스인가, PC 화면인가?
2. 필요한 커넥터가 Standard인가 Premium인가?
3. 사람이 로그인한 상태에서 실행해도 되는가, 무인 실행이 필요한가?
4. 실패했을 때 누가 확인하고 재실행할 것인가?
5. 조직 정책과 라이선스가 허용하는가?

If you decide on these five things first, it will be much clearer whether you should use Power Automate or Power Automate Desktop.

References

  • Microsoft Learn: Getting started with Power Automate: https://learn.microsoft.com/en-us/power-automate/getting-started
  • Microsoft Learn: Introduction to Desktop flows: https://learn.microsoft.com/en-us/power-automate/desktop-flows/introduction
  • Install Microsoft Learn: Power Automate Desktop: https://learn.microsoft.com/en-us/power-automate/desktop-flows/install
  • Microsoft Learn: Power Platform Licensing Overview: https://learn.microsoft.com/en-us/power-platform/admin/pricing-billing-skus
  • Microsoft Learn: Power Automate Limits: https://learn.microsoft.com/en-us/power-automate/limits-and-config
  • Microsoft Learn: Desktop flows runtime troubleshooting: https://learn.microsoft.com/en-us/power-automate/desktop-flows/troubleshoot