Add a note about we do not configure NSG for Internal Load Balancer

Author: Welasco

articles/load-balancer/upgrade-basic-standard-vmss.md

@@ -110,7 +110,7 @@ Yes, for both public and internal load balancers, the module ensures that front
 The upgrade normally takes a few minutes for the script to finish. The following factors may lead to longer upgrade times:
 - Complexity of your load balancer configuration
 - Number of backend pool members
-- Instance count of associated Virtual Machine Scale Sets. 
+- Instance count of associated Virtual Machine Scale Sets.
 Keep the downtime in mind and plan for failover if necessary.
 
 ### Does the script migrate my backend pool members from my basic load balancer to the newly created standard load balancer?
@@ -158,6 +158,9 @@ The script migrates the following from the Basic load balancer to the Standard l
   - All virtual machine scale set network interfaces and IP configurations will be migrated to the new Standard load balancer
   - If there's a virtual machine scale set using Rolling Upgrade policy, the script will update the virtual machine scale set upgrade policy to "Manual" during the migration process and revert it back to "Rolling" after the migration is completed.
 
+>[!NOTE]
+> Network security group are not configured as part of Internal Load Balancer upgrade. To learn more about NSGs, see [Network security groups](/azure/virtual-network/network-security-groups-overview)
+
 ### What happens if my upgrade fails mid-migration?
 
 The module is designed to accommodate failures, either due to unhandled errors or unexpected script termination. The failure design is a 'fail forward' approach, where instead of attempting to move back to the Basic load balancer, you should correct the issue causing the failure (see the error output or log file), and retry the migration again, specifying the `-FailedMigrationRetryFilePathLB <BasicLoadBalancerbackupFilePath> -FailedMigrationRetryFilePathVMSS <VMSSBackupFile>` parameters. For public load balancers, because the Public IP Address SKU has been updated to Standard, moving the same IP back to a Basic load balancer won't be possible. The basic failure recovery procedure is: