Last review

Julia Shimanskiy · Julia Shimanskiy · commit 40e5fc517b61 · 2021-10-26T14:04:29.000-07:00
diff --git a/articles/virtual-machine-scale-sets/orchestration-modes-api-comparison.md b/articles/virtual-machine-scale-sets/orchestration-modes-api-comparison.md
@@ -53,6 +53,21 @@ Invoke Single VM APIs:
 - [ARM Lock Resource](../azure-resource-manager/management/lock-resources.md?tabs=json) for Instance Protection type behavior 
     
 
+## Get or Update scale set VM instances
+
+| Uniform API | Flexible alternative |
+|-|-|
+| [Get scale set VM details](/rest/api/compute/virtualmachinescalesetvms/get) | [Get virtual machine](/rest/api/compute/virtualmachines/get) |
+| [Update scale set VM instance](/rest/api/compute/virtualmachinescalesetvms/update) | [Update virtual machine](/rest/api/compute/virtualmachines/update) |
+
+
+## Instance protection 
+
+| Uniform API | Flexible alternative |
+|-|-|
+| [Instance Protection](virtual-machine-scale-sets-instance-protection.md) | [ARM Lock Resource](../azure-resource-manager/management/lock-resources.md?tabs=json) for Instance Protection type behavior | 
+
+
 ## List instances 
 
 **Uniform API:**
