Automate business processes
Automate repeatable work with rules-based flows first (Power Automate cloud and desktop flows, Azure Logic Apps), and add AI steps or agents only where inputs are messy or a step needs judgment.
The problem
Much office work is copying data between systems, chasing approvals and rekeying documents into old applications that have no API. Each manual handoff adds delay and errors.
The newer temptation is to hand everything to an AI agent. Microsoft's own guidance says fixed, rule-based steps are faster, cheaper and more reliable as regular automation, so the real question is where AI adds something a flow cannot.12
The approach
Map the process and mark each step as fixed (same rules every time) or variable (needs reading, interpretation or judgment).
- Fixed steps in Microsoft 365 and SaaS apps: Power Automate cloud flows, triggered by an event, a button or a schedule, using connectors. Copilot can draft a flow from a description in the new designer.
- Legacy desktop or terminal applications: Power Automate desktop flows (RPA) that work through UI elements, images or coordinates.
- Enterprise integration: Azure Logic Apps, with more than 1,400 prebuilt connectors and B2B standards such as AS2, EDIFACT and X12.
- Steps that need judgment: Copilot Studio workflows and agent flows, which can call an agent, run prompts and include human review; or Logic Apps agentic workflows. For code-first teams, Microsoft Agent Framework workflows give explicit control over execution order.
Govern makers with Power Platform Managed Environments: sharing limits, data policies, pipelines and usage insights. Microsoft says unmanaged developer environments are deprecated and need Managed Environments enabled before 15 December 2026.
When a simpler route is enough: a single scheduled flow or a small function. Microsoft's agent guidance says to write a function when a function can do the job.134567
Conceptual architecture
Diagram as a list
Copilot & business apps
- Triggers: events, schedules, buttonsStart the processConnects to Power Automate cloud flows
- Human review and approvalsApprove or correct consequential stepsConnects to Business systems: Dataverse, Dynamics 365, SharePoint, ERP
Agents & automation
- AI step: Copilot Studio agent or agent flowHandles reading, classification or judgment within the flowConnects to Human review and approvals
Data & analytics
- Business systems: Dataverse, Dynamics 365, SharePoint, ERPSystems of record that the process updates
Developer tools
- Power Automate cloud flowsRun fixed steps across connected apps
- Power Automate desktop flowsAutomate legacy desktop and terminal apps through the UIConnects to Business systems: Dataverse, Dynamics 365, SharePoint, ERP
- Azure Logic AppsEnterprise and B2B integration workflows
Security, identity & governance
- Managed Environments and data policiesControl sharing, connectors and deployment
Technologies and their roles
Microsoft Power Platform7
Low-code automation
Power Automate cloud and desktop flows cover connector-based and UI-based automation, governed by Managed Environments.
Microsoft Copilot Studio5
AI steps and workflows
Workflows and agent flows combine agents, tools and logic with human-in-the-loop controls.
Microsoft Agent Framework6
Code-first workflows
Graph-based workflows connect agents and functions through explicit execution paths.
What you need first7
- A process map that separates fixed steps from steps that need judgment
- Connectors or APIs for each system, or desktop access for RPA where no API exists
- Power Platform or Copilot Studio licenses for makers and users of the flows
- Managed Environments and data policies set up before makers publish
- An owner for each flow and a place to log failures
Risks and how to reduce them
- AI used for steps that rules would handle2
- Keep fixed steps in flows and reserve agents for variable input, as Microsoft's agent guidance advises.
- Desktop flows break when an application screen changes
- Prefer connectors or APIs where they exist and test desktop flows after each application update.
- Unmanaged sprawl of maker flows7
- Enable Managed Environments, limit sharing and apply data policies on connectors.
- Data residency questions for AI steps4
- Check where models run; Microsoft notes that agents in Logic Apps Consumption can use an Azure OpenAI model from any region.
Documented examples
Direct pojišťovna (part of the Direct group)
In productionDirect pojišťovna: AI agents for windshield claims
15 minutes to about 2 minutes (87% less) (measured)
Financial services, Czechia
Banco Popular Dominicano
In productionBanco Popular Dominicano: AURA agents for operational risk
100% coverage (measured)
Financial services, Dominican Republic
EY
ScalingEY: Dynamics 365 Sales with agents, and Copilot across the firm
85,000 in 18 months; goal 100,000 (measured)
Professional services, Global
Related
Sources
- Introduction to desktop flows (opens in a new tab)
- Business plan for AI agents (Cloud Adoption Framework) (opens in a new tab)
- Overview of cloud flows: Power Automate (opens in a new tab)
- What is Azure Logic Apps? (opens in a new tab)
- Overview: Microsoft Copilot Studio (opens in a new tab)
- Microsoft Agent Framework overview (opens in a new tab)
- Managed Environments overview (opens in a new tab)
Thank you. Your correction was sent.
The editors check it against the sources. If you left an email address, they may reply about it.