Merge pull request #272314 from halkazwini/nw-migrate

Tweaks

Author: prmerger-automator[bot]

articles/network-watcher/nsg-flow-logs-migrate.md

@@ -6,7 +6,7 @@ author: halkazwini
 ms.author: halkazwini
 ms.service: network-watcher
 ms.topic: how-to
-ms.date: 04/15/2024
+ms.date: 04/16/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.
 ---
@@ -15,6 +15,9 @@ ms.date: 04/15/2024
 
 In this article, you learn how to migrate your existing NSG flow logs to VNet flow logs. VNet flow logs overcome some of the limitations of NSG flow logs. For more information, see [VNet flow logs](vnet-flow-logs-overview.md).
 
+> [!IMPORTANT]
+> The VNet flow logs feature is currently in preview. This preview version is provided without a service-level agreement, and we don't recommend it for production workloads. Certain features might not be supported or might have constrained capabilities. For legal terms that apply to Azure features that are in beta, in preview, or otherwise not yet released into general availability, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
+
 ## Prerequisites
 
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
@@ -53,11 +56,8 @@ In this section, you learn how to generate and download the migration files for
 
 In this section, you learn how to use the script file that you downloaded in the previous section to migrate your NSG flow logs.
 
-1. Use [Connect-AzAccount](/powershell/module/az.accounts/connect-azaccount) to sign in to Azure with the subscription that contains the NSG flow logs that you want to migrate.
-
-    ```powershell
-    Connect-AzAccount -Subscription 'mySubscription'
-    ```
+> [!IMPORTANT]
+> Once you start running the script, you shouldn't make any changes to the topology in the regions and subscriptions of the flow logs that you're migrating. 
 
 1. Run the script file `MigrationFromNsgToAzureFlowLogging.ps1`.
 
@@ -78,14 +78,17 @@ In this section, you learn how to use the script file that you downloaded in the
     Please enter the path to scope selecting config file: .\RegionSubscriptionConfig.json
     ```
 
-1. Enter **16** for the number of threads or press enter.
+1. Enter the number of threads or leave blank to use the default value of 16.
 
     ```powershell
-    Please enter the number of threads you would like to use, press enter for using default value of 16: 16  
+    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).
 
+    > [!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.
+
 1. Enter **2** or **3** to choose the type of migration that you want to perform.
 
     ```powershell
@@ -96,8 +99,14 @@ 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.
+
+    ```powershell
+    Do you want to rollback? You won't get the option to revert the actions done now again (y/n): n
+    ```
+
 > [!NOTE]
-> See `AnalysisReport-<subscriptionId>-<region>-<time>.html` file for a full report of the migration that you performed. The file is available in the same directory of the script.
+> Keep the script and analysis report files for reference in case you have any issues with the migration.
 
 ## Related content