Power Automate

    Power Automate for handovers, approvals and data sync.

    An invoice arrives by email; the flow files it, adds the cost centre and gets the approval in Teams. We set the rules and build error handling your IT can follow.

    For departments and IT who want to automate recurring handovers, approvals and ERP syncs reliably.

    • Power Automate
    • Cloud flows
    • Desktop flows
    • Agent flows
    • Copilot Studio
    • Microsoft Teams
    A funicular station above an Alpine lake, the red car climbs the slope, a Power Automate flow from document to approval to team on the laptop, the robot agent beside it
    01

    Event or schedule

    A new list item starts an approval, an incoming email creates a task, every night a flow syncs data with the ERP. When a step needs judgement, such as classifying a request, an agent takes it on and calls the flow as a tool. We look at frequency, volume and exceptions; for long-running transactions or high-load integrations, we assess Azure Logic Apps or a dedicated interface.

    02

    Cloud flows, desktop flows, agent flows

    We define triggers, conditions, actions and owners. Connections run through agreed service identities, and retries, notifications and logs are set up so that a failure is noticed and can be resolved. The building blocks:

    • Cloud flowsApprovals in Teams and Outlook, notifications, filing and data sync between Microsoft 365 and connected systems.Result: the next step starts as soon as the previous one is done.
    • Desktop flowsAutomation of applications without an interface, attended at the workstation or unattended on a dedicated machine.Result: older business applications become part of the workflow too.
    • Agent flowsWorkflows in Copilot Studio that an agent calls as a tool, or that read documents and draft replies with AI actions.Result: the agent acts by fixed rules, and every run can be traced.
    • ERP syncAbacus and bexio through the connections from the ERP integration, with sync of master data and documents.Result: every value is maintained in one place and is current wherever it is needed.
    • OperationsFlows in solutions, service accounts with limited rights, failure alerts to a named contact, analysis of runs.Result: a failure is noticed before anyone in the business runs into it.
    03

    Licences, accounts, cover

    Flows with standard connectors run with Microsoft 365. Premium connectors, desktop flows and flows in managed environments need Power Automate Premium or a per-flow plan; agent flows consume Copilot Studio capacity. The starting point is a business description of the workflow and access to the source and destination systems; we check API limits and data policies. An automated approval needs a rule for absence and escalation.

    04

    What happens on failure

    We test duplicate triggers, missing data, expired connections and recovery after a failure. Your team checks that a transaction makes only the intended changes. A person is named for changes; Support & Operations can take over day-to-day operations.

    Sound familiar? Tell us where you stand today.

    Contact

    What's new.

    As of: October 2026

    • Since 31 August 2026

      The Power Automate mobile app has been retired.

      Existing flows keep running. The "Send me a mobile notification" action no longer arrives; approvals run through the Approvals app in Teams, through Outlook or the portal in the browser. We replace the action in your flows with messages in Teams or by email.

      Source: Microsoft Learn: Important changes coming in Power Platform
    • As of 18 June 2026

      A cloud flow can be converted into an agent flow, in one direction only.

      Copilot Studio then manages the flow, and every action consumes Copilot Studio capacity. Because the billing changes, the conversion cannot be reversed. When capacity runs out, no new runs start; we plan capacity and pay-as-you-go in advance.

      Source: Microsoft Learn: Agent flows overview
    • As of 31 August 2026

      Cloud flows in managed environments need a premium licence.

      Anyone running a cloud flow there needs Power Automate Premium, Power Apps Premium or a suitable Dynamics 365 licence; alternatively, a per-flow plan covers the workflow. Flows that run from within an app or an agent are covered by that app's or agent's licence.

      Source: Microsoft Learn: Licensing requirements for managed environments

    What IT and the business ask before the first flow.

    Which licence does a flow need?

    Flows with standard connectors such as SharePoint, Outlook and Teams run with the Microsoft 365 licence. Premium connectors, custom connectors and desktop flows need Power Automate Premium per user or a per-flow plan. We assign every flow to a licence before it goes live.

    What happens when the person who built the flow leaves?

    Then the flow must not depend on their account. We keep flows in solutions, give them at least two owners and run connections through service accounts. We regularly check that every flow has an active owner.

    Cloud flow or agent flow?

    A cloud flow fits fixed workflows that run on Power Automate licences. An agent flow fits when an agent calls the workflow as a tool or AI actions are part of it; it consumes Copilot Studio capacity. Converting a cloud flow into an agent flow cannot be reversed, so we decide it based on the workflow.

    What changes for AI actions with AI Builder?

    From 1 November 2026, new and renewed licences no longer include AI Builder credits; credits already purchased continue until the end of the contract term. After that, AI actions in flows consume Copilot Credits, for example when reading invoices. We check which flows use such actions and plan the monthly budget.

    When is Power Automate no longer enough?

    With very many runs, long transactions or interfaces with strict response times. We then assess Azure Logic Apps or a dedicated interface that still uses Power Automate for approvals and notifications. We look up the limits per licence and connector before we build.

    Agree on a useful next step

    Tell us about your current workflow, the systems involved and the result you need. In our first conversation, we identify what else we need to know to plan a useful next step.