Merge pull request #176202 from ju-shim/flex-1018

Flex 1018

Author: Court72

articles/azure-monitor/vm/vminsights-overview.md

@@ -15,7 +15,7 @@ VM insights monitors the performance and health of your virtual machines and vir
 VM insights supports Windows and Linux operating systems on the following machines:
 
 - Azure virtual machines
-- Azure virtual machine scale sets in Uniform orchestration mode
+- Azure virtual machine scale sets
 - Hybrid virtual machines connected with Azure Arc
 - On-premises virtual machines
 - Virtual machines hosted in another cloud environment

articles/virtual-machine-scale-sets/TOC.yml

@@ -190,7 +190,7 @@
   - name: Endorsed Linux distros
     href: ../virtual-machines/linux/endorsed-distros.md
     maintainContext: true
-  - name: Orchestration modes (preview)
+  - name: Orchestration modes
     items:
     - name: Overview 
       href: virtual-machine-scale-sets-orchestration-modes.md

articles/virtual-machine-scale-sets/orchestration-modes-api-comparison.md

@@ -85,6 +85,8 @@ Virtual machine scale sets Operations:
 ### Flexible alternative
 Invoke operations on individual VMs.
 
+Virtual machines Operations:
+- [Reimage](/rest/api/compute/virtual-machines/reimage): invoke single VM API - Reimage on Ephemeral OS VMs only
 
 ## VM extension
 

articles/virtual-machine-scale-sets/overview.md

@@ -12,12 +12,10 @@ ms.reviewer: mimckitt
 ---
 # What are virtual machine scale sets?
 
-> [!IMPORTANT]
-> The following article is about virtual machine scale sets in Uniform orchestration mode. We recommend using using [Flexible orchestration mode](../virtual-machines/flexible-virtual-machine-scale-sets.md) for all new scale set deployments. 
-
-
 Azure virtual machine scale sets let you create and manage a group of load balanced VMs. The number of VM instances can automatically increase or decrease in response to demand or a defined schedule. Scale sets provide high availability to your applications, and allow you to centrally manage, configure, and update a large number of VMs. With virtual machine scale sets, you can build large-scale services for areas such as compute, big data, and container workloads.
 
+> [!IMPORTANT]
+> This article is about virtual machine scale sets in Uniform orchestration mode. To learn more about Flexible scale sets, go to [Flexible orchestration mode for virtual machine scale sets](../virtual-machines/flexible-virtual-machine-scale-sets.md).
 
 ## Why use virtual machine scale sets?
 To provide redundancy and improved performance, applications are typically distributed across multiple instances. Customers may access your application through a load balancer that distributes requests to one of the application instances. If you need to perform maintenance or update an application instance, your customers must be distributed to another available application instance. To keep up with extra customer demand, you may need to increase the number of application instances that run your application.

articles/virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes.md

@@ -44,6 +44,9 @@ With Flexible orchestration, Azure provides a unified experience across the Azur
 ## What has changed with Flexible orchestration mode?
 One of the main advantages of Flexible orchestration is that it provides orchestration features over standard Azure IaaS VMs, instead of scale set child virtual machines. This means you can use all of the standard VM APIs when managing Flexible orchestration instances, instead of the virtual machine scale set VM APIs you use with Uniform orchestration. There are several differences between managing instances in Flexible orchestration versus Uniform orchestration. In general, we recommend that you use the standard Azure IaaS VM APIs when possible. In this section, we highlight examples of best practices for managing VM instances with Flexible orchestration.
 
+### Scale out with standard Azure virtual machines
+Virtual machine scale sets in Flexible Orchestration mode manages standard Azure VMs. You have full control over the virtual machine lifecycle, as well as network interfaces and disks using the standard Azure APIs and commands. Virtual machines created with Uniform orchestration mode are exposed and managed via the virtual machine scale set VM API commands. Individual instances are not compatible with the standard Azure IaaS VM API commands, Azure management features such as Azure Resource Manager resource tagging RBAC permissions, Azure Backup, or Azure Site Recovery.
+
 ### Assign fault domain during VM creation
 You can choose the number of fault domains for the Flexible orchestration scale set. By default, when you add a VM to a Flexible scale set, Azure evenly spreads instances across fault domains. While it is recommended to let Azure assign the fault domain, for advanced or troubleshooting scenarios you can override this default behavior and specify the fault domain where the instance will land.
 
