Skip to content

Commit 7bb4655

Browse files
authored
Merge pull request #207385 from duongau/patch-3
AFD FAQ - update answer for routing to virtual network
2 parents 154cb5c + 7c46849 commit 7bb4655

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/frontdoor/front-door-faq.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -188,7 +188,7 @@ sections:
188188
- question: |
189189
Can Azure Front Door load balance or route traffic within a virtual network?
190190
answer: |
191-
Azure Front Door (AFD) requires a public IP or publicly resolvable DNS name to route traffic. So, the answer is no AFD directly cannot route within a virtual network, but using an Application Gateway or Azure Load Balancer in between will solve this scenario.
191+
Azure Front Door Standard, Premium and (classic) tier requires a public IP or publicly resolvable DNS name to route traffic to backend resources. Azure resources such as Application Gateways or Azure Load Balancers can enable routing to resources within a virtual network. If you're using a Front Door Premium tier, you can enable Private Link to connect to origins behind an internal load balancer over a private endpoint. For more information, see [Secure origins with Private Link](private-link.md).
192192
193193
- question: |
194194
What are the various timeouts and limits for Azure Front Door?

0 commit comments

Comments
 (0)