Merge pull request #110759 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to master to sync with https://github.com/Microsoft/azure-docs (branch master)

Author: huypub

articles/openshift/howto-using-azure-redhat-openshift.md

@@ -13,7 +13,7 @@ keywords: aro, openshift, az aro, red hat, cli
 # Create, access, and manage an Azure Red Hat OpenShift 4.3 Cluster
 
 > [!IMPORTANT]
-> Please note that Azure Red Hat OpenShift 4.3 is currently only available in private preview in East US. Private preview acceptance is by invitation only. Please be sure to register your subscription before attempting to enable this feature: [Azure Red Hat OpenShift Private Preview Registration](https://aka.ms/aro-preview-register)
+> Please note that Azure Red Hat OpenShift 4.3 is currently only available in private preview in East US and East US 2. Private preview acceptance is by invitation only. Please be sure to register your subscription before attempting to enable this feature: [Azure Red Hat OpenShift Private Preview Registration](https://aka.ms/aro-preview-register)
 
 > [!NOTE]
 > Preview features are self-service and are provided as is and as available and are excluded from the service-level agreement (SLA) and limited warranty. Therefore, the features aren't meant for production use.
@@ -61,7 +61,7 @@ The `az aro` extension allows you to create, access, and delete Azure Red Hat Op
    az -v
    ...
    Extensions:
-   aro                                0.1.0
+   aro                                0.3.0
    ...
    ```
 
@@ -104,7 +104,7 @@ Follow these steps to create a virtual network containing two empty subnets.
 4. Add two empty subnets to your virtual network.
 
    ```console
-    for subnet in "$CLUSTER-master" "$CLUSTER-worker"; do
+   for subnet in "$CLUSTER-master" "$CLUSTER-worker"; do
      az network vnet subnet create \
        -g "$RESOURCEGROUP" \
        --vnet-name vnet \
@@ -137,6 +137,8 @@ az aro create \
   --vnet vnet \
   --master-subnet "$CLUSTER-master" \
   --worker-subnet "$CLUSTER-worker" \
+  --cluster-resource-group "aro-$CLUSTER" \
+  --domain "$CLUSTER" \
   --pull-secret "$PULL_SECRET"
 ```
 

articles/service-fabric/service-fabric-scale-up-node-type.md

@@ -29,7 +29,7 @@ Here is the process for updating the VM size and operating system of the primary
     To find the new scale set in the template, search for the "Microsoft.Compute/virtualMachineScaleSets" resource named by the *vmNodeType2Name* parameter.  The new scale set is added to the primary node type using the properties->virtualMachineProfile->extensionProfile->extensions->properties->settings->nodeTypeRef setting.
 4. Check the cluster health and verify all the nodes are healthy.
 5. Disable the nodes in the old scale set of the primary node type with the intent to remove node. You can disable all at once and the operations are queued. Wait until all nodes are disabled, which may take some time.  As the older nodes in the node type are disabled, the system services and seed nodes migrate to the VMs of the new scale set in the primary node type.
-6. Remove the older scale set from the primary node type.
+6. Remove the older scale set from the primary node type. (After the nodes are disabled as in step 5, in the virtual machine scale set blade in the Azure portal, deallocate the nodes from the old node type one by one.)
 7. Remove the load balancer associated with the old scale set. The cluster is unavailable while the new public IP address and load balancer are configured for the new scale set.  
 8. Store DNS settings of the public IP address associated with the old primary node type scale set in a variable and remove that public IP address.
 9. Replace the DNS settings of the public IP address associated with the new primary node type scale set with the DNS settings of the deleted public IP address.  The cluster is now reachable again.

includes/functions-supported-languages.md

@@ -18,7 +18,7 @@ ms.custom: include file
 |[F#](../articles/azure-functions/functions-reference-fsharp.md)|GA (.NET Framework 4.7)|GA (.NET Core 2.2)| GA (.NET Core 3.1) |
 |[Java](../articles/azure-functions/functions-reference-java.md)|N/A|GA (Java 8)| GA (Java 8)|
 |[PowerShell](../articles/azure-functions/functions-reference-powershell.md) |N/A|GA (PowerShell Core 6)| GA (PowerShell Core 6)|
-|[Python](../articles/azure-functions/functions-reference-python.md)#python-version|N/A|GA (Python 3.6 & 3.7)| GA (Python 3.6, 3.7, & 3.8)|
+|[Python](../articles/azure-functions/functions-reference-python.md#python-version)|N/A|GA (Python 3.6 & 3.7)| GA (Python 3.6, 3.7, & 3.8)|
 |[TypeScript](../articles/azure-functions/functions-reference-node.md#typescript) |N/A|GA<sup>1</sup>| GA<sup>1</sup> |