Skip to content

Commit f7555db

Browse files
genlingenlin
committed
add a new article for logic app
1 parent 163318d commit f7555db

2 files changed

Lines changed: 139 additions & 0 deletions

File tree

‎support/azure/logic-apps/common-error-deploy-logic-apps-private-storage-account.md‎

Lines changed: 96 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,96 @@
1+
---
2+
title: Deploy Standard logic apps to private storage accounts
3+
description: Deploy Standard logic app workflows to Azure storage accounts that use private endpoints and deny public access.
4+
services: logic-apps
5+
ms.suite: integration
6+
ms.reviewer: estfan, azla
7+
ms.custom: sap:Connectors
8+
# Customer intent: As a developer, I want to deploy Standard logic apps to Azure storage accounts that use private endpoints.
9+
---
10+
11+
# Deploy single-tenant Standard logic apps to private storage accounts using private endpoints
12+
13+
[!INCLUDE [logic-apps-sku-standard](../../includes/logic-apps-sku-standard.md)]
14+
15+
When you create a single-tenant Standard logic app resource, you're required to have a storage account for storing logic app artifacts. You can restrict access to this storage account so that only the resources inside a virtual network can connect to your logic app workflow. Azure Storage supports adding private endpoints to your storage account.
16+
17+
This article describes the common error that may happen when you deploy such logic apps to protected private storage accounts.
18+
19+
## Troubleshoot common errors
20+
21+
The following errors commonly happen with a private storage account that's behind a firewall and indicate that the logic app can't access the storage account services.
22+
23+
| Problem | Error |
24+
|---------|-------|
25+
| Access to the `host.json` file is denied | `"System.Private.CoreLib: Access to the path 'C:\home\site\wwwroot\host.json' is denied."` |
26+
| Unable to connect to file share | `"System.Private.CoreLib: The network path was not found: 'C:\home\data\Functions\secrets\Sentinels'."` |
27+
| Unable to authenticate to file share | `"System.Private.CoreLib: The user name or password is incorrect: 'C:\home\data\Functions\secrets\Sentinels'."` |
28+
| Error building configuration in an external startup class | `"System.Private.CoreLib: Could not find a part of the path 'C:\home\site\wwwroot'."` |
29+
| Can't load workflows in the logic app resource | `"Encountered an error (ServiceUnavailable) from host runtime."` |
30+
31+
To help you troubleshoot these problems and find the root cause, follow these steps:
32+
33+
1. In the Azure portal, make sure that the storage account and file share still exist.
34+
35+
1. On the logic app resource menu, under **Settings**, select **Environment variables**.
36+
37+
1. On the **App settings** tab, find the settings named **WEBSITE_CONTENTAZUREFILECONNECTIONSTRING** and **WEBSITE_CONTENTSHARE**.
38+
39+
1. Check that these settings specify the correct storage account and file share, respectively. Make sure no spelling errors exist.
40+
41+
1. On the logic app resource menu, select **Diagnose and solve problems**. Find and run the following detectors: **Logic App Down or Reporting Errors** and **Network Troubleshooter**
42+
43+
These detectors provide insights and suggestions for fixing the problem.
44+
45+
The following list includes more troubleshooting actions that you can take to find the cause:
46+
47+
> [!NOTE]
48+
>
49+
> Your logic app resource and workflows aren't running when these errors occur,
50+
> so you can't use the Kudu console debugging capability in Azure for troubleshooting.
51+
52+
53+
- Create an Azure virtual machine (VM) inside a different subnet within the same virtual network that's integrated with your logic app. Try to connect from the VM to the storage account.
54+
55+
- Check access to the storage account services by using the [Storage Explorer tool](https://azure.microsoft.com/features/storage-explorer/#overview).
56+
57+
If you find any connectivity issues using this tool, continue with the following steps:
58+
59+
1. From the command prompt, run `nslookup` to check whether the storage services resolve to the private IP addresses for the virtual network:
60+
61+
`C:\>nslookup {storage-account-host-name} [optional-DNS-server]`
62+
63+
1. Check all the storage services:
64+
65+
`C:\nslookup {storage-account-host-name}.blob.core.windows.net`
66+
67+
`C:\nslookup {storage-account-host-name}.file.core.windows.net`
68+
69+
`C:\nslookup {storage-account-host-name}.queue.core.windows.net`
70+
71+
`C:\nslookup {storage-account-host-name}.table.core.windows.net`
72+
73+
1. If these DNS queries resolve, run `psping` or `tcpping` to check traffic to the storage account over port 443:
74+
75+
`C:\psping {storage-account-host-name} {port} [optional-DNS-server]`
76+
77+
1. Check all the storage services:
78+
79+
`C:\psping {storage-account-host-name}.blob.core.windows.net:443`
80+
81+
`C:\psping {storage-account-host-name}.queue.core.windows.net:443`
82+
83+
`C:\psping {storage-account-host-name}.table.core.windows.net:443`
84+
85+
`C:\psping {storage-account-host-name}.file.core.windows.net:445`
86+
87+
1. If the queries resolve from the VM, continue with the following steps:
88+
89+
1. In the VM, find the DNS server that's used for resolution.
90+
91+
1. In your logic app, [find and set the `WEBSITE_DNS_SERVER` app setting](edit-app-settings-host-settings.md?tabs=azure-portal?tabs=azure-portal#manage-app-settings---localsettingsjson) to the same DNS server value that you found in the previous step.
92+
93+
1. Check that the virtual network integration is set up correctly with the appropriate virtual network and subnet in your logic app.
94+
95+
96+
[!INCLUDE [Azure Help Support](../../includes/azure-help-support.md)]

‎support/azure/logic-apps/index.yml‎

Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
### YamlMime:Landing
2+
3+
title: Azure Logic Apps documentation # < 60 chars
4+
summary: Build automated scalable workflows, business processes, and enterprise orchestrations to integrate your apps and data across cloud services and on-premises systems. # < 160 chars
5+
6+
metadata:
7+
title: Azure Logic Apps documentation
8+
description: Build automated scalable workflows, business processes, and enterprise orchestrations to integrate your apps and data across cloud services and on-premises systems.
9+
ms.service: azure-logic-apps
10+
ms.topic: landing-page
11+
author: genlin
12+
ms.author: genli
13+
ms.date: 03/27/2025
14+
15+
# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
16+
17+
landingContent:
18+
# Cards and links should be based on top customer tasks or top subjects
19+
# Start card title with a verb
20+
# Card (optional)
21+
- title: Azure Logic Apps troubleshooting
22+
linkLists:
23+
- linkListType: overview
24+
links:
25+
- text: What is Azure Logic Apps?
26+
url: logic-apps-overview.md
27+
28+
- title: More information
29+
linkLists:
30+
- linkListType: reference
31+
links:
32+
- text: Service limits and configuration
33+
url: logic-apps-limits-and-config.md
34+
- text: Pricing model
35+
url: logic-apps-pricing.md
36+
- text: Azure CLI - Consumption
37+
url: /cli/azure/logic
38+
- text: Azure CLI - Standard
39+
url: /cli/azure/logicapp
40+
- text: Azure PowerShell
41+
url: /powershell/module/az.logicapp/
42+
- text: REST API
43+
url: /rest/api/logic/

0 commit comments

Comments
 (0)