TRAFFIC MANAGER ROUTING METHODS

Priority: Select Priority when you want to use a primary service endpoint for all traffic and provide
backups in case the primary or the backup endpoints are unavailable.
You configure the endpoint priority explicitly using the 'priority' property for each endpoint. This
property is a value between 1 and 1000. Lower values represent a higher priority. Endpoints cannot
share priority values. Setting the property is optional. When omitted, a default priority based on the
endpoint order is used.
 

Weighted: Select Weighted when you want to distribute traffic across a set of endpoints, either evenly
or according to weights, which you define.
In the Weighted traffic-routing method, you assign a weight to each endpoint in the Traffic Manager
profile configuration. The weight is an integer from 1 to 1000. This parameter is optional. If omitted,
Traffic Managers uses a default weight of '1'. For each DNS query received, Traffic Manager randomly
chooses an available endpoint. The probability of choosing an endpoint is based on the weights
assigned to all available endpoints. Using the same weight across all endpoints results in an even traffic
distribution. Using higher or lower weights on specific endpoints causes those endpoints to be returned
frequently in the DNS responses.

Performance: Select Performance when you have endpoints in different geographic locations and you

want end users to use the "closest" endpoint in terms of the lowest network latency. Traffic Manager
maintains an Internet Latency Table to track the round-trip time between IP address ranges and each
Azure datacenter. the IP address used to determine the 'closest' endpoint is not the client's IP address,
but it is the IP address of the recursive DNS service. In practice, this IP address is a good proxy for the
client. Performance traffic-routing does not monitor load on a given service endpoint.
The algorithm that chooses the endpoint is deterministic. Repeated DNS queries from the same client
are directed to the same endpoint. However, the Performance traffic-routing method does not
guarantee that a client is always routed to the same endpoint - also because latency table gets updated.

Geographic: Select Geographic so that users are directed to specific endpoints (Azure, External, or

Nested) based on which geographic location their DNS query originates from. This empowers Traffic
Manager customers to enable scenarios where knowing a user’s geographic region and routing them
based on that is important. Examples include complying with data sovereignty mandates, localization of
content & user experience and measuring traffic from different regions.

 
  World– any region
 Regional Grouping – for example, Africa, Middle East, Australia/Pacific etc.
 Country/Region – for example, Ireland, Peru, Hong Kong SAR etc.
 State/Province – for example, USA-California, Australia-Queensland, Canada-Alberta etc. (note:
this granularity level is supported only for states / provinces in Australia, Canada, UK, and USA).

If a user’s region comes under two different endpoints’ geographic mapping, Traffic Manager
selects the endpoint with the lowest granularity and does not consider routing requests from that
region to the other endpoint. For example, consider a Geographic Routing type profile with two
endpoints - Endpoint1 and Endpoint2. Endpoint1 is configured to receive traffic from Ireland and
Endpoint2 is configured to receive traffic from Europe. If a request originates from Ireland, it is always
routed to Endpoint1. 

Since a region can be mapped only to one endpoint, Traffic Manager returns it regardless of
whether the endpoint is healthy or not. It is strongly recommended that customers using the
geographic routing method associate it with the Nested type endpoints that has child profiles
containing at least two endpoints within each.

If an endpoint match is found and that endpoint is in the Stopped state, Traffic Manager returns a
NODATA response. If an endpoint displays a Disabled status, it won’t be included in the region matching
process.

If a query is coming from a geographic region that has no mapping in that profile, Traffic Manager
returns a NODATA response. Therefore, it is strongly recommended that customers use geographic
routing with one endpoint, ideally of type Nested with at least two endpoints within the child profile,
with the region World assigned to it

<--- which geolocation database do we use?

  With “Geographic” TM routing method, Traffic Manager uses the source IP address of the DNS query to
determine the region from which a user is querying from.

The table is here \\reddog\builds\branches\git_networking_trafficmanager_watm142_latest\retail-amd64\

deploy\StaticResources in the Geomap.csv file
 
Be careful, the file is so big that Excel will crash so you need to use your favorite text editor 

***For further information, please go to:

https://docs.microsoft.com/en-us/azure/traffic-manager/traffic-manager-routing-methods