Merge pull request #252608 from MicrosoftDocs/release-ga-expressroute-traffic-collector

Release ga expressroute traffic collector --scheduled release at 4AM of 9/25

Author: huypub

articles/expressroute/how-to-configure-traffic-collector.md

@@ -1,51 +1,49 @@
 ---
-title: 'Configure ExpressRoute Traffic Collector for ExpressRoute Direct using the Azure portal (Preview)'
-description: Learn how to create an ExpressRoute Traffic Collector resource to import logs into a Log Analytics workspace.
+title: Configure Traffic Collector for ExpressRoute Direct
+titleSuffix: Azure ExpressRoute
+description: This article shows you how to create an ExpressRoute Traffic Collector resource and import logs into a Log Analytics workspace.
 services: expressroute
 author: duongau
 ms.service: expressroute
-ms.topic: tutorial
-ms.date: 07/15/2022
+ms.topic: how-to
+ms.date: 08/09/2023
 ms.author: duau
+#Customer intent: As a network engineer, I want to configure ExpressRoute Traffic Collector to import flow logs into a Log Analytics workspace.
 ---
 
-# Configure ExpressRoute Traffic Collector for ExpressRoute Direct using the Azure portal (Preview)
+# Configure Traffic Collector for ExpressRoute Direct
 
-This article will help you deploy an ExpressRoute Traffic Collector using the Azure portal. You'll learn how to add and remove an ExpressRoute Traffic Collector, associate it to an ExpressRoute Direct circuit and Log Analytics workspace. Once the ExpressRoute Traffic Collector is deployed, sampled flow logs will get imported into a Log Analytics workspace. For more information, see [About ExpressRoute Traffic Collector](traffic-collector.md).
+This article helps you deploy an ExpressRoute Traffic Collector using the Azure portal. You learn how to add and remove an ExpressRoute Traffic Collector, associate it to an ExpressRoute Direct circuit and Log Analytics workspace. Once the ExpressRoute Traffic Collector is deployed, sampled flow logs get imported into a Log Analytics workspace. For more information, see [About ExpressRoute Traffic Collector](traffic-collector.md).
 
-> [!IMPORTANT]
-> ExpressRoute Traffic Collector is currently in PREVIEW.
-> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
+## Prerequisites
+
+- An ExpressRoute Direct circuit with Private or Microsoft peering configured.
+- A Log Analytics workspace (Create new or use existing workspace).
 
 ## Limitations
 
 - ExpressRoute Traffic Collector supports a maximum ExpressRoute Direct circuit size of 100 Gbps.
-- You can associate up to 20 ExpressRoute Direct circuits with ExpressRoute Traffic Collector as long as the total circuit bandwidth doesn't exceed 100 Gbps.
-
-## Prerequisites
-
-- ExpressRoute Direct circuit with Private or Microsoft peering configured.
-- A Log Analytics workspace (Create new or use existing).
+- You can associate up to 20 ExpressRoute Direct circuits with ExpressRoute Traffic Collector. The total circuit bandwidth can't exceed 100 Gbps.
+- The ExpressRoute Direct circuit, Traffic Collector and the Log Analytics workspace must be in the same geo-political region. Cross geo-political resource association isn't supported.  
+- The ExpressRoute Direct circuit and Traffic Collector must be deployed in the same subscription. Cross subscription deployments aren't available. 
 
 > [!NOTE]
-> - The ExpressRoute Direct circuit, ExpressRoute Traffic Collector and the Log Analytics workspace must be in the same geo-political region. Cross geo-political resource association is not supported.  
-> - The ExpressRoute Direct circuit and ExpressRoute Traffic Collector must be deployed in the same subscription. Cross subscription deployment is currently not available. 
-> - Log Analytics and ExpressRoute Traffic Collector can be deployed in cross subscription.
+> - Log Analytics and ExpressRoute Traffic Collector can be deployed in a different subscription.
 > - When ExpressRoute Traffic Collector gets deployed in an Azure region that supports availability zones, it will have availability zone enabled by default.
 
 ## Permissions
 