@@ -70,7 +85,7 @@ resources
 | where properties.virtualMachineScaleSet.id contains "portalbb01" 
 ```
 
-## Scale set operations 
+## Scale set instance operations 
 
 **Uniform API:**
 
diff --git a/articles/virtual-machine-scale-sets/quick-create-portal.md b/articles/virtual-machine-scale-sets/quick-create-portal.md
@@ -57,7 +57,7 @@ You can deploy a scale set with a Windows Server image or Linux image such as RH
 1. In the **Basics** tab, under **Project details**, make sure the correct subscription is selected and select *myVMSSResourceGroup* from resource group list. 
 1. Type *myScaleSet* as the name for your scale set.
 1. In **Region**, select a region that is close to your area.
-1. Under **Orchestration**, select the *Uniform* option for **Orchestration mode**. 
+1. Under **Orchestration**, ensure the *Uniform* option is selected for **Orchestration mode**. 
 1. Select a marketplace image for **Image**. In this example, we have chosen *Ubuntu Server 18.04 LTS*.
 1. Enter your desired username, and select which authentication type you prefer.
    - A **Password** must be at least 12 characters long and meet three out of the four following complexity requirements: one lower case character, one upper case character, one number, and one special character. For more information, see [username and password requirements](../virtual-machines/windows/faq.yml#what-are-the-password-requirements-when-creating-a-vm-).
diff --git a/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes.md b/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes.md
@@ -110,7 +110,7 @@ The following table compares the Flexible orchestration mode, Uniform orchestrat
 | Managed Identity  | User Assigned Identity Only  | System Assigned or User Assigned  | N/A (can specify Managed Identity on individual instances) |
 | Add/remove existing VM to the group  | No  | No  | No |
 | Service Fabric  | No  | Yes  | No |
-| Azure Kubernetes Service (AKS) / AKE / k8s node pool  | No  | Yes  | No |
+| Azure Kubernetes Service (AKS) / AKE  | No  | Yes  | No |
 | UserData  | Partial, UserData can be specified for individual VMs | Yes  | UserData can be specified for individual VMs |
 
 
diff --git a/articles/virtual-machines/flexible-virtual-machine-scale-sets-migration-resources.md b/articles/virtual-machines/flexible-virtual-machine-scale-sets-migration-resources.md
@@ -86,9 +86,9 @@ Virtual machine scale sets with Flexible orchestration allows you to combine the
 /virtual-machines/flexible-virtual-machine-scale-sets-migration-resources.md#create-scalable-network-connectivity
 -->
 
-Networking behavior will vary depending on how you choose to create virtual machines within your scale set. **Manually added VM instances** have default outbound connectivity access. **Implicitly created VM instances** do not have default access. 
+Networking outbound access behavior will vary depending on how you choose to create virtual machines within your scale set. **Manually added VM instances** have default outbound connectivity access. **Implicitly created VM instances** do not have default access. 
 
-In order to enhance default network security, Virtual machine scale sets with Flexible orchestration will require that instances created implicitly via the autoscaling profile have outbound connectivity defined explicitly through one of the following methods: 
+In order to enhance default network security, **virtual machine instances created implicitly via the autoscaling profile do not have default outbound access**. In order to use virtual machine scale sets with implicitly created VM instances, outbound access must be explicitly defined through one of the following methods: 
 
 - For most scenarios, we recommend [NAT Gateway attached to the subnet](../virtual-network/nat-gateway/tutorial-create-nat-gateway-portal.md).
 - For scenarios with high security requirements or when using Azure Firewall or Network Virtual Appliance (NVA), you can specify a custom User Defined Route as next hop through firewall. 
@@ -99,10 +99,12 @@ Common scenarios that will require explicit outbound connectivity include:
 
 - Windows VM activation will require that you have defined outbound connectivity from the VM instance to the Windows Activation Key Management Service (KMS). See [Troubleshoot Windows VM activation problems](/troubleshoot/azure/virtual-machines/troubleshoot-activation-problems) for more information.  
 - Access to storage accounts or Key Vault. Connectivity to Azure services can also be established via [Private Link](../private-link/private-link-overview.md). 
+- Windows updates.
+- Access to Linux package managers. 
 
-See [Default outbound access in Azure](../virtual-network/ip-services/default-outbound-access.md) for more details on defining secure outbound connections.
+See [Default outbound access in Azure](../virtual-network/ip-services/default-outbound-access.md) for more details on defining  outbound connectivity.
 
-With single instance VMs and virtual machine scale sets with Uniform orchestration, outbound connectivity is provided automatically. 
+With single instance VMs where you explicitly create the NIC, default outbound access is provided. Virtual machine scale sets in Uniform Orchestration mode also has default outbound connectivity. 
 
 
 > [!IMPORTANT]
diff --git a/articles/virtual-machines/flexible-virtual-machine-scale-sets-portal.md b/articles/virtual-machines/flexible-virtual-machine-scale-sets-portal.md
@@ -26,32 +26,6 @@ This article steps through using Azure portal to create a virtual machine scale
 Log in to the Azure portal at https://portal.azure.com.
 
 
-## Create a load balancer
-
-Azure [load balancer](../load-balancer/load-balancer-overview.md) distributes incoming traffic among healthy virtual machine instances. 
-
-First, create a public Standard Load Balancer by using the portal. The name and public IP address you create are automatically configured as the load balancer's front end.
-
-1. In the Azure portal search box, type *load balancer*. Under **Marketplace** in the search results, pick **Load balancer**.
-1. In the **Basics** tab of the **Create load balancer** page, enter or select the following information:
-
-    | Setting                 | Value   |
-    | ---| ---|
-    | Subscription  | Select your subscription.    |    
-    | Resource group | Select **Create new** and type *myVMSSResourceGroup* in the text box.|
-    | Name           | *myLoadBalancer*         |
-    | Region         | Select **East US**.       |
-    | Type          | Select **Public**.       |
-    | SKU           | Select **Standard**.       |
-    | Public IP address | Select **Create new**. |
-    | Public IP address name  | *myPip*   |
-    | Assignment| Static |
-    | Availability zone | Select **Zone-redundant**. |
-
-1. When you are done, select **Review + create** 
-1. After it passes validation, select **Create**. 
-
-
 ## Create a virtual machine scale set
 
 You can deploy a scale set with a Windows Server image or Linux image such as RHEL, CentOS, Ubuntu, or SLES.
@@ -75,7 +49,7 @@ You can deploy a scale set with a Windows Server image or Linux image such as RH
 
 1. On the **Networking** page, under **Load balancing**, select the **Use a load balancer** checkbox to put the scale set instances behind a load balancer. 
 1. In **Load balancing options**, select **Azure load balancer**.
-1. In **Select a load balancer**, select *myLoadBalancer* that you created earlier.
+1. In **Select a load balancer**, select a load balancer or create a new one.
 1. For **Select a backend pool**, select **Create new**, type *myBackendPool*, then select **Create**.
 
 > [!NOTE]
diff --git a/articles/virtual-machines/flexible-virtual-machine-scale-sets.md b/articles/virtual-machines/flexible-virtual-machine-scale-sets.md
@@ -119,7 +119,7 @@ The following tables list the Flexible orchestration mode features and links to
 | Managed Identity  | User Assigned Identity Only  |
 | Add/remove existing VM to the group  | No  |
 | Service Fabric  | No  |
-| Azure Kubernetes Service (AKS) / AKE / k8s node pool  | No  |
+| Azure Kubernetes Service (AKS) / AKE  | No  |
 | UserData  | Partial, UserData can be specified for individual VMs |
 
 
