Azure Logic Apps traditionally rely on Azure Storage to manage workflow states and runtime data. However, with the introduction of SQL as a storage provider (currently in preview), developers now have a compelling alternative that offers greater control, flexibility, and integration with existing SQL infrastructure. This post explores the benefits, configuration steps, and considerations for using SQL storage with Standard Logic Apps.
Logic Apps uses Azure Storage by default to hold workflows, states and runtime data. However, now in preview, you can use SQL storage instead of Azure Storage for your logic apps workflow related transactions.
Note that Azure Storage is still required and SQL is only an alternative for workflow transactions.
Why Use SQL Storage?
| Benefit | Description |
|---|---|
| Portability | SQL runs on VMs, PaaS, and containers—ideal for hybrid and multi-cloud setups. |
| Control | Predictable pricing based on usage. |
| Reuse Assets | Leverage SSMS, CLI, SDKs, and Azure Hybrid Benefits. |
| Compliance | Enterprise-grade backup, restore, failover, and redundancy options. |
When to Use SQL Storage
| Scenario | Recommended Storage |
|---|---|
| Need control over performance | SQL |
| On-premises workflows (Azure Arc) | SQL |
| Predictable cost modeling | SQL |
| Prefer SQL ecosystem | SQL |
| Reuse existing SQL environments | SQL |
| General-purpose or default use cases | Azure Storage |
Configuration via Azure Portal
Prerequisites:
- Azure Subscription
- Azure SQL Server and Database
Azure SQL Setup:
- From your Azure SQL server, navigate to Security > Networking > Public Access > select "Selected networks".
- Scroll down and enable “Allow Azure services and resources…”.
- Navigate to Settings > Microsoft Entra ID > Ensure “Microsoft Entra authentication only” is unchecked.
Note: this can be done during SQL server creation from the Networking tab.
Standard Logic App Setup:
- From your Azure Portal, create a new Logic App (Standard).
- In the Storage tab, select SQL from the dropdown.
- Add your SQL connection string.
Verification Tip: After deployment, check your logic apps environment variable 'Workflows.Sql.ConnectionString' to confirm the SQL DB name is reflected.
Known Issues & Fixes
| Issue | Fix |
|---|---|
| Could not find a part of the path 'C:\home\site\wwwroot' | Re-enable SQL authentication and verify path settings. |
| SQL login error due to AAD-only authentication |
Navigate to Settings > Microsoft Entra ID > Ensure “Microsoft Entra authentication only” is unchecked. |
Final Thoughts
SQL as a storage provider for Logic Apps opens up new possibilities for hybrid deployments, performance tuning, and cost predictability. While still in preview, it’s a promising option for teams already invested in the SQL ecosystem. If you are already using this as an alternative or think this would be useful, let us know in the comments below.
Resources
Microsoft