@@ -93,7 +96,7 @@ The following table compares the Flexible orchestration mode, Uniform orchestrat
 | Feature | Supported by Flexible orchestration for scale sets | Supported by Uniform orchestration for scale sets | Supported by Availability Sets |
 |---|---|---|---|
 | Virtual machine type  | Standard Azure IaaS VM (Microsoft.compute/virtualmachines)  | Scale Set specific VMs (Microsoft.compute/virtualmachinescalesets/virtualmachines)  | Standard Azure IaaS VM (Microsoft.compute/virtualmachines) |
-| Maximum Instance Count  | 1000  | 3000 (1000 per Availability Zone)  | 200 |
+| Maximum Instance Count (with FD guarantees)  | 1000  | 100  | 200 |
 | SKUs supported  | D series, E series, F series, A series, B series, Intel, AMD; Specialty SKUs (G, H, L, M, N) are not supported | All SKUs  | All SKUs |
 | Full control over VM, NICs, Disks  | Yes  | Limited control with virtual machine scale sets VM API  | Yes  |
 | RBAC Permissions Required  | Compute VMSS Write, Compute VM Write, Network | Compute VMSS Write  | N/A |
@@ -123,7 +126,7 @@ The following table compares the Flexible orchestration mode, Uniform orchestrat
 | Terminate Notifications (VM scale sets) | Yes, read [Terminate Notifications documentation](../virtual-machine-scale-sets/virtual-machine-scale-sets-terminate-notification.md) | Yes, read [Terminate Notifications documentation](../virtual-machine-scale-sets/virtual-machine-scale-sets-terminate-notification.md) | N/A |
 | Monitor Application Health | Application health extension | Application health extension or Azure load balancer probe | Application health extension |
 | Instance Repair (VM scale sets) | Yes, read [Instance Repair documentation](../virtual-machine-scale-sets/virtual-machine-scale-sets-automatic-instance-repairs.md) | Yes, read [Instance Repair documentation](../virtual-machine-scale-sets/virtual-machine-scale-sets-automatic-instance-repairs.md) | N/A |
-| Instance Protection | No | Yes | No |
+| Instance Protection | No, use [Azure resource lock](../azure-resource-manager/management/lock-resources.md) | Yes | No |
 | Scale In Policy | No | Yes | No |
 | VMSS Get Instance View | No | Yes | N/A |
 | Perform Maintenance | No (can trigger maintenance on each instance using VM API) | Yes | N/A |
@@ -133,20 +136,20 @@ The following table compares the Flexible orchestration mode, Uniform orchestrat
 
 | Feature | Supported by Flexible orchestration for scale sets | Supported by Uniform orchestration for scale sets | Supported by Availability Sets |
 |---|---|---|---|
-| Availability SLA | 99.95% | 99.95 for FD>1 in Single Placement Group; 99.99% for instances spread across multiple zones | 99.95% |
+| Availability SLA | 99.95% for instances spread across fault domains; 99.99% for instances spread across multiple zones | 99.95% for FD>1 in Single Placement Group; 99.99% for instances spread across multiple zones | 99.95% |
 | Availability Zones | Specify instances land across 1, 2 or 3 availability zones | Specify instances land across 1, 2 or 3 availability zones | Not supported |
 | Assign VM to a Specific Availability Zone | Yes | No | No |
 | Fault Domain – Max Spreading (Azure will maximally spread instances) | Yes | Yes | No |
 | Fault Domain – Fixed Spreading | 2-3 FDs (depending on regional maximum FD Count); 1 for zonal deployments | 2, 3, 5 FDs; 1, 5 for zonal deployments | 2-3 FDs (depending on regional maximum FD Count) |
 | Assign VM to a Specific Fault Domain | Yes | No | No |
-| Update Domains | None (platform maintenance performed FD by FD) | 5 update domains | Up to 20 update domains |
+| Update Domains | Depreciated (platform maintenance performed FD by FD) | 5 update domains | Up to 20 update domains |
 | Maintenance Control | No | Yes | Yes |
 
 ### Networking 
 
 | Feature | Supported by Flexible orchestration for scale sets | Supported by Uniform orchestration for scale sets | Supported by Availability Sets |
 |---|---|---|---|
