Skip to content

Commit 50e3152

Browse files
authored
Merge pull request #127730 from jaesoni/agw-vs-slb-update
AGW and SLB comparison update
2 parents e362d16 + 5854f9f commit 50e3152

1 file changed

Lines changed: 16 additions & 1 deletion

File tree

articles/application-gateway/tcp-tls-proxy-overview.md

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: application-gateway
55
author: mbender-ms
66
ms.service: azure-application-gateway
77
ms.topic: concept-article
8-
ms.date: 05/21/2025
8+
ms.date: 10/14/2025
99
ms.author: mbender
1010
# Customer intent: As a network architect, I want to implement TCP/TLS proxy capabilities on an application gateway, so that I can efficiently manage both HTTP and non-HTTP workloads while ensuring secure connections to backend servers.
1111
---
@@ -33,6 +33,21 @@ Process flow:
3333
| [**Azure Load Balancer**](../load-balancer/load-balancer-overview.md) | A pass-through load balancer where a client directly establishes a connection with a backend server selected by the Load Balancer's distribution algorithm. |
3434
| **Azure Application Gateway** | Terminating load balancer where a client directly establishes a connection with Application Gateway and a separate connection is initiated with a backend server selected by Application Gateway's distribution algorithm. |
3535

36+
#### Azure Application Gateway (TLS/TCP proxy)
37+
- **Type** – Layer-4 terminating proxy.
38+
- **Protocols** – Supports TCP or TLS protocols.
39+
- **Versatility** – Use a single endpoint (frontend IP) to serve HTTP and non-HTTP workloads.
40+
- **Scaling** – Configure autoscaling (up to 125 instances) to serve your TCP and TLS traffic.
41+
- **Security through TLS termination** – Simplify security with centralized TLS termination and certificate management ensuring consistent compliance across all applications, including non-HTTP workloads. Seamlessly integrates with Azure Key Vault for secure certificate management.
42+
- **Backend types** – Flexibly connect your applications to backends anywhere; within the same Virtual Network, across peered VNets, through remote FQDNs or IPs, or even via hybrid connectivity to your on-premises servers.
43+
44+
#### Azure Load Balancer
45+
- **Type** – Layer-4 pass-through network device.
46+
- **Protocols** – Supports TCP or UDP protocols.
47+
- **Performance** – Provides low latency and high throughput. Built for millions of simultaneous connections with microsecond-level latency.
48+
- **Scaling** – Handles long-lived connections and scales up to millions of flows for all TCP and UDP applications.
49+
- **Inbound and outbound** – Azure Load Balancer delivers complete traffic control with both inbound and outbound capabilities. Seamlessly connect external clients to your applications, while enabling your backend instances to securely reach the internet and other services.
50+
- **Direct server return** - For the return traffic, the backend instance sends the response packet directly back to the client's IP address, reducing latency and improving performance.
3651

3752
## Features
3853

0 commit comments

Comments
 (0)