Five patterns that hold up at enterprise volume
Most Power Automate failures EPC Group is asked to fix share a root cause: a flow that worked for one team was promoted to an enterprise process without changing how it was built. It ran under the author's personal account, had no error path, looped over every SharePoint item on each run, and lived outside a solution. The enterprise version of the same flow applies five patterns. It runs on the right engine, under a non-human identity, inside try-catch scopes, within the request and connector limits Microsoft documents, and inside a solution that moves through environments with connection references and environment variables. The sections below take each pattern in turn with the Microsoft documentation behind it. They are the standards EPC Group's Power Platform consulting practice applies to SharePoint, Dataverse and Azure integrations, whether the flow is new or inherited.
Cloud flows, desktop flows or Azure Logic Apps
Cloud flows call connectors and APIs. Desktop flows bring robotic process automation to Power Automate: they record and play back user interface actions such as clicks and keyboard input for applications that don't have complete APIs (Microsoft Learn, Core components for Power Automate RPA SAP GUI automation, accessed 2026-10-20). Unattended desktop flows need the Power Automate Process plan, run in a remote desktop session that Power Automate creates on the target machine, and cannot run on Windows 10 or Windows 11 devices that have any active user session, even a locked one (Microsoft Learn, Run unattended desktop flows, accessed 2026-10-20). Desktop flows are therefore the exception, used only where no API exists.
The second decision is Power Automate or Azure Logic Apps. Microsoft describes both as designer-first platforms with overlapping connectors, positions Power Automate for business users, office workers and citizen developers, and positions Logic Apps for integrations ranging from little-code to codeful workflows, including B2B processes and enterprise interactions with Azure DevOps; a Power Automate flow can call a Logic Apps workflow, and Logic Apps can call Azure Functions (Microsoft Learn, Choose the right integration and automation services in Azure, accessed 2026-10-20). Microsoft's capability comparison lists managed identity, virtual network integration and private endpoints for Logic Apps (Standard), and rates its scalability for large-scale, high-throughput workflows against small to medium scale for Power Automate (Microsoft Learn, Power Automate migration to Azure Logic Apps (Standard), accessed 2026-10-20). EPC Group keeps approvals, notifications and SharePoint document processes in Power Automate, and moves system-to-system integrations that need network isolation or sustained volume to Logic Apps through its Azure cloud services practice.
Identity: service principals, not personal connections
A flow owned by a person breaks when that person changes a password, loses MFA registration or leaves. Microsoft's guidance is to use service principals for flow ownership and for creating connections whenever possible; a service principal is created as an application user, which can own flows and have connections shared with it, and secrets belong in environment variables rather than hard-coded values in the flow definition (Microsoft Learn, Keep flow configuration generic, accessed 2026-10-20). Microsoft also recommends a Microsoft Entra service principal over a shared service account, and notes that one Power Automate Premium license on an account that many users share is multiplexing and not compliant (Microsoft Learn, Power Automate licensing FAQ, accessed 2026-10-20). Licensing follows the identity: a service principal flow draws on the tenant's non-licensed request pool, which for Power Automate is 25,000 base requests per 24 hours, unless it has a Process license, belongs to a licensed flow group or has a designated licensed user (Microsoft Learn, Requests limits and allocations, accessed 2026-10-20).
Error handling and retries
Every production flow EPC Group ships has an explicit failure path. Microsoft's pattern is to place the main actions in a Try scope, add a Catch scope configured with Run after to execute when Try fails, filter the output of the result() function to find the action that failed, and use the workflow() function to build a link to the run for the notification or the error log. For transient faults, Microsoft prefers exponential retry policies, set per action, over fixed intervals (Microsoft Learn, Employ robust error handling, accessed 2026-10-20). The defaults matter when sizing retries: for medium and high performance profiles the default policy sends up to 12 retries at exponentially increasing intervals, a custom policy allows up to 90 attempts with delays between five seconds and one day, and a flow whose trigger or actions fail continuously for 14 days is turned off (Microsoft Learn, Limits of automated, scheduled, and instant flows, accessed 2026-10-20). Retries also count against request limits, so EPC Group caps them and writes each Catch result to a Dataverse log table that support staff can query.
Request limits, connector throttling and SharePoint
Two kinds of limit apply. Power Platform request limits count every trigger and action, successful or failed, plus retries and pagination. The official limit is 40,000 requests per 24 hours for a Power Automate Premium user; a Process license gives a single flow 250,000 requests per 24 hours and can be stacked up to 10 times; a flow group shares one Process license across up to 25 solution-aware flows; and a five-minute limit of 100,000 requests applies regardless of license. Microsoft notes that organizations are in a transition period in which Premium limits are applied per cloud flow and advises designing for the per-user limits (Microsoft Learn, Requests limits and allocations, accessed 2026-10-20). Connector limits apply in addition: the SharePoint connector allows 600 operations per minute per connection, shared across every flow using that connection, and returns HTTP 429 when exceeded (Microsoft Learn, Power Automate licensing FAQ, accessed 2026-10-20). EPC Group designs SharePoint flows with trigger conditions so they run only on relevant changes, OData filters instead of looping over whole lists, and Dataverse for transactional data that outgrows a list.
Moving flows between environments
Flows that leave development travel inside solutions. Solution-aware cloud flows add versioning and environment variables, and a user can own any number of them, against a maximum of 600 non-solution flows (Microsoft Learn, Understand the benefits of using solution-aware cloud flows, accessed 2026-10-20). Environment variables and connection references carry the values that differ between development, test and production; Microsoft notes that a value changed directly in an environment, rather than through a solution import, reaches a flow only after it is saved or turned off and on again (Microsoft Learn, Use environment variables in Power Automate solution cloud flows, accessed 2026-10-20). Pipelines in Power Platform deploy the managed solution with its connection references and environment variables, validate them before deployment and push the same artifact through each stage (Microsoft Learn, Overview of pipelines in Power Platform, accessed 2026-10-20). EPC Group's Power Platform CoE service configures those pipelines alongside the environment model.
Documented work
ANON-CASES: EPC Group engagement data for Power Automate integration covers mid-size and large construction and manufacturing organizations moving approval, document control and field-reporting flows from personal ownership in the default environment to service principal ownership, try-catch error handling and solution-based promotion, with high-volume integrations moved to Azure Logic Apps, delivered by the firm's Power Platform consulting practice. Client names are not published here. Engagements are described by industry and organization size only, and no outcome figures are quoted that cannot be traced to a signed deliverable. EPC Group is a Microsoft Solutions Partner with all six Solutions Partner Designations as of October 2026.
Primary sources
- Choose the right integration and automation services in Azure — Microsoft Learn, accessed 2026-10-20
- Power Automate migration to Azure Logic Apps (Standard) — Microsoft Learn, accessed 2026-10-20
- Core components for Power Automate RPA SAP GUI automation — Microsoft Learn, accessed 2026-10-20
- Run unattended desktop flows — Microsoft Learn, accessed 2026-10-20
- Keep flow configuration generic — Microsoft Learn, accessed 2026-10-20
- Power Automate licensing FAQ — Microsoft Learn, accessed 2026-10-20
- Employ robust error handling — Microsoft Learn, accessed 2026-10-20
- Limits of automated, scheduled, and instant flows — Microsoft Learn, accessed 2026-10-20
- Requests limits and allocations — Microsoft Learn, accessed 2026-10-20
- Understand the benefits of using solution-aware cloud flows — Microsoft Learn, accessed 2026-10-20
- Use environment variables in Power Automate solution cloud flows — Microsoft Learn, accessed 2026-10-20
- Overview of pipelines in Power Platform — Microsoft Learn, accessed 2026-10-20
Frequently Asked Questions
Cloud flows, desktop flows or Logic Apps: how do you choose?
Use a cloud flow when the systems involved have connectors or APIs; use a desktop flow when an application has no usable API and the work has to be done through its user interface, which is what desktop flows automate (Microsoft Learn, Core components for Power Automate RPA SAP GUI automation, accessed 2026-10-20). Microsoft positions Power Automate for business users and citizen developers and Azure Logic Apps for integrations that grow into codeful, B2B or Azure DevOps scenarios, and a flow can call a Logic Apps workflow (Microsoft Learn, Choose the right integration and automation services in Azure, accessed 2026-10-20). EPC Group moves high-volume or network-isolated integrations to Logic Apps (Standard).
How should flows authenticate: service accounts or service principals?
Microsoft recommends a Microsoft Entra service principal as the flow owner rather than a shared service account, because shared credentials are a security risk and make it hard to track who changed a flow; assigning one Premium license to a service account that many users share is multiplexing and is not compliant (Microsoft Learn, Power Automate licensing FAQ, accessed 2026-10-20). A service principal is set up as an application user, which can own flows and have connections shared with it (Microsoft Learn, Keep flow configuration generic, accessed 2026-10-20). EPC Group uses service principal connections for production flows and keeps personal connections in development only.
How are errors handled and retried?
Microsoft recommends grouping actions into a Try scope and adding a Catch scope configured with Run after to execute when Try fails, using the result() function to find the failed action and workflow() to build a link to the run; it also prefers exponential retry policies over fixed intervals for transient failures (Microsoft Learn, Employ robust error handling, accessed 2026-10-20). The default policy for most flows sends up to 12 retries at exponentially increasing intervals, and a custom policy allows up to 90 attempts with a maximum delay of one day (Microsoft Learn, Limits of automated, scheduled, and instant flows, accessed 2026-10-20). EPC Group logs every Catch to a Dataverse table.
What are the request limits and how are they avoided?
Every trigger and action counts as a Power Platform request, including failed actions, retries and pagination. The official limit is 40,000 requests per 24 hours per Power Automate Premium user, a Process license gives one flow 250,000 and can be stacked up to 10 times, and a five-minute limit of 100,000 applies regardless of license (Microsoft Learn, Requests limits and allocations, accessed 2026-10-20). Connectors add their own limits: the SharePoint connector allows 600 operations per minute per connection and returns HTTP 429 when exceeded (Microsoft Learn, Power Automate licensing FAQ, accessed 2026-10-20). EPC Group filters at the trigger, batches with queries and spreads load across connections.
How are flows moved between environments?
Flows move inside solutions. Solution-aware cloud flows support versioning and environment variables, and a user can own any number of them, against a maximum of 600 non-solution flows (Microsoft Learn, Understand the benefits of using solution-aware cloud flows, accessed 2026-10-20). Connection references and environment variables are set per environment on import; a value changed directly in an environment rather than through solution import takes effect only after the flow is saved or turned off and on again (Microsoft Learn, Use environment variables in Power Automate solution cloud flows, accessed 2026-10-20). EPC Group promotes managed solutions through pipelines in Power Platform.
Talk to a senior architect
If your critical flows still run under personal accounts with no error path, a 30-minute discovery call with a senior EPC Group architect reviews them against these five patterns and identifies which belong in Azure Logic Apps. See the Power Platform consulting service hub for engagement structures.
Email contact@epcgroup.net or call 888-381-9725.
a Microsoft Gold Partner (2000 until Microsoft retired the program in 2022) — today holding all six Microsoft Solutions Partner Designations.
Related reading
- Anonymized engagement summary: generative AI for contract audits and policy drafting at a public transit district (2023)
- Anonymized engagement summary: a Power Apps and Power Automate task-automation program, including a well-test editing app on SQL, for an oil and gas producer (2020)
- Anonymized engagement summary: Dynamics 365 CRM security-model, data-model and Unified Interface remediation after an EPC Group assessment, for a professional association (2021)
- Anonymized engagement summary: a Dynamics 365 CRM platform for a law firm's IT operations — onboarding, assets, configuration, cases, scheduling, change and vendors (2020)