Skip to content

Commit bc0a535

Browse files
Merge pull request #285184 from Harikrishnan-M-B/patch-17
Update best-practices.md
2 parents d0979bc + 1cec4f4 commit bc0a535

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/frontdoor/best-practices.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ This article summarizes best practices for using Azure Front Door.
1515

1616
## General best practices
1717

18-
### Avoid combining Traffic Manager and Front Door
18+
### Understanding when to combine Traffic Manager and Front Door
1919

2020
For most solutions, we recommend the use *either* Front Door *or* [Azure Traffic Manager](../traffic-manager/traffic-manager-overview.md), but not both. Azure Traffic Manager is a DNS-based load balancer. It sends traffic directly to your origin's endpoints. In contrast, Azure Front Door terminates connections at points of presence (PoPs) near to the client and establishes separate long-lived connections to the origins. The products work differently and are intended for different use cases.
2121

0 commit comments

Comments
 (0)