Skip to content

Commit 66f1139

Browse files
authored
Line 137: Event hub/Event hubs
1 parent 6e3bd3f commit 66f1139

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/logic-apps/connect-virtual-network-vnet-isolated-environment.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -134,7 +134,7 @@ This table describes the ports that your ISE requires to be accessible and the p
134134
| * | 443 | **VirtualNetwork** | **AzureMonitor** | Publish diagnostic logs & metrics ||
135135
| * | 1433 | **VirtualNetwork** | **SQL** | Azure SQL dependency ||
136136
| * | 1886 | **VirtualNetwork** | **AzureMonitor** | Azure Resource Health | Required for publishing health status to Resource Health. |
137-
| * | 5672 | **VirtualNetwork** | **EventHub** | Dependency from Log to Event Hub policy and monitoring agent ||
137+
| * | 5672 | **VirtualNetwork** | **EventHub** | Dependency from Log to Event Hubs policy and monitoring agent ||
138138
| * | 6379 - 6383, plus see **Notes** | **VirtualNetwork** | **VirtualNetwork** | Access Azure Cache for Redis Instances between Role Instances | For ISE to work with Azure Cache for Redis, you must open these [outbound and inbound ports described by the Azure Cache for Redis FAQ](../azure-cache-for-redis/cache-how-to-premium-vnet.md#outbound-port-requirements). |
139139
| * | 53 | **VirtualNetwork** | IP addresses for any custom Domain Name System (DNS) servers on your virtual network | DNS name resolution | Required only when you use custom DNS servers on your virtual network |
140140

0 commit comments

Comments
 (0)