Skip to content

Commit 09e9c7c

Browse files
committed
Correct source/destination
1 parent f15ea2f commit 09e9c7c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -128,8 +128,8 @@ To secure outbound traffic from your logic app, you can integrate your logic app
128128

129129
| Source port | Direction | Protocol | Source / Destination | Purpose |
130130
|-------------|-----------|----------|----------------------|---------|
131-
| 443 | Outbound | TCP | Private endpoint / Storage account | Storage account |
132-
| 445 | Outbound | TCP | Private endpoint / Subnet integrated with Standard logic app | Server Message Block (SMB) File Share |
131+
| 443 | Outbound | TCP | Subnet integrated with Standard logic app / Storage account | Storage account |
132+
| 445 | Outbound | TCP | Subnet integrated with Standard logic app / Storage account | Server Message Block (SMB) File Share |
133133

134134
- 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.
135135

0 commit comments

Comments
 (0)