-- Minimum contributor access is required to deploy ExpressRoute Traffic Collector.
-- Minimum contributor access is required to associate ExpressRoute Direct circuit with ExpressRoute Traffic Collector.
-- Monitor contributor role is required to associate Log Analytics workspace with ExpressRoute Traffic Collector.
+- Minimum of **contributor** access is required to deploy ExpressRoute Traffic Collector.
+- Minimum of **contributor** access is required to associate ExpressRoute Direct circuit with ExpressRoute Traffic Collector.
+- **Monitor contributor** role is required to associate Log Analytics workspace with ExpressRoute Traffic Collector.
 
 For more information, see [Identity and access management](../active-directory/fundamentals/active-directory-ops-guide-iam.md).
 
 ## Deploy ExpressRoute Traffic Collector
 
-1. Sign in to the [Azure portal](https://portal.azure.com/)
+1. Sign in to the [Azure portal](https://portal.azure.com/).
 
-1. In the portal, go to the list of ExpressRoute circuits and select **ExpressRoute Traffic Collectors**. Then select **+ Create new**.
+1. In the portal, go to the ExpressRoute circuits page and select **ExpressRoute Traffic Collectors** from the top of the page. Select **+ Create new** from the drop-down menu.
 
     :::image type="content" source="./media/how-to-configure-traffic-collector/circuit-list.png" alt-text="Screenshot of the create new ExpressRoute Traffic Collector button from the ExpressRoute circuit list page.":::
 
@@ -61,11 +59,13 @@ For more information, see [Identity and access management](../active-directory/f
     | Region | Select a region to deploy this resource into. This resource needs to be in the same geo-political region as the Log Analytics workspace and the ExpressRoute Direct circuits. |
     | Collector Policy | This value is automatically filled in as **Default**. |
 
-1. On the **Select ExpressRoute circuit** tab, select **+ Add ExpressRoute Circuits**. Select the checkbox next to the circuit you would like to add to the Traffic Collector and then select **Add**. Once you're satisfied with the circuits added, select **Next**.
+1. On the **Select ExpressRoute circuit** tab, select **+ Add ExpressRoute Circuits**. 
+
+1. On the **Add Circuits** page, select the checkbox next to the circuit you would like Traffic Collector to monitor and then select **Add**. Select **Next** to configure where logs gets forwarded to.
 
     :::image type="content" source="./media/how-to-configure-traffic-collector/select-circuits.png" alt-text="Screenshot of the select ExpressRoute circuits tab and add circuits page.":::
 
-1. On the **Forward Logs** tab, select the checkbox for **Send to Log Analytics workspace**. You can create a new Log Analytics workspace or choose an existing. The workspace can be in a different Azure subscription but has to be in the same geo-political region. Select **Next** once a workspace has been chosen.
+1. On the **Forward Logs** tab, select the checkbox for **Send to Log Analytics workspace**. You can create a new Log Analytics workspace or select an existing one. The workspace can be in a different Azure subscription but has to be in the same geo-political region. Select **Next** once a workspace has been chosen.
 
     :::image type="content" source="./media/how-to-configure-traffic-collector/forward-logs.png" alt-text="Screenshot of the forward logs tab to Logs Analytics workspace.":::
 
@@ -91,6 +91,6 @@ Once all circuits have been removed from the ExpressRoute Traffic Collector, sel
 
 :::image type="content" source="./media/how-to-configure-traffic-collector/overview.png" alt-text="Screenshot of delete button on overview page." lightbox="./media/how-to-configure-traffic-collector/overview.png":::
 
-## Next steps
+## Next step
 
-- [ExpressRoute Traffic Collector Metrics](expressroute-monitoring-metrics-alerts.md#expressroute-traffic-collector-metrics)
+- Learn about [ExpressRoute Traffic Collector metrics](expressroute-monitoring-metrics-alerts.md#expressroute-traffic-collector-metrics) to monitor your ExpressRoute Traffic Collector resource.

articles/expressroute/traffic-collector.md

@@ -1,28 +1,25 @@
 ---
-title: Enable flow logging using Azure ExpressRoute Traffic Collector (Preview)
-description: Learn about ExpressRoute Traffic Collector and the different use cases where this feature will be helpful.
+title: Azure ExpressRoute Traffic Collector
+titleSuffix: Azure ExpressRoute
+description: Learn about ExpressRoute Traffic Collector and the different use cases where this feature is helpful.
 services: expressroute
 author: duongau
 ms.service: expressroute
 ms.topic: conceptual
-ms.date: 08/02/2022
+ms.date: 08/21/2023
 ms.author: duau
 ms.custom: references_regions
 ---
 
-# Enable flow logging using ExpressRoute Traffic Collector (Preview)
+# Azure ExpressRoute Traffic Collector
 
-ExpressRoute Traffic Collector enables sampling of network flows sent over your ExpressRoute Direct circuits. Flow logs get sent to a [Log Analytics workspace](../azure-monitor/logs/log-analytics-overview.md) where you can create your own log queries for further analysis, export the data to any visualization tool or SIEM (Security Information and Event Management) of your choice. Flow logging can be enabled for both private peering and Microsoft peering with ExpressRoute Traffic Collector.
-
-> [!IMPORTANT]
-> ExpressRoute Traffic Collector is currently in PREVIEW.
-> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
+ExpressRoute Traffic Collector enables sampling of network flows sent over your ExpressRoute Direct circuits. Flow logs get sent to a [Log Analytics workspace](../azure-monitor/logs/log-analytics-overview.md) where you can create your own log queries for further analysis. You can also export the data to any visualization tool or SIEM (Security Information and Event Management) of your choice. Flow logs can be enabled for both private peering and Microsoft peering with ExpressRoute Traffic Collector.
 
 :::image type="content" source="./media/traffic-collector/main-diagram.png" alt-text="Diagram of ExpressRoute traffic collector in an Azure environment.":::
 
 ## Use cases
 
-Flow logs can help you derive various traffic insights. Most common use cases are:
+Flow logs can help you look into various traffic insights. Some common use cases are:
 
 ### Network monitoring
 
@@ -44,7 +41,7 @@ Flow logs can help you derive various traffic insights. Most common use cases ar
 
 ## Flow log collection and sampling
 
-ExpressRoute Traffic Collector enables flow collection for Azure private peering and Microsoft peering. Flow logs are collected every minute. All packets collected for a given flow gets aggregated and imported into a Log Analytics workspace for further analysis. During flow collection, not every packet is captured into its own flow record. ExpressRoute Traffic Collector uses a sampling rate of 1:4096, meaning 1 out of every 4096 packets gets captured. Therefore, sampling rate short flows (in total bytes) may not get collected. This sampling size doesn't affect network traffic analysis when sampled data is aggregated over a longer period of time. Flow collection time and sampling rate are fixed and can't be changed.
+Flow logs are collected at an interval of every 1 minute. All packets collected for a given flow get aggregated and imported into a Log Analytics workspace for further analysis. During flow collection, not every packet is captured into its own flow record. ExpressRoute Traffic Collector uses a sampling rate of 1:4096, meaning 1 out of every 4096 packets gets captured. Therefore, sampling rate short flows (in total bytes) may not get collected. This sampling size doesn't affect network traffic analysis when sampled data is aggregated over a longer period of time. Flow collection time and sampling rate are fixed and can't be changed.
 
 ## Flow log schema
 
@@ -95,16 +92,57 @@ ExpressRoute Traffic Collector enables flow collection for Azure private peering
 
 ExpressRoute Traffic Collector is supported in the following regions:
 
+### North America
+- Canada East
+- Canada Central
 - Central US
-- East US
-- East US 2
+- Central US EUAP
 - North Central US 
 - South Central US 
-- West Central US 
+- West Central US
+- East US
+- East US 2
 - West US 
 - West US 2 
 - West US 3
 
+### South America
+- Brazil South
+- Brazil Southeast
+
+### Europe
+- West Europe
+- North Europe
+- UK South
+- UK West
+- France Central
+- France South
+- Germany North
+- Sweden Central
+- Sweden South
+- Switzerland North
+- Switzerland West
+- Norway East
+- Norway West
+
+### Asia
+- East Asia
+- Central India
+- South India
+- Japan West
+- Korea South
+- UAE North
+
+### Africa
+- South Africa North
+- South Africa West
+
+### Pacific
+- Australia Central
+- Australia Central 2
+- Australia East
+- Australia Southeast
+
 ## Next steps
 
 - Learn how to [set up ExpressRoute Traffic Collector](how-to-configure-traffic-collector.md).