Add your own Traffic Manager to Application Proxy
This article explains how to configure Azure Active Directory (Azure AD) Application Proxy to work with Traffic Manager. With the Application Proxy geo-routing feature, you can optimize which region of the Application Proxy service your connector groups use. You can now combine this functionality with a Traffic Manager solution of your choice. This combination enables a fully dynamic geo-aware solution based on your user location. It unlocks the rich rule set of your preferred Traffic Manager to prioritize how traffic is routed to your apps protected by Application Proxy. With this combination, users can use a single URL to access the instance of the app closest to them.
- A Traffic Manager solution.
- Apps that exist in different regions. Geo-routing is enabled per connector group co-located with the app.
- A custom domain to use for each app.
Application Proxy configuration
To use Traffic Manager, you must configure Application Proxy. The configuration steps that follow refer to the following URL definitions:
- Regional URL: The Application Proxy endpoints for each app. For example, nam.contoso.com and india.contoso.com.
- Alternate URL: The URL configured for the Traffic Manager. For example, contoso.com.
Follow these steps to configure Application Proxy for Traffic Manager:
Install connectors for each location your app instances will be in. For each connector group, use the geo-routing feature to assign the connectors to their respective regions.
Set up your app instances with Application Proxy as follows:
- For each app, upload a custom domain. Include the alternate URL to use for the apps as a SAN URL to the uploaded certificate.
- Assign each app to its respective connector group.
- If you prefer the alternate URL to be maintained throughout the user session, register each app and add the URL as a reply URL. This step is optional.
In the Traffic Manager solution, add the Application Proxy regional URLs that were created for each app as an endpoint.
Configure the Traffic Manager's load balancing rules with a standard SKU.
To give your Traffic Manager a user-friendly URL, create a CNAME record that points the alternate URL to the Traffic Manager's endpoint.
alternateUrlproperty, configure the alternate URL on the onPremisesPublishing resource type of the app.
If you want the alternate URL to be maintained throughout the user session, call
onPremisesPublishingand set the
Sample Application Proxy configuration
The following table shows a sample Application Proxy configuration. This sample uses the sample app domain www.contoso.com as the alternate URL.
|North America-based app||India-based app||Additional Information|
|Internal URL||contoso.com||contoso.com||If the apps are hosted in different regions, you can use the same internal URL for each app.|
|External URL||nam.contoso.com||india.contoso.com||Configure a custom domain for each app.|
|Custom domain certificate||DNS: nam.contoso.com SAN: www.contoso.com||DNS: nam.contoso.com SAN: www.contoso.com||In the certificate you upload for each app, set the SAN value to the alternate URL. The alternate URL is the URL all users use to reach the app.|
|Connector group||NAM Geo Group||India Geo Group||Ensure you assign each app to the correct connector group by using the geo-routing functionality.|
|Redirects||(Optional) To maintain redirects for the alternate URL, add the application registration for the app.||(Optional) To maintain redirects for the alternate URL, add the application registration for the app.||This step is required if the alternate URL (www.contoso.com) is to be maintained for all redirections.|
Traffic manager configuration
Follow these steps to configure the Traffic Manager:
Create a Traffic Manager profile with your preferred routing rules.
In the Traffic Manager, add the NAM endpoint: nam.contoso.com.
Add the India endpoint: india.contoso.com.
Add the app proxy endpoints.
Add a CNAME record to point www.contoso.com to the Traffic Manager's URL. For example, contoso.trafficmanager.net.
The alternate URL now points to the Traffic Manager.
Publish applications on separate networks and locations using connector groups
Submit and view feedback for