|
| 1 | +--- |
| 2 | +title: Troubleshoot Azure Logic Apps Setup and Connectivity |
| 3 | +description: This troubleshooting checklist consolidates the required steps for resolving Azure Logic Apps setup and connectivity issues. |
| 4 | +ms.service: azure-logic-apps |
| 5 | +ms.reviewer: xuehongg, shrahman, v-ryanberg, v-gsitser |
| 6 | +ms.topic: troubleshooting |
| 7 | +ms.custom: Networking |
| 8 | +ms.date: 11/5/2025 |
| 9 | +author: JarrettRenshaw |
| 10 | +ms.author: jarrettr |
| 11 | +--- |
| 12 | + |
| 13 | +# Troubleshoot Azure Logic Apps setup and connectivity |
| 14 | + |
| 15 | +This troubleshooting checklist consolidates the required steps for resolving Azure Logic Apps setup and connectivity issues. |
| 16 | + |
| 17 | +## Troubleshooting checklist |
| 18 | + |
| 19 | +### Configure the logic app for VNet integration |
| 20 | + |
| 21 | +Make sure that the logic app is configured correctly for virtual network (VNet) integration: |
| 22 | + |
| 23 | +1. On the Azure portal, navigate to **Logic App > Settings > Networking > Outbound traffic configuration**. |
| 24 | +1. Select **Add virtual network integration**. |
| 25 | +1. Choose a virtual network that includes a subnet without any delegations. For more information, see [Prerequisites](/azure/logic-apps/secure-single-tenant-workflow-virtual-network-private-endpoint#prerequisites). |
| 26 | +1. Add this app setting: **WEBSITE_VNET_ROUTE_ALL = 1**. |
| 27 | + |
| 28 | +### Verify storage account access |
| 29 | + |
| 30 | +Verify that the storage account has the necessary network rules and permissions to allow access from the logic app: |
| 31 | + |
| 32 | +1. Navigate to **Storage Account > Networking > Public network access > Enable from selected networks**. |
| 33 | +1. In **Virtual Networks**, add the logic app subnet. |
| 34 | + |
| 35 | +### Verify that private addresses are returned for endpoints |
| 36 | + |
| 37 | +If private endpoints are enabled, check DNS settings to make sure that private addresses are returned for endpoints. |
| 38 | + |
| 39 | +> [!IMPORTANT] |
| 40 | +> Make sure that you follow these steps if you use your own DNS server instead of Azure DNS. |
| 41 | +
|
| 42 | +1. Create private DNS zones (for example: *privatelink.blob.core.windows.net*). |
| 43 | +1. Link the DNS zones to the VNet. |
| 44 | +1. Add these app settings: |
| 45 | + - **WEBSITE_DNS_SERVER** |
| 46 | + - **WEBSITE_DNS_ALT_SERVER** |
| 47 | +2. Verify these settings by using Kudu together with the `nameresolver` command. |
| 48 | + |
| 49 | +### Enable Allow storage account key access |
| 50 | + |
| 51 | +Enable **Allow storage account key access** in the storage account configuration: |
| 52 | + |
| 53 | +1. Navigate to **Storage Account** > **Configuration**. |
| 54 | +1. Set **Allow storage account key access** to **Enabled**. |
| 55 | + |
| 56 | +### Ensure private endpoint connectivity |
| 57 | + |
| 58 | +Use the built-in connector for Azure Blob Storage to ensure private endpoint connectivity: |
| 59 | + |
| 60 | +1. Navigate to **Workflows**, and select the workflow that you want. |
| 61 | +1. On the workflow menu, select **Designer**. |
| 62 | +1. Select **Built-in > Azure Blob Storage**. |
| 63 | +1. Provide the storage account connection string. |
| 64 | + |
| 65 | +### Switch to built-in connectors |
| 66 | + |
| 67 | +Switch to using built-in connectors for scenarios that require private endpoint access: |
| 68 | + |
| 69 | +1. Select **Built-in connectors** for private endpoint scenarios. |
| 70 | + |
| 71 | +### Route outbound traffic through the VNet |
| 72 | + |
| 73 | +Make sure that the logic app's outbound traffic is correctly routed through the VNet: |
| 74 | + |
| 75 | +1. Select **Route All**. |
| 76 | +1. Associate an Azure Network Address Translation (NAT) Gateway for predictable outbound IPs. |
| 77 | +1. Verify the network security groups (NSG) and user-defined routes (UDR) rules. |
| 78 | + |
| 79 | +### Search for any missing app settings |
| 80 | + |
| 81 | +Check the logic app runtime configuration to determine whether any app settings are missing. |
| 82 | + |
| 83 | +### Deploy single-tenant logic apps that have private storage accounts |
| 84 | + |
| 85 | +If you still experience deployment failures, make sure that your configurations align with the requirements of your specific deployment scenario. For example, you might have to add the following app settings: |
| 86 | + |
| 87 | +- **WEBSITE_CONTENTOVERVNET = 1** |
| 88 | +- **WEBSITE_VNET_ROUTE_ALL = 1** |
| 89 | + |
| 90 | +Additionally, check DNS and host settings. |
| 91 | + |
| 92 | +## References |
| 93 | + |
| 94 | +- [Secure traffic between Standard workflows and virtual networks - Azure Logic Apps](/azure/logic-apps/secure-single-tenant-workflow-virtual-network-private-endpoint) |
| 95 | +- [Deploy Standard logic apps to private storage accounts - Azure Logic Apps](/azure/logic-apps/deploy-single-tenant-logic-apps-private-storage-account) |
| 96 | +- [Install on-premises data gateway for logic app workflows - Azure Logic Apps](/azure/logic-apps/install-on-premises-data-gateway-workflows) |
| 97 | +- [Connect to on-premises data sources - Azure Logic Apps](/azure/logic-apps/connect-on-premises-data-sources?tabs=consumption) |
| 98 | + |
| 99 | +[!INCLUDE [Azure Help Support](~/includes/azure-help-support.md)] |
| 100 | + |
| 101 | +[!INCLUDE [Third-party contact disclaimer](~/includes/third-party-contact-disclaimer.md)] |
0 commit comments