-| Default outbound connectivity | No, must have explicit outbound connectivity | Yes | Yes |
+| Default outbound connectivity | No, must have [explicit outbound connectivity](../virtual-network/ip-services/default-outbound-access.md) | Yes | Yes |
 | Azure Load Balancer Standard SKU | Yes | Yes | Yes |
 | Application Gateway | Yes | Yes | Yes |
 | Infiniband Networking | No | Yes, single placement group only | Yes |
@@ -160,7 +163,7 @@ The following table compares the Flexible orchestration mode, Uniform orchestrat
 | Azure Backup  | Yes | No | Yes |
 | Azure Site Recovery | Yes (via PowerShell) | No | Yes |
 | Azure Alerts  | Yes | Yes | Yes |
-| VM Insights  | No | Yes | Yes |
+| VM Insights  | Can be installed into individual VMs | Yes | Yes |
 
 
 ## Get started with Flexible orchestration mode
@@ -178,7 +181,7 @@ Register and get started with [Flexible orchestration mode](..\virtual-machines\
 
     | Availability attribute  | Flexible orchestration  | Uniform orchestration  | Availability Sets  |
     |-|-|-|-|
-    | Deploy across availability zones  | No  | Yes  | No  |
+    | Deploy across availability zones  | Yes  | Yes  | No  |
     | Fault domain availability guarantees within a region  | Yes, up to 1000 instances can be spread across up to 3 fault domains in the region. Maximum fault domain count varies by region  | Yes, up to 100 instances  | Yes, up to 200 instances  |
     | Placement groups  | Flexible mode always uses multiple placement groups (singlePlacementGroup = false)  | You can choose Single Placement Group or Multiple Placement Groups | N/A  |
     | Update domains  | None, maintenance or host updates are done fault domain by fault domain  | Up to 5 update domains  | Up to 20 update domains  |
@@ -189,33 +192,6 @@ Register and get started with [Flexible orchestration mode](..\virtual-machines\
     |-|-|-|-|
     | Maximum Instance Count (with FD availability guarantee)  | 1000  | 3000  | 200  |
 
-## Troubleshoot scale sets with Flexible orchestration
-Find the right solution to your troubleshooting scenario.
-
-
-```
-InvalidParameter. The specified fault domain count 2 must fall in the range 1 to 1.
-```
-
-**Cause:** The `platformFaultDomainCount` parameter is invalid for the region or zone selected.
-
-**Solution:** You must select a valid `platformFaultDomainCount` value. For zonal deployments, the maximum `platformFaultDomainCount` value is 1. For regional deployments where no zone is specified, the maximum `platformFaultDomainCount` varies depending on the region. See [Manage the availability of VMs for scripts](../virtual-machines/availability.md) to determine the maximum fault domain count per region.
-
-```
-OperationNotAllowed. Deletion of Virtual Machine Scale Set is not allowed as it contains one or more VMs. Please delete or detach the VM(s) before deleting the Virtual Machine Scale Set.
-```
-
-**Cause:** Trying to delete a scale set in Flexible orchestration mode that is associated with one or more virtual machines.
-
-**Solution:** Delete all of the virtual machines associated with the scale set in Flexible orchestration mode, then you can delete the scale set.
-
-```
-InvalidParameter. The value 'True' of parameter 'singlePlacementGroup' is not allowed. Allowed values are: False.
-```
-**Cause:** The `singlePlacementGroup` parameter is set to *True*.
-
-**Solution:** The `singlePlacementGroup` must be set to *False*.
-
 
 ## Next steps
 > [!div class="nextstepaction"]

articles/virtual-machines/availability.md

@@ -15,17 +15,22 @@ ms.reviewer: cynthn
 
 This article provides an overview of the availability options for Azure virtual machines (VMs).
 
-## Availability zones
 
+## Availability zones
 [Availability zones](../availability-zones/az-overview.md?context=/azure/virtual-machines/context/context) expands the level of control you have to maintain the availability of the applications and data on your VMs. An Availability Zone is a physically separate zone, within an Azure region. There are three Availability Zones per supported Azure region. 
 
 Each Availability Zone has a distinct power source, network, and cooling. By designing your solutions to use replicated VMs in zones, you can protect your apps and data from the loss of a data center. If one zone is compromised, then replicated apps and data are instantly available in another zone. 
 
+
 ## Virtual Machines Scale Sets 
+[Azure virtual machine scale sets](flexible-virtual-machine-scale-sets.md) let you create and manage a group of load balanced VMs. The number of VM instances can automatically increase or decrease in response to demand or a defined schedule. Scale sets provide high availability to your applications, and allow you to centrally manage, configure, and update many VMs. There is no cost for the scale set itself, you only pay for each VM instance that you create.
 
-[Azure virtual machine scale sets](flexible-virtual-machine-scale-sets.md) let you create and manage a group of load balanced VMs. The number of VM instances can automatically increase or decrease in response to demand or a defined schedule. Scale sets provide high availability to your applications, and allow you to centrally manage, configure, and update many VMs. We recommended that two or more VMs are created within a scale set to provide for a highly available application and to meet the [99.95% Azure SLA](https://azure.microsoft.com/support/legal/sla/virtual-machines/). There is no cost for the scale set itself, you only pay for each VM instance that you create.
+Virtual machines in a scale set can also be deployed into multiple availability zones, a single availability zone, or regionally. Availability zone deployment options may differ based on the [orchestration mode](../virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes.md?context=/azure/virtual-machines/context/context).
+
+
+## Availability sets
+An [availability set](availability-set-overview.md) is a logical grouping of VMs that allows Azure to understand how your application is built to provide for redundancy and availability. We recommended that two or more VMs are created within an availability set to provide for a highly available application and to meet the [99.95% Azure SLA](https://azure.microsoft.com/support/legal/sla/virtual-machines/). There is no cost for the Availability Set itself, you only pay for each VM instance that you create.
 
-Virtual machines in a scale set can also be deployed into a single Availability zone, or regionally. Availability zone deployment options may differ based on the [orchestration mode](../virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes.md?context=/azure/virtual-machines/context/context).
 
 ## Load balancer
 Combine the [Azure Load Balancer](../load-balancer/load-balancer-overview.md) with an availability zone or availability set to get the most application resiliency. The Azure Load Balancer distributes traffic between multiple virtual machines. For our Standard tier virtual machines, the Azure Load Balancer is included. Not all virtual machine tiers include the Azure Load Balancer. For more information about load balancing your virtual machines, see **Load Balancing virtual machines** for [Linux](linux/tutorial-load-balancer.md) or [Windows](windows/tutorial-load-balancer.md).
@@ -41,6 +46,7 @@ When deciding which redundancy option is best for your scenario, consider the tr
 
 For more information, see [Azure Storage redundancy](../storage/common/storage-redundancy.md)
 
+
 ## Azure Site Recovery
 As an organization you need to adopt a business continuity and disaster recovery (BCDR) strategy that keeps your data safe, and your apps and workloads online, when planned and unplanned outages occur.
 
@@ -50,9 +56,6 @@ Site Recovery can manage replication for:
 - Azure VMs replicating between Azure regions.
 - On-premises VMs, Azure Stack VMs, and physical servers.
 
-## Availability sets
-An [availability set](availability-set-overview.md) is a logical grouping of VMs that allows Azure to understand how your application is built to provide for redundancy and availability. We recommended that two or more VMs are created within an availability set to provide for a highly available application and to meet the [99.95% Azure SLA](https://azure.microsoft.com/support/legal/sla/virtual-machines/). There is no cost for the Availability Set itself, you only pay for each VM instance that you create.
-
 ## Next steps
 - [Create a virtual machine in an availability zone](./linux/create-cli-availability-zone.md)
 - [Create a virtual machine in an availability set](./linux/tutorial-availability-sets.md)

articles/virtual-machines/flexible-virtual-machine-scale-sets-cli.md

@@ -35,20 +35,11 @@ In the following example, we specify a virtual machine profile (VM type, network
 
 ```azurecli-interactive
 az vmss create
---resource-group $rg
 --name $vmssName
---single-placement-group false
---orchestration-mode flexible
---platform-fault-domain-count 1
+--resource-group $rg
 --image UbuntuLTS
---admin-username azureuser
 --instance-count 2
---vm-sku 'Standard_D2s_v3'
---network-api-version '2020-11-01'
---computer-name-prefix $computerNamePrefix
---vnet-name $vnetName
---subnet $subnetName
---public-ip-per-vm
+--orchestration-mode flexible
 ```
 
 ### Add a single VM to a scale set