Merge pull request #272627 from halkazwini/nw-migrate

Add screenshot

Author: American-Dipper

articles/network-watcher/media/nsg-flow-logs-migrate/list-flow-logs.png

@@ -1,14 +1,14 @@
 ---
 title: Migrate to VNet flow logs
 titleSuffix: Azure Network Watcher
-description: Learn how to migrate your Azure Network Watcher NSG flow logs to VNet flow logs using the Azure portal and PowerShell.
+description: Learn how to migrate your Azure Network Watcher NSG flow logs to VNet flow logs using the Azure portal and a PowerShell script.
 author: halkazwini
 ms.author: halkazwini
 ms.service: network-watcher
 ms.topic: how-to
-ms.date: 04/16/2024
+ms.date: 04/18/2024
 
-#CustomerIntent: As an Azure administrator, I want to learn how to migrate my NSG flow logs to the new VNet flow logs so that I can use VNet flow logs to log my virtual network IP traffic.
+#CustomerIntent: As an Azure administrator, I want to migrate my NSG flow logs to the new VNet flow logs so that I can use all the benefits of VNet flow logs, which overcome some of the NSG flow logs limitations..
 ---
 
 # Migrate from NSG flow logs to VNet flow logs
@@ -22,7 +22,7 @@ In this article, you learn how to migrate your existing NSG flow logs to VNet fl
 
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 
-- PowerShell 7. For more information, see [Install PowerShell on Windows, Linux, and macOS](/powershell/scripting/install/installing-powershell). This article requires the Az PowerShell module. For more information, see [How to install Azure PowerShell](/powershell/azure/install-azure-powershell). To find the installed version, run `Get-Module -ListAvailable Az`. 
+- PowerShell installed on your machine. For more information, see [Install PowerShell on Windows, Linux, and macOS](/powershell/scripting/install/installing-powershell). This article requires the Az PowerShell module. For more information, see [How to install Azure PowerShell](/powershell/azure/install-azure-powershell). To find the installed version, run `Get-Module -ListAvailable Az`. 
 
 - Necessary RBAC permissions for subscriptions of the flow logs and Log Analytics workspaces if traffic analytics is enabled for any of the NSG flow logs. For more information, see [Network Watcher RBAC permissions](required-rbac-permissions.md).
 
@@ -84,7 +84,7 @@ In this section, you learn how to use the script file that you downloaded in the
     Please enter the number of threads you would like to use, press enter for using default value of 16:    
     ```
 
-    After the analysis is complete, you'll see the analysis report on screen and in an html file in the same directory of the migration files. The report lists the number of NSG flow logs that will be disabled and the number of VNet flow logs that are created to replace them. The number of VNet flow logs that will be created depends on the type of migration that you choose. For example, if the network security group that you're migrating its flow log is associated with three network interfaces in the same virtual network, then you can choose *migration with aggregation* to have a single VNet flow log resource applied to the virtual network. You can also choose *migration without aggregation* to have three VNet flow logs (one VNet flow log resource per network interface).
+    After the analysis is complete, you'll see the analysis report on screen and in an html file in the same directory of the migration files. The report lists the number of NSG flow logs that will be disabled and the number of VNet flow logs that are created to replace them. The number of VNet flow logs that are created depends on the type of migration that you choose. For example, if the network security group that you're migrating its flow log is associated with three network interfaces in the same virtual network, then you can choose *migration with aggregation* to have a single VNet flow log resource applied to the virtual network. You can also choose *migration without aggregation* to have three VNet flow logs (one VNet flow log resource per network interface).
 
     > [!NOTE]
     > See `AnalysisReport-<subscriptionId>-<region>-<time>.html` file for a full report of the analysis that you performed. The file is available in the same directory of the script.
@@ -99,15 +99,19 @@ In this section, you learn how to use the script file that you downloaded in the
     4. Quit
     ```
 
-1. After the migration is completed successfully, you can cancel the migration and revert changes. To accept the migration enter **n**, otherwise enter **y**. Once you accept the changes you can't revert them.
+1. After you see the summary of migration on screen, you can cancel the migration and revert changes. To accept and proceed with the migration enter **n**, otherwise enter **y**. Once you accept the changes, you can't revert them.
 
     ```
     Do you want to rollback? You won't get the option to revert the actions done now again (y/n): n
     ```
 
-> [!NOTE]
-> Keep the script and analysis report files for reference in case you have any issues with the migration.
+1. Check the Azure portal to confirm that the status of NSG flow logs that you migrated became disabled, and VNet flow logs are created to replace them.
+ 
+    :::image type="content" source="./media/nsg-flow-logs-migrate/list-flow-logs.png" alt-text="Screenshot that shows the newly created VNet flow log as a result of migrating from NSG flow log." lightbox="./media/nsg-flow-logs-migrate/list-flow-logs.png":::
 
+    > [!NOTE]
+    > Keep the script and analysis report files for reference in case you have any issues with the migration.
+    
 ## Related content
 
 - [NSG flow logs](nsg-flow-logs-overview.md)