Merge pull request #181921 from laurabren/migrate-managed-data-disks

edit pass

Author: ShawnJackson

articles/service-fabric/service-fabric-managed-disk.md

@@ -1,6 +1,6 @@
 ---
-title: Deploy Service Fabric node-types Managed Data disks
-description: Learn how to create and deploy Service fabric node-types with attached Managed data disks
+title: Deploy Service Fabric node types with managed data disks
+description: Learn how to create and deploy Service Fabric node types with attached managed data disks.
 author: craftyhouse
 
 ms.topic: conceptual
@@ -9,29 +9,34 @@ ms.author: micraft
 
 ---
 
-# Deploy an Azure Service Fabric cluster node-type with Managed data disks(Preview)
+# Deploy an Azure Service Fabric cluster node type with managed data disks (preview)
 
 >[!NOTE]
-> Support for Managed Data disks is only in Preview right now, and should not be used with Production workloads.
+> Support for managed data disks is only in preview right now and should not be used with production workloads.
 
 
-Service Fabric node types by default use the temporary disk on each VM in the underlying virtual machine scale set for data storage. However, since the temporary disk is not persistent, and the size of the temporary disk is bound to a given VM SKU, that can be too restrictive for some scenarios. With Azure Managed Disks customers have a persistent data disk they can specify the size and performance on that will be used for a node-type, separately from a VM SKU. The following document provides steps to use native support from Service fabric to configure and use Azure Managed Disks as the default data path. Service Fabric will automatically configure Azure Managed Disks on node type creation and handle situations where VMs or the virtual machine scale set is reimaged.
+Azure Service Fabric node types, by default, use the temporary disk on each virtual machine (VM) in the underlying virtual machine scale set for data storage. However, because the temporary disk is not persistent, and the size of the temporary disk is bound to a given VM SKU, this can be too restrictive for some scenarios. 
 
-* Required minimum disk size for the managed data disk is 50 GB.
-* In scenarios where more than one managed data disk is attached, customer needs to manage the data disks on their own.
+This article provides the steps for how to use native support from Service Fabric to configure and use managed data disks as the default data path. Service Fabric will automatically configure managed data disks at node type creation and handle situations where VMs or the virtual machine scale set is reimaged.
 
-## Configuring virtual machine scale set to use managed data disks in Service fabric
-To use Azure Managed Disks on a node type, configure the underlying virtual machine scale set resource with the following:
+## Prerequisites
+
+* The required minimum disk size for the managed data disk is 50 GB.
+* In scenarios where more than one managed data disk is attached, the customer needs to manage the data disks themselves.
+
+## Configure the virtual machine scale set to use managed data disks in Service Fabric
+To use managed data disks on a node type, configure the underlying virtual machine scale set resource with the following:
 
 * Add a managed disk in data disks section of the template for the virtual machine scale set. 
-* Update the Service fabric extension with following settings: 
-    * For Windows - **useManagedDataDisk: true** and **dataPath: 'K:\\\\SvcFab'** .  Note, the drive letter "K" is just a representation, it can be any drive Letter lexicographically greater than all the drive letter present in the virtual machine scale set SKU.
-    * For Linux - **useManagedDataDisk:true** and **dataPath: '\mnt\sfdataroot'** .
+* Update the Service Fabric extension with following settings: 
+    * For Windows: **useManagedDataDisk: true** and **dataPath: 'K:\\\\SvcFab'**. Note that drive K is just a representation. You can use any drive letter lexicographically greater than all the drive letters present in the virtual machine scale set SKU.
+    * For Linux: **useManagedDataDisk:true** and **dataPath: '\mnt\sfdataroot'**.
 
 >[!NOTE]
-> Support for Managed Data disks for Linux Service Fabric clusters is currently not available.
+> Support for managed data disks for Linux Service Fabric clusters is currently not available.
+
+Here's an Azure Resource Manager template for a Service Fabric extension:
 
-Service Fabric Extension Azure Resource Manager template
 ```json
 {
     "virtualMachineProfile": {
@@ -77,12 +82,21 @@ Service Fabric Extension Azure Resource Manager template
 }
 ```
 
-## Migrate to using Managed data disks for Service fabric node types
-* For all migration scenarios, a new node type needs to be added which uses managed data disks as specified above.
-* Once new node types are added, migrate the workloads to the new node types.
-* Once the resources have finished deploying, you can begin to disable the nodes in the node type that you want to remove from the original cluster.
+## Migrate to using managed data disks for Service Fabric node types
+
+For all migration scenarios:
+
+1. Add a new node type that's configured to use managed data disks as specified earlier.
+
+1. Migrate any required workloads to the new node type.
+
+1. Disable and remove the old node type from the cluster.
+
+
+
+
 
 ## Next steps 
-* [Service Fabric Overview](service-fabric-reliable-services-introduction.md)
+* [Service Fabric overview](service-fabric-reliable-services-introduction.md)
 * [Node types and virtual machine scale sets](service-fabric-cluster-nodetypes.md)
 * [Service Fabric capacity planning](service-fabric-best-practices-capacity-scaling.md)