Traffic Manager in Azure App services

Traffic Manager

  • Traffic Manager is used for applications that need to scale beyond the capacity of a single deployment or whose users are globally dispersed.
  • Deploying your web app to multiple regions (or data-centers) is a scale-out strategy that can be used to achieve massive sociability for your web app.
  • Assume, for example, that you have a web app deployment in the Central US region. If your users are dispersed around the world, then you may choose to deploy to the West US, East US, and North Europe regions as well. Doing so will significantly increase capacity of your web app.
  • The challenge of routing users to one of many web app deployments can be met by using Azure Traffic Manager. This is a networking service that can be used to achieve global scale for your web apps by allowing you to control how user traffic is routed to multiple deployments of your application

To use Traffic Manager, you first must create a Traffic Manager profile, which identifies a unique DNS name for the profile in the domain, a list of (web app deployments) that you specify, and which can be one of the following:

  1. Performance: Select this method if your end points are deployed in different geographical locations and you want to use the one with lowest latency (closer to the user).
  2. Priority: Select this when you want to select an endpoint which has highest priority and is available.
  3. Weighted: Select this method when you want to distribute traffic across a set of endpoints as per the weight provided

How Traffic Manager works:

When you configure a Traffic Manager profile, the settings that you specify provide Traffic Manager with the information needed to determine which endpoint should service the request based on a DNS query. No actual endpoint traffic routes through Traffic Manager.

  1. User traffic to company domain name: The client requests information using the company domain name. The goal is to resolve a DNS name to an IP address. Company domains must be reserved through normal Internet domain name registrations that are maintained outside of Traffic Manager. In Figure 1, the example company domain is
  2. Company domain name to Traffic Manager domain name: The DNS resource record for the company domain points to a Traffic Manager domain name maintained in Azure Traffic Manager. This is achieved by using a CNAME resource record that maps the company domain name to the Traffic Manager domain name. In the example, the Traffic Manager domain name is
  3. Traffic Manager Domain name and profile: The Traffic Manager domain name is part of the Traffic Manager profile. The user’s DNS server sends a new DNS query for the Traffic Manager domain name (in our example,, which is received by the Traffic Manager DNS name servers.
  4. Traffic Manager Profile rules processed: Traffic Manager uses the specified traffic routing method and monitoring status to determine which Azure or other endpoint should service the request.
  5. Endpoint domain name sent to user: Traffic Manager returns a CNAME record that maps the Traffic Manager domain name to the domain name of the endpoint. The user’s DNS server resolves the endpoint domain name to its IP address and sends it to the user.
  6. User calls the endpoint: The user calls the returned endpoint directly using its IP address.

Note: Since the company domain and resolved IP address are cached on the client machine, the user continues to interact with the chosen endpoint until its local DNS cache entry expires. It is important to note that the DNS client caches DNS host entries for the duration of their Time-to-Live (TTL). Retrieving host entries from the DNS client cache bypasses the Traffic Manager profile and you could experience connection delays if the endpoint becomes unavailable before the TTL expires.

To implement Traffic Manager

  1. Deploy the Web Apps in different Geographical locations
  2. Browse à Traffic Manager profiles –> Add
  3. Set Name=Demo, Routing Method = Weighted –> Create
  4. Go to Traffic Manger –> Settings –> End Points –> Add
  5. Type = Azure EndPoint, Name=WebApp1EP, Target Resource Type = App Service, Choose an App Service, Weight = 1 –> OK
  6. Repeat step 5 for every Web App deployment.


What is Cloud Computing?

  • Cloud is just a metaphor for the internet, when we say cloud, we are just referring to internet.
  • In the simplest terms, cloud computing means storing and accessing data and programs over the Internet instead of our local computer’s hard drive.
  • The phrase cloud computing means “a type of Internet-based computing” where different services — such as servers, storage and applications — are delivered to an organization’s computers and devices through the Internet.
  • Cloud Computing refer to a variety of services available over the Internet that deliver computing functionality on the service provider’s infrastructure.
  • Cloud platform hide the complexity and details of the underlying infrastructure from users and applications by providing very simple graphical interface or API (Applications Programming Interface).
  • The Cloud platform provides on demand services that are always on, anywhere, anytime and anyplace

Why are businesses moving to cloud?

In traditional hosting, a software company has to deal with licensing costs, protection of data, frequent upgrades to latest technologies, maintenance and up gradation of hardware and most important finding the right skillsets at the right time.

Visit for Complete Training and Tutorial: Microsoft Azure Tutorial