Hello @Katare, Ashish ,
I'm unable to share the internal architecture or workflow of Azure Frontdoor, however, below is the update I received from AFD PG team:
Resolution for both DNS and HTTP (the portions in Microsoft’s control of both of those) route via Anycast which means they will resolve to the closest Microsoft Edge location as mentioned here. While this creates a very high likelihood at geo-regional traffic (e.g. Europe will resolve to European DNS and CDN servers), there is no strict guarantee around this.
If you need 100% strict geo-isolation then it cannot be guaranteed by Front Door (or any other CDN for that matter) today. We have a roadmap feature to support this but it is not short term.
One workaround that I can think of at the moment would be to use Azure Traffic Manager (Since you can use Geographic traffic routing method in Traffic manager to comply with local data sovereignty mandates which require that users from a specific region be served only by endpoints in that region) and Azure Front Door parallelly to serve all traffic for your application as described in the below article:
https://learn.microsoft.com/en-us/azure/frontdoor/front-door-lb-with-azure-app-delivery-suite#building-with-azures-application-delivery-suite
Kindly let us know if the above helps or you need further assistance on this issue.
----------------------------------------------------------------------------------------------------------------
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.