Controlling Azure web app traffic with Azure Traffic Manager

Note

This article provides summary information for Microsoft Azure Traffic Manager as it relates to Azure Web Apps. More information about Azure Traffic Manager itself can be found by visiting the links at the end of this article.

Introduction

You can use Azure Traffic Manager to control how requests from web clients are distributed to web apps in Azure App Service. When web app endpoints are added to an Azure Traffic Manager profile, Azure Traffic Manager keeps track of the status of your web apps (running, stopped, or deleted) so that it can decide which of those endpoints should receive traffic.

Routing methods

Azure Traffic Manager uses three different routing methods. These methods are described in the following list as they pertain to Azure web apps.

  • Priority: use a primary web app for all traffic, and provide backups in case the primary or the backup web apps are unavailable.
  • Weighted: distribute traffic across a set of web apps, either evenly or according to weights, which you define.
  • Performance: when you have web apps in different geographic locations, use the "closest" web app in terms of the lowest network latency.
  • Geographic: direct users to specific web apps based on which geographic location their DNS query originates from.

For more information, see Traffic Manager routing methods.

Web Apps and Traffic Manager Profiles

To configure the control of web app traffic, you create a profile in Azure Traffic Manager that uses one of the three load balancing methods described previously, and then add the endpoints (in this case, web apps) for which you want to control traffic to the profile. Your web app status (running, stopped, or deleted) is regularly communicated to the profile so that Azure Traffic Manager can direct traffic accordingly.

When using Azure Traffic Manager with Azure, keep in mind the following points:

  • For web app only deployments within the same region, Web Apps already provides failover and round-robin functionality without regard to web app mode.
  • For deployments in the same region that use Web Apps in conjunction with another Azure cloud service, you can combine both types of endpoints to enable hybrid scenarios.
  • You can only specify one web app endpoint per region in a profile. When you select a web app as an endpoint for one region, the remaining web apps in that region become unavailable for selection for that profile.
  • The web app endpoints that you specify in an Azure Traffic Manager profile appears under the Domain Names section on the Configure page for the web app in the profile, but is not configurable there.
  • After you add a web app to a profile, the Site URL on the Dashboard of the web app's portal page displays the custom domain URL of the web app if you have set one up. Otherwise, it displays the Traffic Manager profile URL (for example, contoso.trafficmgr.com). Both the direct domain name of the web app and the Traffic Manager URL are visible on the web app's Configure page under the Domain Names section.
  • Your custom domain names work as expected, but in addition to adding them to your web apps, you must also configure your DNS map to point to the Traffic Manager URL. For information on how to set up a custom domain for an Azure web app, see Configuring a custom domain name for an Azure web site.
  • You can only add web apps that are in standard or premium mode to an Azure Traffic Manager profile.

Next Steps

For a conceptual and technical overview of Azure Traffic Manager, see Traffic Manager Overview.

For more information about using Traffic Manager with Web Apps, see the blog posts Using Azure Traffic Manager with Azure Web Sites and Azure Traffic Manager can now integrate with Azure Web Sites.