You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/application-gateway/private-link.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,7 +58,6 @@ Four components are required to implement Private Link with Application Gateway:
58
58
- The subnet used for PrivateLinkConfiguration can't be same as the Application Gateway subnet.
59
59
- Private link configuration for Application Gateway doesn't expose the "Alias" property and must be referenced via resource URI.
60
60
- Private Endpoint creation doesn't create a \*.privatelink DNS record or zone. All DNS records should be entered in existing zones used for your Application Gateway.
61
-
- Azure Front Door and Application Gateway don't support chaining via Private Link.
62
61
- Private Link Configuration for Application Gateway has an idle timeout of ~5 minutes (300 seconds). To avoid hitting this limit, applications connecting through private endpoints to Application Gateway must use TCP keepalive intervals of less than 300 seconds.
0 commit comments