Hi @Karamjit Singh,
Azure front door supports only for Geo Location in the rule engine configuration. Unfortunately, it doesn't support the regions.to specifically route the traffic
Refer this doc:
https://learn.microsoft.com/en-us/azure/web-application-firewall/afds/waf-front-door-geo-filtering
- By default, Azure Front Door routes traffic to the origin that is closest to your end users. The latency routing method is the default behavior for end users.
- This method directs user requests to the origin with the lowest network latency, rather than the closest geographic location, ensuring optimal performance.
For example, East US users will be routed to the East US web application. Central US users will be routed to the Central US web application.
Refer this doc:
https://learn.microsoft.com/en-us/azure/frontdoor/routing-methods#lowest-latencies-based-traffic-routing
May I ask if the above behavior is not working on your setup? If so, could you please provide some insights or issues you are experiencing?
Kindly let us know if the above helps or you need further assistance on this issue.
Please accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer. Here is how.