Desktop automation and machine boundaries

Home Tools Platforms Power Automate Desktop automation and machine boundaries

Understand a desktop flow’s machine, session, application, and operational requirements.

Workflow & automation · Documented · Documentation checked 2026-10-04

Cloud flows, desktop flows, AI Builder prompts, and Power Platform environments.

Work or school account, licenses, connectors, regional AI capacity, and environment policy affect availability.

The worked example is illustrative and has not been tested in a signed-in product account.

What it does and how it connects

Understand a desktop flow’s machine, session, application, and operational requirements.

Desktop flows automate actions in a machine session, unlike cloud connector calls. Installed client, machine registration, user/session access, and attended or unattended setup affect execution. Screen automation is sensitive to application state and UI changes.

Walkthrough

Use the product named in the access panel. The steps below combine documented controls with the editorial example.

  1. Follow the supported desktop setup and create a sample flow on a permitted machine.
  2. Use a harmless local application or test file, not production accounts.
  3. Record or add the documented actions and explicit input / output handling.
  4. Run in the intended session and inspect actual application state and output.

Worked example

Populate a fictional workshop checklist in a local sample app. Avoid real registration systems. Test the app being absent or a dialog unexpectedly appearing, so the flow cannot continue blindly into the wrong screen.

Illustrative desktop-flow contract
Approved machine and sample app only
Input: fictional checklist
Before action: verify expected window / record
Output: new draft file
Unexpected dialog, missing app, or wrong record: stop
No production credentials or outbound actions

Inspect and verify the result

Inspect the actual window and resulting file. Test an unexpected UI state and confirm the flow stops. Check session and machine identity rather than assuming the same behavior as your interactive desktop.

Limits and troubleshooting

UI changes, locked sessions, and inaccessible applications can break RPA. Attended and unattended licensing / machine setup differ. Do not replace a stable supported connector with screen automation without a concrete need.

Data, permissions, and actions

A desktop flow can act with the session’s application privileges. Credentials, screenshots, and machine logs need protection. Apply documented machine and tenant governance and define a recovery process for interrupted actions.

Environments, data policies, and governance

Check which connectors may exchange information before activating an AI-enabled flow.

Explore Environments, data policies, and governance

From an AI prompt to a human-approved action

Place a reviewed draft between AI interpretation and a consequential cloud-flow action.

Explore From an AI prompt to a human-approved action

A desktop draft task with a safe failure path

Create a new draft in a sample desktop application under explicit machine boundaries.

Explore A desktop draft task with a safe failure path

Permissions and meaningful approvals

Decide what a system may read, what it may change, and when someone needs to authorize a concrete action.

Explore Permissions and meaningful approvals

Sources and verification

Documentation checked 2026-10-04. Examples are illustrative unless described otherwise.

Create a desktop flow · Microsoft

Desktop flow governance · Microsoft

Share this page