Azure front door latency based routing ensures that requests are sent to the lowest latency backends acceptable within a sensitivity range. Basically, your user requests are sent to the "closest" set of backends in respect to network latency. So if request comes via A region as the latency is less to the A region Function App, the request will be routed to A region Function App.
The 'closest' backend isn't necessarily closest as measured by geographic distance. Instead, Front Door determines the closest backends by measuring network latency. Ex: If the user from A region requests but during that time the latency to the A location is high than B location, then the request will be routed to Location B as the latency is less.
Ref: https://learn.microsoft.com/en-us/azure/frontdoor/front-door-routing-methods.
Configuration : By default you see latency based routing , if you want other routing methods to enable then under backend pool you will find priority and weight options.
Ref: https://learn.microsoft.com/en-gb/azure/frontdoor/front-door-backend-pool
If you want only Geo based filtering irrespective of the latency then you need to go with Traffic manager service, Geographic as routing method.
Ref: https://learn.microsoft.com/en-us/azure/traffic-manager/traffic-manager-routing-methods
Loadbalancing Ref : https://learn.microsoft.com/en-us/azure/architecture/guide/technology-choices/load-balancing-overview
Hope this was helpful. Please let us know in case of any additional questions or concerns.
Please "Accept the answer" if the information helped you. This will help us and others in the community as well