Inside Logic Apps Standard: How Azure Tables Store Your Workflows

Source: Dev.to

Overview

Azure Logic Apps Standard uses Azure Table Storage as its primary persistence layer for:

• Workflow state
• Execution history
• Runtime metadata

This document provides a comprehensive reference to the table architecture, naming conventions, and schema patterns.

Table Categories

Logic Apps Standard organizes data into two distinct table categories:

This separation enables workflow isolation, horizontal scaling, and independent lifecycle management.

Base Tables (App‑Level)

Base tables store metadata that applies to the entire Logic App resource. All workflows within a Logic App share these tables.

Table‑naming pattern

flow{LAIdentifier}{suffix}

Base table types

Example

For a Logic App named OrderProcessing:

LAIdentifier = flow7365adc025615f3

Resulting base tables:

flow7365adc025615f3flows
flow7365adc025615f3flowruntimecontext
flow7365adc025615f3flowaccesskeys
flow7365adc025615f3flowsubscriptions
flow7365adc025615f3flowsubscriptionsummary
flow7365adc025615f3jobdefinitions

Flow Tables (Workflow‑Level)

Flow tables store execution data specific to each workflow. Each workflow gets its own isolated set of tables.

Table‑naming pattern

flow{LAIdentifier}{WFIdentifier}{suffix}

Flow‑table types

Date‑stamped tables

Action‑related tables are partitioned by date for scalability:

{WFIdentifier}yyyyMMddT000000Z{suffix}

Example: 1c859134ef297b720250114T000000Zactions

Example

For workflow ProcessOrder in the OrderProcessing Logic App:

LAIdentifier = flow7365adc025615f3
WFIdentifier = 1c859134ef297b7

Resulting tables:

flow7365adc025615f31c859134ef297b7flows
flow7365adc025615f31c859134ef297b7runs
flow7365adc025615f31c859134ef297b7histories
flow7365adc025615f31c859134ef297b720250114T000000Zactions
flow7365adc025615f31c859134ef297b720250114T000000Zvariables

Table Key Fields

Base Flows Table (Master Registry)

FlowRuntimeContext Table

FlowAccessKeys Table

FlowSubscriptions Table

FlowSubscriptionSummary Table

JobDefinitions Table

This reference is intended for developers, architects, and operations engineers who need to understand or troubleshoot the persistence layer of Azure Logic Apps Standard.

Recurrence & Retry Configuration

Runs Table

Histories Table (Trigger History)

Actions Table

Variables Table

Workflow Flows Table (Per‑Workflow Cache)

Identifier Generation

Logic Apps uses MurmurHash64 for deterministic, collision‑resistant identifier generation.

Algorithm

// Generate Logic App identifier (LAIdentifier)
string laIdentifier = "flow" + MurmurHash64(logicAppName).Substring(0, 15);

// Generate Workflow identifier (WFIdentifier)
string wfIdentifier = MurmurHash64(workflowId).Substring(0, 15);

// Build the complete table name
string tableName = laIdentifier + wfIdentifier + suffix;

Constraints

• Table names: Max 63 characters (Azure Table Storage limit)
• Characters: Lowercase alphanumeric only
• Hash truncation: 15 characters provides sufficient uniqueness

Quick Reference

Table‑Name Format

Base:   flow{LAIdentifier}{suffix}
Flow:   flow{LAIdentifier}{WFIdentifier}{suffix}
Dated:  flow{LAIdentifier}{WFIdentifier}{yyyyMMddT000000Z}{suffix}

Common Suffixes