Skip to content

Commit 7f36a44

Browse files
committed
edits
1 parent d03ff6b commit 7f36a44

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/spring-apps/troubleshooting-vnet.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -67,15 +67,15 @@ For more information, see [Access your application in a private network](./acces
6767

6868
Azure Spring Apps supports exposing applications to the internet by using public endpoints. For more information, see [Expose applications on Azure Spring Apps to the internet from a public network](how-to-access-app-from-internet-virtual-network.md).
6969

70-
If you're using a user defined route feature, the following features aren't supported because of asymmetric routing:
70+
If you're using a user defined route feature, some features aren't supported because of asymmetric routing. For unsupported features, use the following list:
7171

7272
- Use public network to access the application through public endpoint.
7373
- Use public network to access the log stream.
7474
- Use public network to access the App console.
7575

7676
For more information, see [Control egress traffic for an Azure Spring Apps instance](how-to-create-user-defined-route-instance.md).
7777

78-
The same limitations also apply to Azure Spring Apps when egress traffics are routed to a firewall. The problem occurs because both situations introduce asymmetric routing into the cluster. Packets arrive on the endpoint's public IP address but return to the firewall via the private IP address. So, the firewall must block such traffic. For more information, see [Bring Your Own Route Table](how-to-deploy-in-azure-virtual-network.md#bring-your-own-route-table).
78+
Similar limitations also apply to Azure Spring Apps when egress traffics are routed to a firewall. The problem occurs because both situations introduce asymmetric routing into the cluster. Packets arrive on the endpoint's public IP address but return to the firewall via the private IP address. So, the firewall must block such traffic. For more information, see [Bring your own route table](how-to-deploy-in-azure-virtual-network.md#bring-your-own-route-table).
7979

8080
If you're routing egress traffics to a firewall but also need to expose the application to internet, use the expose applications to the internet with TLS Termination feature. For more information, see [Expose applications to the internet with TLS Termination at Application Gateway](expose-apps-gateway-tls-termination.md).
8181

0 commit comments

Comments
 (0)