Change edge location selection from Anycast to Unicast#128212
Change edge location selection from Anycast to Unicast#128212ravisha22 wants to merge 1 commit intoMicrosoftDocs:mainfrom
Conversation
Updated the edge location selection method from Anycast to Unicast for Azure Front Door traffic routing.
|
Learn Build status updates of commit 07b1fa3:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/frontdoor/billing.md | Details | ||
| articles/frontdoor/classic-overview.md | Details | ||
| articles/frontdoor/front-door-overview.md | Details | ||
| articles/frontdoor/scenarios.md | Details | ||
| articles/frontdoor/front-door-traffic-acceleration.md | ✅Succeeded |
articles/frontdoor/billing.md
- Line 90, Column 153: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#select-the-front-door-edge-location-for-the-request-anycast' in 'articles/frontdoor/front-door-traffic-acceleration.md', did you mean '#select-the-front-door-edge-location-for-the-request-unicast'?
articles/frontdoor/classic-overview.md
- Line 42, Column 179: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#select-the-front-door-edge-location-for-the-request-anycast' in 'articles/frontdoor/front-door-traffic-acceleration.md', did you mean '#select-the-front-door-edge-location-for-the-request-unicast'?
articles/frontdoor/front-door-overview.md
- Line 46, Column 60: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#select-the-front-door-edge-location-for-the-request-anycast' in 'articles/frontdoor/front-door-traffic-acceleration.md', did you mean '#select-the-front-door-edge-location-for-the-request-unicast'?
articles/frontdoor/scenarios.md
- Line 49, Column 150: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#select-the-front-door-edge-location-for-the-request-anycast' in 'articles/frontdoor/front-door-traffic-acceleration.md', did you mean '#select-the-front-door-edge-location-for-the-request-unicast'? - Line 81, Column 156: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#select-the-front-door-edge-location-for-the-request-anycast' in 'articles/frontdoor/front-door-traffic-acceleration.md', did you mean '#select-the-front-door-edge-location-for-the-request-unicast'?
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
There was a problem hiding this comment.
Pull request overview
This PR updates Azure Front Door documentation to reflect a change in the edge location selection method from Anycast to Unicast for traffic routing.
Changes:
- Updated section heading to reference Unicast instead of Anycast
- Changed technical explanation to describe Unicast routing instead of Anycast
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| Globally, [Front Door has over 150 edge locations](edge-locations-by-region.md), or points of presence (PoPs), located in many countries/regions. Every Front Door PoP can serve traffic for any request. | ||
|
|
||
| Traffic routed to the Azure Front Door edge locations uses [Anycast](https://en.wikipedia.org/wiki/Anycast) for both DNS (Domain Name System) and HTTP (Hypertext Transfer Protocol) traffic. Anycast allows for user requests to reach the closest edge location in the fewest network hops. This architecture offers better round-trip times for end users by maximizing the benefits of [Split TCP](#connect-to-the-front-door-edge-location-split-tcp). | ||
| Traffic routed to the Azure Front Door edge locations uses [Unicast](https://en.wikipedia.org/wiki/Unicast) for both DNS (Domain Name System) and HTTP (Hypertext Transfer Protocol) traffic. Unicast allows for user requests to reach the closest edge location in the fewest network hops. This architecture offers better round-trip times for end users by maximizing the benefits of [Split TCP](#connect-to-the-front-door-edge-location-split-tcp). |
There was a problem hiding this comment.
The description of Unicast routing is technically incorrect. Unicast is a one-to-one transmission method where packets are sent from a single source to a single destination. The statement 'Unicast allows for user requests to reach the closest edge location' is misleading, as Unicast itself doesn't provide automatic routing to the closest location—that capability is characteristic of Anycast. If the platform is changing from Anycast to Unicast, the documentation should explain how closest-edge routing is now achieved (e.g., through DNS-based geo-routing or another mechanism) rather than incorrectly attributing Anycast properties to Unicast.
| Traffic routed to the Azure Front Door edge locations uses [Unicast](https://en.wikipedia.org/wiki/Unicast) for both DNS (Domain Name System) and HTTP (Hypertext Transfer Protocol) traffic. Unicast allows for user requests to reach the closest edge location in the fewest network hops. This architecture offers better round-trip times for end users by maximizing the benefits of [Split TCP](#connect-to-the-front-door-edge-location-split-tcp). | |
| Traffic routed to the Azure Front Door edge locations uses [Unicast](https://en.wikipedia.org/wiki/Unicast) for both DNS (Domain Name System) and HTTP (Hypertext Transfer Protocol) traffic, establishing a one-to-one connection between the client and the selected edge location. Front Door's global routing architecture and edge rings help ensure that user requests are directed to nearby edge locations in the fewest network hops. This architecture offers better round-trip times for end users by maximizing the benefits of [Split TCP](#connect-to-the-front-door-edge-location-split-tcp). |
prmerger-automator
bot
requested review from
AbdullahBell,
cherylmc,
halkazwini and
johndowns
|
@ravisha22 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Can you review the proposed changes? Note that the warnings will need to be resolved before the PR can be merged. IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
3 participants
Updated the edge location selection method from Anycast to Unicast for Azure Front Door traffic routing, inline with the changes being performed in the platform.