Merge pull request #185643 from craftyhouse/micraft-sfmc-quickfixes

Update how-to-managed-cluster-availability-zones.md

Author: denrea

articles/service-fabric/how-to-managed-cluster-availability-zones.md

@@ -2,7 +2,7 @@
 title: Deploy a Service Fabric managed cluster across Availability Zones
 description: Learn how to deploy Service Fabric managed cluster across Availability Zones and how to configure in an ARM template.
 ms.topic: how-to
-ms.date: 5/10/2021
+ms.date: 1/20/2022
 ---
 # Deploy a Service Fabric managed cluster across availability zones
 Availability Zones in Azure are a high-availability offering that protects your applications and data from datacenter failures. An Availability Zone is a unique physical location equipped with independent power, cooling, and networking within an Azure region.
@@ -61,45 +61,6 @@ To enable a zone resilient Azure Service Fabric managed cluster, you must includ
 }
 ```
 
-## Migrate an existing non-zone resilient cluster to Zone Resilient (Preview) 
-Existing Service Fabric managed clusters which are not spanned across availability zones can now be migrated in-place to span availability zones. Supported scenarios include clusters created in regions that have three availability zones as well as clusters in regions where three availability zones are made available post-deployment.
-
->[!NOTE]
->Availability Zone spanning is only available on Standard SKU clusters and requires three availability zones in the region.
-
->[!NOTE]
->Migration to a zone resilient configuration can cause a brief loss of external connectivity through the load balancer, but will not effect cluster health. This occurs when a new Public IP needs to be created in order to make the networking resilient to Zone failures. Please plan the migration accordingly.
-
-The following steps are required to migrate a cluster to be zone resilient:
-
-* Use apiVersion 2021-11-01-preview or higher
-* Add a new primary node type to the cluster with zones parameter in the nodetype set to ["1", "2", "3"] as show below:
-```json
-{
-  "apiVersion": "2021-11-01-preview",
-  "type": "Microsoft.ServiceFabric/managedclusters/nodetypes",
-  "name": "[concat(parameters('clusterName'), '/', parameters('nodeTypeName'))]",
-  "location": "[resourcegroup().location]",
-  "dependsOn": [
-    "[concat('Microsoft.ServiceFabric/managedclusters/', parameters('clusterName'))]"
-  ],
-  "properties": {
-    ...
-    "isPrimary": true,
-    "zones": ["1", "2", "3"]
-    ...
-  }
-}
-```
-
-* A brief period of unreachability to the cluster can occur during the step above.
-* Add new secondary node type(s) with same zones parameter as required. Skip if you have no secondary node type.
-* Migrate existing services from the old node types to the new ones. [Recommended using placement properties](./service-fabric-cluster-resource-manager-cluster-description.md)
-* Remove the old node types from the cluster using [Portal or cmdlet](./how-to-managed-cluster-modify-node-type.md). Make sure to remove old node types from your template.
-* Set zonalResiliency: true in the cluster ARM template and do a deployment to mark cluster as zone resilient and ensure all new node type deployments span across availability zones.
-
-
-
 
 [sf-architecture]: ./media/service-fabric-cross-availability-zones/sf-cross-az-topology.png
 [sf-architecture]: ./media/service-fabric-cross-availability-zones/sf-cross-az-topology.png