Merge pull request #106037 from erikadoyle/sf-fixes

Service Fabric content updates and fixes

Author: American-Dipper

articles/service-fabric/media/service-fabric-cluster-creation-setup-aad/web-application-reply-url.png

@@ -72,7 +72,6 @@ Ephemeral OS disks is not a specific Service Fabric feature, but rather a featur
         "virtualMachineProfile": {
             "storageProfile": {
                 "osDisk": {
-                        "vhdContainers": ["[concat(reference(concat('Microsoft.Storage/storageAccounts/', parameters('vmStorageAccountName')), variables('storageApiVersion')).primaryEndpoints.blob, parameters('vmStorageAccountContainerName'))]"],
                         "caching": "ReadOnly",
                         "createOption": "FromImage",
                         "diffDiskSettings": {

articles/service-fabric/service-fabric-cluster-azure-deployment-preparation.md

@@ -100,7 +100,7 @@ When you try to sign in to Azure AD in Service Fabric Explorer, the page returns
 The cluster (web) application that represents Service Fabric Explorer attempts to authenticate against Azure AD, and as part of the request it provides the redirect return URL. But the URL is not listed in the Azure AD application **REPLY URL** list.
 
 #### Solution
-On the Azure AD page, select **App registrations**, select your cluster application, and then select **Reply URLs**. In the **Reply URLs** pane, add the Service Fabric Explorer URL to the list, or replace one of the items in the list. Save your change.
+On the Azure AD app registration page for your cluster, select **Authentication**, and under the **Redirect URIs** section, add the Service Fabric Explorer URL to the list. Save your change.
 
 ![Web application reply URL][web-application-reply-url]
 

articles/service-fabric/service-fabric-cluster-creation-setup-aad.md

@@ -8,7 +8,9 @@ ms.custom: sfrev
 ---
 # Azure Service Fabric node types and virtual machine scale sets
 
-[Virtual machine scale sets](/azure/virtual-machine-scale-sets) are an Azure compute resource. You can use scale sets to deploy and manage a collection of virtual machines as a set. Each node type that you define in an Azure Service Fabric cluster sets up a separate scale. The Service Fabric runtime is installed on each virtual machine in the scale set by the *Microsoft.Azure.ServiceFabric* Virtual Machine extension. You can independently scale each node type up or down, change the OS SKU running on each cluster node, have different sets of ports open, and use different capacity metrics.
+[Virtual machine scale sets](/azure/virtual-machine-scale-sets) are an Azure compute resource. You can use scale sets to deploy and manage a collection of virtual machines as a set. Each node type that you define in an Azure Service Fabric cluster sets up exactly one scale set: multiple node types cannot be backed by the same scale set and one node type should not (in most cases) be backed by multiple scale sets. An exception to this is in the rare situation of [vertical scaling](service-fabric-best-practices-capacity-scaling.md#vertical-scaling-considerations) a node type, when you temporarily have two scale sets with the same `nodeTypeRef` value while replicas are migrated from the original to the upgraded scale set.
+
+The Service Fabric runtime is installed on each virtual machine in the scale set by the *Microsoft.Azure.ServiceFabric* Virtual Machine extension. You can independently scale each node type up or down, change the OS SKU running on each cluster node, have different sets of ports open, and use different capacity metrics.
 
 The following figure shows a cluster that has two node types, named *FrontEnd* and *BackEnd*. Each node type has five nodes.