Merge pull request #49848 from mrkarMSFT/patch-1

Update service-fabric-scale-up-node-type.md

Author: ktoliver

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.