add ipv6 notes and Q

Author: greg-lindsay

articles/traffic-manager/traffic-manager-FAQs.md

@@ -5,7 +5,7 @@ services: traffic-manager
 author: greg-lindsay
 ms.service: traffic-manager
 ms.topic: conceptual
-ms.date: 04/22/2024
+ms.date: 06/03/2024
 ms.author: greglin
 ---
 
@@ -144,8 +144,12 @@ Yes, only API version 2017-03-01 and newer supports the Geographic routing type.
 ### What are some use cases where subnet routing is useful?
 
 Subnet routing allows you to differentiate the experience you deliver for specific sets of users identified by the source IP of their DNS requests IP address. An example would be showing different content if users are connecting to a website from your corporate HQ. Another would be restricting users from certain ISPs to only access endpoints that support only IPv4 connections if those ISPs have subpar performance when IPv6 is used.
+
 Another reason to use Subnet routing method is in conjunction with other profiles in a nested profile set. For example, if you want to use Geographic routing method for geo-fencing your users, but for a specific ISP you want to do a different routing method, you can have a profile withy Subnet routing method as the parent profile and override that ISP to use a specific child profile and have the standard Geographic profile for everyone else.
 
+> [!NOTE]
+> Azure Traffic Manager supports IPv6 addresses in subnet overrides for subnet profiles. This capability enables more granular control over traffic routing based on the source IP address of DNS queries, including both IPv4 and IPv6 addresses.  
+
 ### How does Traffic Manager know the IP address of the end user?
 
 End-user devices typically use a DNS resolver to do the DNS lookup on their behalf. The outgoing IP of such resolvers is what Traffic Manager sees as the source IP. In addition, Subnet routing method also looks to see if there's EDNS0 Extended Client Subnet (ECS) information that was passed with the request. If ECS information is present, that is the address used to determine the routing. In the absence of ECS information, the source IP of the query is used for routing purposes.
@@ -335,6 +339,18 @@ Azure endpoints that are associated with a Traffic Manager profile are tracked u
 
 For more information, see [To move an endpoint](traffic-manager-manage-endpoints.md#to-move-an-endpoint).
 
+### Does Azure Traffic Manager support IPv6 Extension Mechanisms for DNS (ECS)?
+
+Azure Traffic Manager supports IPv6 addresses with Extension Mechanisms for DNS (ECS). This means that when a DNS query includes ECS information, Azure Traffic Manager can use the source IP address within the ECS to make intelligent routing decisions.  
+
+The support for IPv6 ECS brings several advantages: 
+
+- **Improved Localization**: By considering the IPv6 address in the ECS, Traffic Manager can route users to the nearest or most appropriate endpoint, enhancing the user experience with reduced latency. 
+- **Enhanced Traffic Control**: IPv6 ECS allows for more granular traffic routing decisions, enabling better management of global traffic and distribution. 
+
+When using IPv6 ECS, it’s important to ensure that your endpoints are correctly configured to handle IPv6 traffic. Also verify that your DNS infrastructure, including recursive resolvers, is capable of handling ECS information with IPv6 addresses. 
+
+
 ## Traffic Manager endpoint monitoring
 
 ### Is Traffic Manager resilient to Azure region failures?
@@ -531,7 +547,7 @@ The following table describes the behavior of Traffic Manager health checks for
 
 ### Why can't I add Azure Cloud Services Extended Support Endpoints to my Traffic Manager profile? 
 
-In order to add Azure Cloud Extended endpoints to a Traffic Manager profile, the resource group must have compatibility with the Azure Service Management (ASM) API. Profiles located in the older resource group must adhere to ASM API standards, which prohibit the inclusion of public IP address endpoints or endpoints from a different subscription than that of the profile. To resolve this, consider moving your Traffic Manager profile and associated resources to a new resource group compatible with the ASM API.  
+In order to add Azure Cloud Extended endpoints to a Traffic Manager profile, the resource group must have compatibility with the Azure Service Management (ASM) API. Profiles located in the older resource group must adhere to ASM API standards, which prohibit the inclusion of public IP address endpoints or endpoints from a different subscription than that of the profile. To resolve this, consider moving your Traffic Manager profile and associated resources to a new resource group compatible with the ASM API.
 
 ## Next steps:
 

articles/traffic-manager/traffic-manager-subnet-override-cli.md

@@ -5,7 +5,7 @@ services: traffic-manager
 author: greg-lindsay
 ms.topic: how-to
 ms.service: traffic-manager
-ms.date: 09/18/2019
+ms.date: 06/03/2024
 ms.author: greglin
 ms.custom: template-how-to, devx-track-azurecli
 ---
@@ -25,6 +25,9 @@ There are two types of routing profiles that support subnet overrides:
 * **Geographic** - If Traffic Manager finds a subnet override for the DNS query's IP address, it will route the query to the endpoint whatever the health of the endpoint is.
 * **Performance** - If Traffic Manager finds a subnet override for the DNS query's IP address, it will only route the traffic to the endpoint if it's healthy.  Traffic Manager will fall back to the performance routing heuristic if the subnet override endpoint isn't healthy.
 
+> [!NOTE]
+> Azure Traffic Manager supports IPv6 addresses in subnet overrides for subnet profiles. This capability enables more granular control over traffic routing based on the source IP address of DNS queries, including both IPv4 and IPv6 addresses. 
+
 ## Create a Traffic Manager subnet override
 
 To create a Traffic Manager subnet override, you can use Azure CLI to add the subnets for the override to the Traffic Manager endpoint.

articles/traffic-manager/traffic-manager-subnet-override-powershell.md

@@ -5,7 +5,7 @@ services: traffic-manager
 author: greg-lindsay
 ms.topic: how-to
 ms.service: traffic-manager
-ms.date: 05/07/2023
+ms.date: 06/03/2024
 ms.author: greglin
 ms.custom: template-how-to, devx-track-azurepowershell
 ---
@@ -25,6 +25,9 @@ There are two types of routing profiles that support subnet overrides:
 * **Geographic** - If Traffic Manager finds a subnet override for the DNS query's IP address, it will route the query to the endpoint whatever the health of the endpoint is.
 * **Performance** - If Traffic Manager finds a subnet override for the DNS query's IP address, it will only route the traffic to the endpoint if it's healthy.  Traffic Manager will fall back to the performance routing heuristic if the subnet override endpoint isn't healthy.
 
+> [!NOTE]
+> Azure Traffic Manager supports IPv6 addresses in subnet overrides for subnet profiles. This capability enables more granular control over traffic routing based on the source IP address of DNS queries, including both IPv4 and IPv6 addresses. 
+
 ## Prerequisites
 
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).

