Skip to content

Commit e283242

Browse files
Merge pull request #310501 from darshils2001/keepalive-email-change
Change email alias for keep alive
2 parents 7045eb9 + 54889b7 commit e283242

2 files changed

Lines changed: 2 additions & 2 deletions

File tree

articles/application-gateway/application-gateway-private-deployment.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -176,7 +176,7 @@ A list of all Azure CLI references for Private Link Configuration on Application
176176
After registering the feature, configuration of NSG, Route Table, and private IP address frontend configuration can be performed using any methods. For example: REST API, ARM Template, Bicep deployment, Terraform, PowerShell, CLI, or Portal.
177177

178178
> [!NOTE]
179-
> If your client application connects to App Gateway via a private IP, requires an idle timeout greater > than 4 minutes, and the client application does not send TCP keep-alive packets, contact appgw-idle-timeout@microsoft.com to request initiation of keep‑alive from Application Gateway.
179+
> If your client application connects to App Gateway via a private IP, requires an idle timeout greater > than 4 minutes, and the client application does not send TCP keep-alive packets, contact agprivateip-keepalive@microsoft.com to request initiation of keep‑alive from Application Gateway.
180180
181181
## Application Gateway Subnet
182182

articles/application-gateway/private-link-configure.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ To enable Private Link configuration, you must have a dedicated subnet that's se
5353
To create a dedicated subnet for Private Link, see [Add, change, or delete a virtual network subnet](../virtual-network/virtual-network-manage-subnet.md).
5454

5555
> [!NOTE]
56-
> If your client application connects to App Gateway via a private IP, requires an idle timeout greater > than 4 minutes, and the client application does not send TCP keep-alive packets, contact appgw-idle-timeout@microsoft.com to request initiation of keep‑alive from Application Gateway.
56+
> If your client application connects to App Gateway via a private IP, requires an idle timeout greater > than 4 minutes, and the client application does not send TCP keep-alive packets, contact agprivateip-keepalive@microsoft.com to request initiation of keep‑alive from Application Gateway.
5757
5858
# [Azure portal](#tab/portal)
5959

0 commit comments

Comments
 (0)