Optimizing DNS Resolution for Balanced Traffic in Azure Traffic Manager

Advanced Techniques for Controlling Traffic Flow in Azure Traffic Manager

We built a traffic manager with a weight routing method (former round robin mode), and configured two endpoints with the same weight value.

We expected that the traffic would be evenly distributed to two endpoints. But actually, we saw one endpoint get much more traffic than another one.

We then checked the "automation script" of traffic manager on portal and found this:

{
    "name": "test1",
    "type": "Microsoft.Network/trafficManagerProfiles/externalEndpoints",
    "properties": {
        "endpointStatus": "Enabled",
        "target": "www.abc.com",
        "weight": 1,
        "priority": 1,
        "endpointLocation": null
    }
},
{
    "name": "test2",
    "type": "Microsoft.Network/trafficManagerProfiles/externalEndpoints",
    "properties": {
        "endpointStatus": "Enabled",
        "target": "www.xyz.com",
        "weight": 1,
        "priority": 2,
        "endpointLocation": null
    }
}

There is "priority" in the above template, what priority mean in weight routing mode? Will this setting affect the traffic routing?

How to resolve the above issue ?