Jio India PreferredLocations list generated by ApplicationRegion has unexpectedly low priority for Central India

[camillemarie]

Describe the bug The PreferredLocations list generated when using ApplicationRegion for Jio India Central and Jio India West contains regions outside of India before India Central.

Based on what I can see internally, the region proximity for these regions was copied from Central India (not actual network latencies, probably because there isn't a public measurement for those as of now), but the latencies between those regions and Central India was set to a guess of "100 ms". Unless there is a major network problem between these nearby regions, I think it is unlikely that this value is correct.

To Reproduce

1. Set ApplicationRegion to Jio India Central or Jio India West
2. Check the PreferredLocations generated by the SDK

Expected behavior Central India would be one of the top regions in the PreferredLocations list.

Actual behavior Top 10 preferred locations for Jio India Central (Central India and Jio India West lower than expected): "preferredLocations": [ "Jio India Central", "West India", "South India", "Qatar Central", "UAE Central", "UAE North", "Southeast Asia", "East Asia", "Jio India West", "Central India", ]

Top 10 preferred locations for Jio India West (this is more correct, but nonetheless unlikely latency to East Asia is better than either India Central region): "preferredLocations": [ "Jio India West", "West India", "South India", "Qatar Central", "UAE Central", "UAE North", "Southeast Asia", "East Asia", "Jio India Central", "Central India" ]

Environment summary SDK Version: 3.31.0 OS Version (e.g. Windows, Linux, MacOSX): Windows

[ealsur]

@camillemarie We'll take a look, the input of this list is Azure buildout, the values are coming from the buildout latencies inbetween regions.