HeadlinesBriefing favicon HeadlinesBriefing.com

Azure Logic Apps Compute Units Explained

DEV Community •
×

Azure Logic Apps Standard introduces Compute Units (CU) for horizontal storage scaling. When workflows grow, a single Azure Storage account hits partition limits around 2,000 requests per second, causing throttling. Microsoft suggests a threshold of roughly 100,000 action executions per minute per storage account before considering additional storage accounts to handle the load.

Scale Units allow distribution across up to 32 storage accounts, configured via `host.json`. The architecture uses CU00 as the master for app-level base tables. Workflow metadata like `flows` and `runs` lives in a specific CU assigned at deployment via the `ScaleUnit` field. This assignment is non-deterministic for developers.

Action tables differ significantly: they distribute per-run based on the `RunId-CUXX` suffix. This means a single workflow's actions can span multiple storage accounts. When querying run histories, you must parse the Run ID to find the correct storage endpoint. Ignoring this routing leads to missing data in monitoring tools or export utilities.