Customer-managed persistence for Logic Apps workflows running on hybrid infrastructure
|
Important scope clarification SQL as a storage provider is supported only for Hybrid Logic Apps. It is not supported as a storage provider for regular Azure-hosted Logic Apps Standard. |
We are excited to announce the general availability of SQL as a storage provider for Hybrid Logic Apps, giving organizations greater flexibility and control over how workflow runtime state is persisted when Logic Apps runs on customer-managed infrastructure.
This capability is foundational for customers operating integration workloads in datacenters, edge locations, regulated environments, or other infrastructure where runtime persistence must remain within a customer-managed boundary.
Why SQL storage for Hybrid Logic Apps?
Hybrid Logic Apps enables organizations to run the Logic Apps runtime on their own infrastructure while retaining the familiar Logic Apps development and workflow experience. In this architecture, SQL Server provides the durable persistence layer required by the runtime.
SQL storage persists runtime information such as:
- Workflow runs and execution state
- Actions and triggers
- Jobs and subscriptions
- Runtime context and workflow metadata
- Queue-backed runtime processing
Built for customer-managed environments
SQL storage supports organizations that need to run integration workloads closer to the applications and systems they connect to, while applying established enterprise database practices.
- Infrastructure control: Run workflow workloads within customer-managed environments.
- Data locality: Keep workflow runtime state within the infrastructure boundary managed by the organization.
- Operational consistency: Reuse established SQL Server monitoring, security, backup, and administration practices.
- Enterprise resilience: Apply existing SQL capabilities for availability, failover, backup, restore, and disaster recovery.
- Hybrid flexibility: Run integrations closer to on-premises applications, datacenter systems, and edge workloads.
Runtime-managed SQL schema
Customers do not need to manually create the Logic Apps runtime tables. When the Hybrid Logic Apps runtime starts, it connects to the configured SQL database and validates and initializes the database schema required for workflow execution. The runtime remains responsible for its application-level schema and runtime-managed objects.
|
Treat the runtime schema as platform-owned Do not manually create, change, rename, or drop Logic Apps runtime tables, indexes, stored procedures, or other runtime-managed database objects unless explicitly directed by Microsoft Support. |
Shared responsibility for SQL storage
|
Managed by the Logic Apps runtime |
Managed by the customer |
|
Runtime schema initialization and management |
SQL Server provisioning and capacity planning |
|
Runtime tables and database objects |
Database availability and infrastructure monitoring |
|
Workflow execution-state persistence |
Backup, restore, and disaster recovery |
|
Runtime-managed data-lifecycle operations |
Security, access management, patching, and infrastructure maintenance |
SQL storage is not source control
SQL provides runtime persistence for Hybrid Logic Apps. It is not a replacement for source control or a mechanism for recovering previous versions of workflow definitions. Continue to manage workflow definitions, deployment artifacts, configuration, and infrastructure definitions through established development, source-control, and DevOps practices.
Scope of general availability
|
Deployment model |
SQL as runtime storage provider |
|
Hybrid Logic Apps |
Supported |
|
Azure Workflow Service hosted Logic Apps Standard |
Not supported |
Enabling enterprise integration wherever applications run
For organizations modernizing integration workloads while retaining control over where applications and data run, Hybrid Logic Apps with SQL storage brings together Logic Apps workflow capabilities, customer-managed infrastructure, familiar enterprise database technology, and hybrid deployment flexibility.
We look forward to seeing how customers use Hybrid Logic Apps and SQL Server to modernize integration workloads across datacenters, edge environments, and hybrid architectures.
SQL Server maintenance and operational guidance
For performance benchmarking guidance, refer Hybrid Logic Apps - SQL as storage provider benchmarking | Microsoft Community Hub
Customers manage the underlying SQL Server environment, while the Hybrid Logic Apps runtime manages its schema and workflow execution state. The following practices help maintain a reliable production environment.
1. Monitor database growth and storage utilization
- Monitor database size, free space, storage consumption trends, and transaction log utilization.
- Plan capacity based on workflow execution volume, concurrency, run duration, and workload characteristics.
- Configure alerts before data or log files approach infrastructure capacity limits.
- Do not delete records directly from runtime tables to reclaim space.
2. Configure backups and disaster recovery
- Configure full, differential, and transaction log backups according to the organization’s recovery-point and recovery-time objectives.
- Regularly validate backup integrity and test restore procedures in a nonproduction environment.
3. Monitor SQL Server performance
- Monitor CPU, memory, database I/O latency, transaction log throughput, connection availability, blocking, and deadlocks.
- Provision SQL resources for expected workflow concurrency and peak execution volume, not only average utilization.
- Investigate sustained latency or resource saturation because SQL responsiveness directly affects persistence and retrieval of workflow state.
4. Maintain database and platform health
- Use supported SQL Server integrity checks and monitor database health.
- Review statistics and index health using established SQL Server maintenance practices, without changing runtime-owned object definitions.
- Keep SQL Server and the supporting operating environment current with applicable, supported security and servicing updates.
5. Plan for availability and maintenance windows
- Evaluate supported SQL Server high-availability and disaster-recovery options based on business continuity requirements.
- Validate network connectivity and failover behavior between Hybrid Logic Apps runtime instances and SQL Server.
- Plan database maintenance that requires downtime as a coordinated application maintenance window.
- After maintenance or failover, verify database connectivity and validate that workflow processing has resumed as expected.
6. Establish monitoring and alerting
- Alert on database connectivity failures, high resource utilization, storage pressure, transaction log issues, backup failures, and database availability events.
- Maintain dashboards and runbooks that help operators correlate SQL health with workflow processing symptoms.
References
- Hybrid Logic Apps - SQL as storage provider benchmarking | Microsoft Community Hub
- https://learn.microsoft.com/en-us/azure/logic-apps/set-up-sql-database-storage-standard