remove the AzureRM note

halkazwini · halkazwini · commit 79c282ecd913 · 2024-03-05T17:09:47.000-06:00
diff --git a/articles/network-watcher/diagnose-vm-network-routing-problem-powershell.md b/articles/network-watcher/diagnose-vm-network-routing-problem-powershell.md
@@ -19,8 +19,6 @@ In this article, you deploy a virtual machine (VM), and then check communication
 
 If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
 
-[!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]
-
 [!INCLUDE [cloud-shell-try-it.md](../../includes/cloud-shell-try-it.md)]
 
 If you choose to install and use PowerShell locally, this article requires the Azure PowerShell `Az` module. To find the installed version, run `Get-Module -ListAvailable Az`. If you need to upgrade, see [Install Azure PowerShell module](/powershell/azure/install-azure-powershell). If you are running PowerShell locally, you also need to run `Connect-AzAccount` to create a connection with Azure.
diff --git a/articles/network-watcher/network-watcher-connectivity-powershell.md b/articles/network-watcher/network-watcher-connectivity-powershell.md
@@ -21,9 +21,6 @@ ms.custom: devx-track-azurepowershell
 
 Learn how to use connection troubleshoot to verify whether a direct TCP connection from a virtual machine to a given endpoint can be established.
 
-
-[!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]
-
 ## Before you begin
 
 * An instance of Network Watcher in the region you want to troubleshoot a connection.
diff --git a/articles/network-watcher/network-watcher-nsg-auditing-powershell.md b/articles/network-watcher/network-watcher-nsg-auditing-powershell.md
@@ -20,8 +20,6 @@ Customers are often faced with the challenge of verifying the security posture o
 
 To learn more about network security groups, see [Network security groups overview](../virtual-network/network-security-groups-overview.md).
 
-[!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]
-
 ## Prerequisites
 
 - If you don't have an Azure account with an active subscription, [create one for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
diff --git a/articles/network-watcher/network-watcher-packet-capture-manage-powershell-vmss.md b/articles/network-watcher/network-watcher-packet-capture-manage-powershell-vmss.md
@@ -27,9 +27,6 @@ This article takes you through the different management tasks that are currently
 - [**Delete a packet capture**](#delete-a-packet-capture)
 - [**Download a packet capture**](#download-a-packet-capture)
 
-
-[!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]
-
 ## Before you begin
 
 This article assumes you have the following resources:
diff --git a/articles/network-watcher/network-watcher-read-nsg-flow-logs.md b/articles/network-watcher/network-watcher-read-nsg-flow-logs.md
@@ -16,9 +16,6 @@ Learn how to read NSG flow logs entries with PowerShell.
 
 NSG flow logs are stored in a storage account in [block blobs](/rest/api/storageservices/understanding-block-blobs--append-blobs--and-page-blobs). Block blobs are made up of smaller blocks. Each log is a separate block blob that is generated every hour. New logs are generated every hour, the logs are updated with new entries every few minutes with the latest data. In this article you learn how to read portions of the flow logs.
 
-
-[!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]
-
 ## Scenario
 
 In the following scenario, you have an example flow log that is stored in a storage account. You learn how to selectively read the latest events in NSG flow logs. In this article you use PowerShell, however, the concepts discussed in the article are not limited to the programming language, and are applicable to all languages supported by the Azure Storage APIs.
diff --git a/articles/network-watcher/network-watcher-security-group-view-powershell.md b/articles/network-watcher/network-watcher-security-group-view-powershell.md
@@ -18,9 +18,6 @@ ms.custom: devx-track-azurepowershell, engagement-fy23
 
 Security group view returns configured and effective network security rules that are applied to a virtual machine. This capability is useful to audit and diagnose Network Security Groups and rules that are configured on a VM to ensure traffic is being correctly allowed or denied. In this article, we show you how to retrieve the configured and effective security rules to a virtual machine using PowerShell
 
-
-[!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]
-
 ## Before you begin
 
 In this scenario, you run the `Get-AzNetworkWatcherSecurityGroupView` cmdlet to retrieve the security rule information.
diff --git a/articles/network-watcher/view-relative-latencies.md b/articles/network-watcher/view-relative-latencies.md
@@ -20,9 +20,6 @@ ms.custom: devx-track-azurepowershell, engagement-fy23
 
 In this tutorial, learn how to use the Azure [Network Watcher](network-watcher-monitoring-overview.md) service to help you decide what Azure region to deploy your application or service in, based on your user demographic. Additionally, you can use it to help evaluate service providers' connections to Azure.  
         
-
-[!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]
-
 ## Create a network watcher
 
 If you already have a network watcher in at least one Azure [region](https://azure.microsoft.com/regions), you can skip the tasks in this section. Create a resource group for the network watcher. In this example, the resource group is created in the East US region, but you can create the resource group in any Azure region.
