Merge pull request #219116 from v-ksreedevan/21Nov-NWContentFreshnessUpdate

Updated the date of the last major commit

Author: ttorble

articles/network-watcher/azure-monitor-agent-with-connection-monitor.md

@@ -4,9 +4,9 @@ description: This article describes how to monitor network connectivity in Conne
 services: network-watcher
 author: v-ksreedevan
 ms.service: network-watcher
-ms.custom: ignite-2022
+ms.custom: ignite-2022, engagement-fy23
 ms.topic: how-to
-ms.date: 09/11/2022
+ms.date: 10/27/2022
 ms.author: v-ksreedevan
 #Customer intent: I need to monitor a connection by using Azure Monitor Agent.
 ---
@@ -38,7 +38,7 @@ Connection Monitor relies on lightweight executable files to run connectivity ch
 
 ### Agents for Azure virtual machines and scale sets
 
-To install agents for Azure virtual machines and virtual machine scale sets, see the "Agents for Azure virtual machines and virtual machine scale sets" section of [Monitor network connectivity by using Connection Monitor](connection-monitor-overview.md#agents-for-azure-virtual-machines-and-virtual-machine-scale-sets).
+To install agents for Azure virtual machines and Virtual Machine Scale Sets, see the "Agents for Azure virtual machines and Virtual Machine Scale Sets" section of [Monitor network connectivity by using Connection Monitor](connection-monitor-overview.md#agents-for-azure-virtual-machines-and-virtual-machine-scale-sets).
 
 ### Agents for on-premises machines
 

articles/network-watcher/connection-monitor-connected-machine-agent.md

@@ -4,9 +4,9 @@ description: This article describes how to install Azure Connected Machine agent
 services: network-watcher
 author: v-ksreedevan
 ms.service: network-watcher
-ms.custom: ignite-2022
+ms.custom: ignite-2022, engagement-fy23
 ms.topic: how-to
-ms.date: 09/11/2022
+ms.date: 10/27/2022
 ms.author: v-ksreedevan
 #Customer intent: I need to monitor a connection by using Azure Monitor Agent.
 ---

articles/network-watcher/connection-monitor-create-using-portal.md

@@ -7,8 +7,8 @@ author: vinynigam
 ms.service: network-watcher
 ms.topic: how-to
 ms.workload:  infrastructure-services
-ms.custom: ignite-2022
-ms.date: 11/23/2020
+ms.custom: ignite-2022, engagement-fy23
+ms.date: 11/05/2022
 ms.author: vinigam
 #Customer intent: I need to create a connection monitor to monitor communication between one VM and another.
 ---
@@ -22,11 +22,11 @@ This article describes how to create a monitor in Connection Monitor by using th
 > To minimize service disruption to your current workloads, [migrate your tests from Network Performance Monitor ](migrate-to-connection-monitor-from-network-performance-monitor.md) or  [migrate from Connection Monitor (classic)](migrate-to-connection-monitor-from-connection-monitor-classic.md) to the new connection monitor in Azure Network Watcher before February 19, 2024.
 
 > [!IMPORTANT]
-> Connection Monitor supports end-to-end connectivity checks from and to Azure virtual machine scale sets. These checks enable faster performance monitoring and network troubleshooting across scale sets. 
+> Connection Monitor supports end-to-end connectivity checks from and to Azure Virtual Machine Scale Sets. These checks enable faster performance monitoring and network troubleshooting across scale sets. 
 
 ## Before you begin 
 
-In monitors that you create by using Connection Monitor, you can add on-premises machines, Azure virtual machines (VMs), and Azure virtual machine scale sets as sources. These connection monitors can also monitor connectivity to endpoints. The endpoints can be on Azure or on any other URL or IP.
+In monitors that you create by using Connection Monitor, you can add on-premises machines, Azure virtual machines (VMs), and Azure Virtual Machine Scale Sets as sources. These connection monitors can also monitor connectivity to endpoints. The endpoints can be on Azure or on any other URL or IP.
 
 Here are some definitions to get you started:
 
@@ -111,7 +111,7 @@ In the Azure portal, to create a test group in a connection monitor, specify val
 
 * **Test group Name**: Enter the name of your test group.
 * **Sources**: Select **Add sources** to specify both Azure VMs and on-premises machines as sources if agents are installed on them. To learn about installing an agent for your source, see [Install monitoring agents](./connection-monitor-overview.md#install-monitoring-agents).
-   * To choose Azure agents, select the **Azure endpoints** tab. Here you see only VMs or virtual machine scale sets that are bound to the region that you specified when you created the connection monitor. By default, VMs and virtual machine scale sets are grouped into the subscription that they belong to. These groups are collapsed. 
+   * To choose Azure agents, select the **Azure endpoints** tab. Here you see only VMs or Virtual Machine Scale Sets that are bound to the region that you specified when you created the connection monitor. By default, VMs and Virtual Machine Scale Sets are grouped into the subscription that they belong to. These groups are collapsed. 
 
        You can drill down to further levels in the hierarchy from the **Subscription** level:
 
@@ -121,7 +121,7 @@ In the Azure portal, to create a test group in a connection monitor, specify val
 
       When you select a virtual network, subnet, a single VM, or a virtual machine scale set, the corresponding resource ID is set as the endpoint. By default, all VMs in the selected virtual network or subnet participate in monitoring. To reduce the scope, either select specific subnets or agents or change the value of the scope property. 
 
-      :::image type="content" source="./media/connection-monitor-2-preview/add-sources-1.png" alt-text="Screenshot that shows the 'Add Sources' pane and the Azure endpoints, including the 'Virtual machine scale sets' tab in Connection Monitor.":::
+      :::image type="content" source="./media/connection-monitor-2-preview/add-sources-1.png" alt-text="Screenshot that shows the 'Add Sources' pane and the Azure endpoints, including the 'Virtual Machine Scale Sets' tab in Connection Monitor.":::
 
    * To choose on-premises agents, select the **Non–Azure endpoints** tab. Select from a list of on-premises hosts with a Log Analytics agent installed. Select **Arc Endpoint** as the **Type**, and select the subscriptions from the **Subscription** dropdown list. The list of hosts that have the [Azure Arc endpoint](azure-monitor-agent-with-connection-monitor.md) extension and the [Azure Monitor Agent extension](connection-monitor-install-azure-monitor-agent.md) enabled are displayed.
 
@@ -184,9 +184,9 @@ In the Azure portal, to create a test group in a connection monitor, specify val
    :::image type="content" source="./media/connection-monitor-2-preview/add-test-config.png" alt-text="Screenshot that shows where to set up a test configuration in Connection Monitor.":::
 
 * **Test Groups**: You can add one or more test groups to a connection monitor. These test groups can consist of multiple Azure or non-Azure endpoints.
-    * For selected Azure VMs or Azure virtual machine scale sets and non-Azure endpoints without monitoring extensions, the extension for Azure VMs and the npm solution for non-Azure endpoints will be auto enabled after the creation of the connection monitor begins.
+    * For selected Azure VMs or Azure Virtual Machine Scale Sets and non-Azure endpoints without monitoring extensions, the extension for Azure VMs and the npm solution for non-Azure endpoints will be auto enabled after the creation of the connection monitor begins.
     * If the selected virtual machine scale set is set for a manual upgrade, you'll have to upgrade the scale set after Network Watcher extension installation to continue setting up the connection monitor with virtual machine scale set as endpoints. If the virtual machine scale set is set to auto upgrade, you don't need to worry about any upgrading after the Network Watcher extension is installed.
-    * In the previously mentioned scenario, you can consent to an auto upgrade of a virtual machine scale set with auto enabling of the Network Watcher extension during the creation of the connection monitor for virtual machine scale sets with manual upgrading. This would eliminate your having to manually upgrade the virtual machine scale set after you install the Network Watcher extension.   
+    * In the previously mentioned scenario, you can consent to an auto upgrade of a virtual machine scale set with auto enabling of the Network Watcher extension during the creation of the connection monitor for Virtual Machine Scale Sets with manual upgrading. This would eliminate your having to manually upgrade the virtual machine scale set after you install the Network Watcher extension.   
 
    :::image type="content" source="./media/connection-monitor-2-preview/consent-vmss-auto-upgrade.png" alt-text="Screenshot that shows where to set up test groups and consent for auto-upgrading of a virtual machine scale set in the connection monitor.":::
 * **Disable test group**: You can select this checkbox to disable monitoring for all sources and destinations that the test group specifies. This checkbox is cleared by default.

articles/network-watcher/connection-monitor-create-using-template.md

@@ -9,14 +9,15 @@ ms.service: network-watcher
 ms.topic: how-to
 ms.tgt_pltfrm: na
 ms.workload:  infrastructure-services
-ms.date: 01/07/2021
+ms.date: 02/08/2021
+ms.custom: engagement-fy23
 ms.author: vinigam
 #Customer intent: I need to create a connection monitor to monitor communication between one VM and another.
 ---
 # Create a Connection Monitor using the ARM template
 
 > [!IMPORTANT]
-> Starting 1 July 2021, you will not be able to add new tests in an existing workspace or enable a new workspace in Network Performance Monitor. You will also not be able to add new connection monitors in Connection Monitor (classic). You can continue to use the tests and connection monitors created prior to 1 July 2021. To minimize service disruption to your current workloads, [migrate your tests from Network Performance Monitor ](migrate-to-connection-monitor-from-network-performance-monitor.md) or  [migrate from Connection Monitor (classic)](migrate-to-connection-monitor-from-connection-monitor-classic.md) to the new Connection Monitor in Azure Network Watcher before 29 February 2024.
+> Starting 1 July 2021, you'll not be able to add new tests in an existing workspace or enable a new workspace in Network Performance Monitor. You'll also not be able to add new connection monitors in Connection Monitor (classic). You can continue to use the tests and connection monitors created prior to 1 July 2021. To minimize service disruption to your current workloads, [migrate your tests from Network Performance Monitor ](migrate-to-connection-monitor-from-network-performance-monitor.md) or  [migrate from Connection Monitor (classic)](migrate-to-connection-monitor-from-connection-monitor-classic.md) to the new Connection Monitor in Azure Network Watcher before 29 February 2024.
 
 Learn how to create Connection Monitor to monitor communication between your resources using the ARMClient. It supports hybrid and Azure cloud deployments.
 
@@ -221,7 +222,7 @@ address: '<URL>'
     
      port: '<port of choice>'
   
-    preferHTTPS: true // If port chosen is not 80 or 443
+    preferHTTPS: true // If port chosen isn't 80 or 443
     
     method: 'GET', //Choose GET or POST
     
@@ -357,9 +358,9 @@ armclient PUT $ARM/$SUB/$NW/connectionMonitors/$connectionMonitorName/?api-versi
 
 * Endpoints
 	* name – Unique name for each endpoint
-	* resourceId – For Azure endpoints, resource ID refers to the Azure Resource Manager resource ID for virtual machines.For non-Azure endpoints, resource ID refers to the Azure Resource Manager resource ID for the Log Analytics workspace linked to non-Azure agents.
-	* address – Applicable only when either resource ID is not specified or if resource ID is Log Analytics workspace. If used with Log Analytics resource ID, this refers to the FQDN of the agent that can be used for monitoring. If used without resource ID, this can be the URL or IP of any public endpoint.
-	* filter – For non-Azure endpoints, use filter to select agents from Log Analytics workspace that will be used for monitoring in Connection monitor resource. If filters are not set, all agents belonging to the Log Analytics workspace can be used for monitoring
+	* resourceId – For Azure endpoints, resource ID refers to the Azure Resource Manager resource ID for virtual machines. For non-Azure endpoints, resource ID refers to the Azure Resource Manager resource ID for the Log Analytics workspace linked to non-Azure agents.
+	* address – Applicable only when either resource ID isn't specified or if resource ID is Log Analytics workspace. If used with Log Analytics resource ID, this refers to the FQDN of the agent that can be used for monitoring. If used without resource ID, this can be the URL or IP of any public endpoint.
+	* filter – For non-Azure endpoints, use filter to select agents from Log Analytics workspace that will be used for monitoring in Connection monitor resource. If filters aren't set, all agents belonging to the Log Analytics workspace can be used for monitoring
 		* type – Set type as “Agent Address”
 		* address – Set address as the FQDN of your on-premises agent
 
@@ -377,10 +378,10 @@ armclient PUT $ARM/$SUB/$NW/connectionMonitors/$connectionMonitorName/?api-versi
 
 		* preferHTTPS - Specify whether to use HTTPS over HTTP, when port used is neither 80 nor 443
 		* port - Specify the destination port of your choice.
-		* disableTraceRoute - This applies to test configurations whose protocol is TCP or ICMP. It stop sources from discovering topology and hop-by-hop RTT.
+		* disableTraceRoute - This applies to test configurations whose protocol is TCP or ICMP. It stops sources from discovering topology and hop-by-hop RTT.
 		* method - This applied to test configurations whose protocol is HTTP. Select the HTTP request method--either GET or POST
 		* path - Specify path parameters to append to URL
-		* validStatusCodes - Choose applicable status codes. If response code does not match this list, you will get a diagnostic message
+		* validStatusCodes - Choose applicable status codes. If response code doesn't match this list, you'll get a diagnostic message
 		* requestHeaders - Specify custom request header strings that will make be passed to the destination
 		
 	* successThreshold - You can set thresholds on the following network parameters:

articles/network-watcher/connection-monitor-install-azure-monitor-agent.md

@@ -6,7 +6,7 @@ author: v-ksreedevan
 ms.service: network-watcher
 ms.custom: ignite-2022
 ms.topic: how-to
-ms.date: 09/11/2022
+ms.date: 10/25/2022
 ms.author: v-ksreedevan
 #Customer intent: I need to monitor a connection by using Azure Monitor Agent.
 ---

articles/network-watcher/connection-monitor-overview.md

@@ -7,14 +7,13 @@ author: vinynigam
 manager: agummadi
 editor: ''
 tags: azure-resource-manager
-
 ms.service: network-watcher
 ms.topic: how-to
 ms.tgt_pltfrm: na
 ms.workload:  infrastructure-services
-ms.date: 01/04/2021
+ms.date: 10/04/2022
 ms.author: vinigam
-ms.custom: mvc
+ms.custom: mvc, engagement-fy23
 #Customer intent: I need to monitor communication between one VM and another. If the communication fails, I need to know why so that I can resolve the problem. 
 ---
 # Monitor network connectivity by using Connection Monitor

articles/network-watcher/connection-monitor-schema.md

@@ -5,14 +5,13 @@ services: network-watcher
 documentationcenter: na
 author: mjha
 manager: vinigam
-editor:
-
 ms.service: network-watcher
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload:  infrastructure-services
-ms.date: 07/05/2021
+ms.date: 08/14/2021
 ms.author: mjha
+ms.custom: engagement-fy23
 ---
 
 # Azure Network Watcher Connection Monitor schemas