Azure front door always routes request to the latest or last origin in an origin group of blob storages.

Question

Actally i was expecting front door to select the nearest and fastest blob storage to upload files, like i added 4 origins:

1. Central Australia.
2. North India
3. US east 2
4. UAE north.

Based on my assumptions, it should have selected uae north for me because it has the lowest latency. I have set same weights and priorities for each origin. But it always routes requests to the last origin in number. What am i doing wrong?

Answer 1

@Zeeshan Ashraf ,

Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

Looking at your configuration, the load distribution should be round robin provided all the origins have a latency of less than 300 ms.

When you say, "it should have selected uae north for me because it has the lowest latency"

• Is this is still happening?
• May I ask how you are saying UAE North is the one with the lowest latency.
• Is it because of the geographical location of the client?

The 'closest' origin isn't necessarily closest as measured by geographic distance. Instead, Azure Front Door determines the closest origin by measuring network latency. Read more about Azure Front Door routing architecture.

• When you say, "But it always routes requests to the last origin in number."
  • Do you mean the request is always served by "wedfludev"?
  • And if you swap the order of "wedfludev" and "testfrontwed", requests are always served by "testfrontwed"?
• Make sure you have not enabled caching in AFD - this could be giving you the response from a cached endpoint that originally routed to "wedfludev"
• Have you enabled session affinity ?

Cheers,

Kapil