Skip to content

Commit cc46aba

Browse files
Update application-gateway-private-deployment.md
Added NOTE about subnet delegation requirement for Private Deployment Application Gateways (preview) Since May 5, 2025 it was enforced on new and existing deployments
1 parent e43cf1f commit cc46aba

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

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

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -187,6 +187,10 @@ The resource tag is cosmetic, and serves to confirm that the gateway has been pr
187187

188188
Application Gateway Subnet is the subnet within the Virtual Network where the Application Gateway Resources will be deployed. In the Frontend Private Ip configuration, is important that this subnet can reach privately the resources that want to connect to your exposed app or site.
189189

190+
> [!NOTE]
191+
> As of May 5, 2025 new and existing deployments of Private Application Gateway require Subnet Delegation to `Microsoft.Network/applicationGateways`.
192+
> Please follow [these steps](https://learn.microsoft.com/en-us/azure/virtual-network/manage-subnet-delegation?tabs=manage-subnet-delegation-portal) for configuring Subnet Delegation.
193+
190194
## Outbound Internet connectivity
191195

192196
Application Gateway deployments that contain only a private frontend IP configuration (do not have a public IP frontend configuration associated to a request routing rule) aren't able to egress traffic destined to the Internet. This configuration affects communication to backend targets that are publicly accessible via the Internet.

0 commit comments

Comments
 (0)