Skip to content

Commit 2ddfad3

Browse files
authored
Merge pull request #126107 from SonnyGillissen/patch-2
Update secure-single-tenant-workflow-virtual-network-private-endpoint.md
2 parents 72a0567 + 6def98f commit 2ddfad3

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

articles/logic-apps/secure-single-tenant-workflow-virtual-network-private-endpoint.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -132,6 +132,7 @@ To secure outbound traffic from your logic app, you can integrate your logic app
132132
|-------------|------------------|--------|-------------|----------|---------|
133133
| * | 443 | Subnet integrated with Standard logic app | Storage account | TCP | Storage account |
134134
| * | 445 | Subnet integrated with Standard logic app | Storage account | TCP | Server Message Block (SMB) File Share |
135+
| * | 20000-30000 | Subnet integrated with Standard logic app | Worker process | TCP | Communication between App Service Plan and Standard logic app nodes |
135136

136137
- For Azure-hosted managed connectors to work, you need to have an uninterrupted connection to the managed API service. With virtual network integration, make sure that no firewall or network security policy blocks these connections. If your virtual network uses a network security group (NSG), user-defined route table (UDR), or a firewall, make sure that the virtual network allows outbound connections to [all managed connector IP addresses](/connectors/common/outbound-ip-addresses#azure-logic-apps) in the corresponding region. Otherwise, Azure-managed connectors won't work.
137138

0 commit comments

Comments
 (0)