articles/traffic-manager/traffic-manager-use-with-application-gateway.md

@@ -0,0 +1,53 @@
+---
+title: Use Azure Application Gateway with Azure Traffic Manager
+description: This article explains how to use Azure Application Gateway with Azure Traffic Manager.
+services: traffic-manager
+author: greg-lindsay
+ms.service: traffic-manager
+ms.topic: how-to
+ms.date: 06/20/2024
+ms.author: greglin
+ms.custom: template-how-to
+---
+
+# Use Application Gateway with Azure Traffic Manager
+
+Azure Traffic Manager and Azure Application Gateway can be used together to provide global load balancing and failover capabilities for your web applications. Azure Traffic Manager uses DNS-based routing to distribute incoming traffic across multiple regions, while Azure Application Gateway provides application-level routing and load balancing within a region.
+
+## Scenarios for using Azure Application Gateway with Azure Traffic Manager
+
+* Improve application performance: By using Azure Traffic Manager to route traffic to the closest Azure Application Gateway, you can reduce latency and improve application performance for your users.
+* Increase application availability: By using Azure Traffic Manager to distribute traffic across multiple Azure Application Gateways, you can ensure that your application remains available even if one or more gateways become unavailable.
+* Scale your application: By using Azure Application Gateway to load balance traffic within a region, you can scale your application horizontally to handle increased traffic.
+* Secure your application: By using Azure Application Gateway to terminate SSL/TLS connections and protect against web attacks, you can secure your application from external threats.
+
+## Process overview: How to use Application Gateway with Azure Traffic Manager
+
+1.	Create an Azure Traffic Manager profile: Start by creating an Azure Traffic Manager profile. Configure it to use the desired traffic routing method (priority, weighted, performance, or geographic).
+2.	Create an Azure Application Gateway: Next, create an Azure Application Gateway. Configure it to use the desired backend pool and routing rules.
+3.	Add the Azure Application Gateway endpoint to the Azure Traffic Manager profile: Once your Application Gateway is set up, add it as an endpoint to your Traffic Manager profile.
+4.	Test Your Setup: Finally, test the configuration by accessing the Azure Traffic Manager DNS name from a web browser. This will help ensure that traffic is being correctly routed and load balanced.
+
+## Prerequisites
+
+* If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
+
+## Create a resource group
+
+Create a resource group for the Traffic Manager profile.
+
+1. Sign in to the [Azure portal](https://portal.azure.com).
+2. On the left pane of the Azure portal, select **Resource groups**.
+3. In **Resource groups**, on the top of the page, select **Add**.
+4. In **Resource group name**, type a name *myResourceGroupTM1*. For **Resource group location**, select **East US**, and then select **OK**.
+
+By using Azure Traffic Manager with Azure Application Gateway, you can achieve high availability and scalability for your web applications across multiple regions. This combination of services can help you to improve application performance, increase application availability, scale your application, and secure your application.
+
+Remember to monitor the health of your endpoints and adjust your Traffic Manager and Application Gateway configurations as needed to ensure high availability, optimal geographic distribution, and effective load balancing.
+
+## Next steps
+
+- Learn about [weighted traffic routing method](traffic-manager-configure-weighted-routing-method.md).
+- Learn about [priority routing method](traffic-manager-configure-priority-routing-method.md).
+- Learn about [geographic routing method](traffic-manager-configure-geographic-routing-method.md).
+- Learn how to [test Traffic Manager settings](traffic-manager-testing-settings.md).