Skip to content

Commit 27b6ec3

Browse files
committed
content fixes to public-network
1 parent 4870748 commit 27b6ec3

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/modeling-simulation-workbench/how-to-guide-public-network.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -19,15 +19,15 @@ In Azure Modeling and Simulation Workbench, you can deploy a [connector](./conce
1919
Public connectors aren't recommended for use in scenarios in which the organization:
2020

2121
* Has complex network and security infrastructure
22-
* Uses proxies, especially
23-
* Requires users to access corporate resources through managed VPN user endpoints before accessing internet accessible zones
24-
* Has requirements to individually catalog cloud provider endpoints
22+
* Uses proxies, especially managed services with large number of exit nodes shared with other customers
23+
* Requires users to access corporate resources through managed VPN before accessing the internet or cloud services
24+
* Has requirements to individually catalog cloud service IP addresses
2525
* Has restrictions on the use of nonstandard destination ports
26-
* Frequently rotates externally facing IP addresses, either via intentionally short DHCP leases or rotating exit IPs
27-
* Requires firewalls or custom network security at the permiter
26+
* Frequently rotates externally facing IP exit addresses, either through intentionally short DHCP leases or random exit IPs
27+
* Requires firewalls or custom network security at the permiter for cloud services
2828
* Requires all cloud services to be connected to a virtual network
2929

30-
If the above situations apply, a [private networking connector](how-to-guide-private-network.md) is recommended instead.
30+
If these situations apply, a [private networking connector](how-to-guide-private-network.md) is recommended instead.
3131

3232
## Prerequisites
3333

@@ -104,7 +104,7 @@ $connectorProperties.networkAcls
104104

105105
## Immediately terminate access
106106

107-
Deleting an IP address from the connector allowlist doesn't terminate active sessions. Only new, previously unestablished sessions are denied. To immediately terminate a session from an IP address or range, [delete](#add-edit-or-delete-ip-addresses-or-ranges) the address entry from the allowlist, submit the changes, then [restart the connector](./how-to-guide-start-stop-restart.md#restart-a-chamber-connector-or-vm).
107+
Deleting an IP address from the connector allowlist doesn't terminate active sessions. Only new, unestablished sessions are denied. To immediately terminate a session from an IP address or range, [delete](#add-edit-or-delete-ip-addresses-or-ranges) the address entry from the allowlist, submit the changes, then [restart the connector](./how-to-guide-start-stop-restart.md#restart-a-chamber-connector-or-vm).
108108

109109
## Idle the connector
110110

0 commit comments

Comments
 (0)