Merge pull request #207633 from roygara/unMEL

Terminology change

Author: GitHubber17

articles/virtual-machines/linux/convert-unmanaged-to-managed-disks.md

@@ -1,6 +1,6 @@
 ---
-title: Convert a Linux VM from unmanaged disks to managed disks
-description: How to convert a Linux VM from unmanaged disks to managed disks by using Azure CLI.
+title: Migrate a Linux VM from unmanaged disks to managed disks
+description: How to Migrate a Linux VM from unmanaged disks to managed disks by using Azure CLI.
 author: roygara
 ms.service: storage
 ms.collection: linux
@@ -10,47 +10,47 @@ ms.author: rogarana
 ms.subservice: disks
 ---
 
-# Convert a Linux virtual machine from unmanaged disks to managed disks
+# Migrate a Linux virtual machine from unmanaged disks to managed disks
 
 **Applies to:** :heavy_check_mark: Linux VMs 
 
-If you have existing Linux virtual machines (VMs) that use unmanaged disks, you can convert the VMs to use [Azure Managed Disks](../managed-disks-overview.md). This process converts both the OS disk and any attached data disks.
+If you have existing Linux virtual machines (VMs) that use unmanaged disks, you can migrate the VMs to use [Azure Managed Disks](../managed-disks-overview.md). This process converts both the OS disk and any attached data disks.
 
-This article shows you how to convert VMs by using the Azure CLI. If you need to install or upgrade it, see [Install Azure CLI](/cli/azure/install-azure-cli). 
+This article shows you how to migrate VMs by using the Azure CLI. If you need to install or upgrade it, see [Install Azure CLI](/cli/azure/install-azure-cli). 
 
 ## Before you begin
 * Review [the FAQ about migration to Managed Disks](../faq-for-disks.yml).
 
 [!INCLUDE [virtual-machines-common-convert-disks-considerations](../../../includes/virtual-machines-common-convert-disks-considerations.md)]
 
-* The original VHDs and the storage account used by the VM before conversion are not deleted. They continue to incur charges. To avoid being billed for these artifacts, delete the original VHD blobs after you verify that the conversion is complete. If you need to find these unattached disks in order to delete them, see our article [Find and delete unattached Azure managed and unmanaged disks](find-unattached-disks.md).
+* The original VHDs and the storage account used by the VM before migration are not deleted. They continue to incur charges. To avoid being billed for these artifacts, delete the original VHD blobs after you verify that the migration is complete. If you need to find these unattached disks in order to delete them, see our article [Find and delete unattached Azure managed and unmanaged disks](find-unattached-disks.md).
 
-## Convert single-instance VMs
-This section covers how to convert single-instance Azure VMs from unmanaged disks to managed disks. (If your VMs are in an availability set, see the next section.) You can use this process to convert the VMs from premium (SSD) unmanaged disks to premium managed disks, or from standard (HDD) unmanaged disks to standard managed disks.
+## Migrate single-instance VMs
+This section covers how to migrate single-instance Azure VMs from unmanaged disks to managed disks. (If your VMs are in an availability set, see the next section.) You can use this process to migrate the VMs from premium (SSD) unmanaged disks to premium managed disks, or from standard (HDD) unmanaged disks to standard managed disks.
 
 1. Deallocate the VM by using [az vm deallocate](/cli/azure/vm). The following example deallocates the VM named `myVM` in the resource group named `myResourceGroup`:
 
     ```azurecli
     az vm deallocate --resource-group myResourceGroup --name myVM
     ```
 
-2. Convert the VM to managed disks by using [az vm convert](/cli/azure/vm). The following process converts the VM named `myVM`, including the OS disk and any data disks:
+2. Migrate the VM to managed disks by using [az vm convert](/cli/azure/vm). The following process converts the VM named `myVM`, including the OS disk and any data disks:
 
     ```azurecli
     az vm convert --resource-group myResourceGroup --name myVM
     ```
 
-3. Start the VM after the conversion to managed disks by using [az vm start](/cli/azure/vm). The following example starts the VM named `myVM` in the resource group named `myResourceGroup`.
+3. Start the VM after the migration to managed disks by using [az vm start](/cli/azure/vm). The following example starts the VM named `myVM` in the resource group named `myResourceGroup`.
 
     ```azurecli
     az vm start --resource-group myResourceGroup --name myVM
     ```
 
-## Convert VMs in an availability set
+## Migrate VMs in an availability set
 
-If the VMs that you want to convert to managed disks are in an availability set, you first need to convert the availability set to a managed availability set.
+If the VMs that you want to migrate to managed disks are in an availability set, you first need to migrate the availability set to a managed availability set.
 
-All VMs in the availability set must be deallocated before you convert the availability set. Plan to convert all VMs to managed disks after the availability set itself has been converted to a managed availability set. Then, start all the VMs and continue operating as normal.
+All VMs in the availability set must be deallocated before you migrate the availability set. Plan to migrate all VMs to managed disks after the availability set itself has been converted to a managed availability set. Then, start all the VMs and continue operating as normal.
 
 1. List all VMs in an availability set by using [az vm availability-set list](/cli/azure/vm/availability-set). The following example lists all VMs in the availability set named `myAvailabilitySet` in the resource group named `myResourceGroup`:
 
@@ -68,35 +68,35 @@ All VMs in the availability set must be deallocated before you convert the avail
     az vm deallocate --resource-group myResourceGroup --name myVM
     ```
 
-3. Convert the availability set by using [az vm availability-set convert](/cli/azure/vm/availability-set). The following example converts the availability set named `myAvailabilitySet` in the resource group named `myResourceGroup`:
+3. Migrate the availability set by using [az vm availability-set convert](/cli/azure/vm/availability-set). The following example converts the availability set named `myAvailabilitySet` in the resource group named `myResourceGroup`:
 
     ```azurecli
     az vm availability-set convert \
         --resource-group myResourceGroup \
         --name myAvailabilitySet
     ```
 
-4. Convert all the VMs to managed disks by using [az vm convert](/cli/azure/vm). The following process converts the VM named `myVM`, including the OS disk and any data disks:
+4. Migrate all the VMs to managed disks by using [az vm convert](/cli/azure/vm). The following process converts the VM named `myVM`, including the OS disk and any data disks:
 
     ```azurecli
     az vm convert --resource-group myResourceGroup --name myVM
     ```
 
-5. Start all the VMs after the conversion to managed disks by using [az vm start](/cli/azure/vm). The following example starts the VM named `myVM` in the resource group named `myResourceGroup`:
+5. Start all the VMs after the migration to managed disks by using [az vm start](/cli/azure/vm). The following example starts the VM named `myVM` in the resource group named `myResourceGroup`:
 
     ```azurecli
     az vm start --resource-group myResourceGroup --name myVM
     ```
 
-## Convert using the Azure portal
+## Migrate using the Azure portal
 
-You can also convert unmanaged disks to managed disks using the Azure portal.
+You can also migrate unmanaged disks to managed disks using the Azure portal.
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
-2. Select the VM from the list of VMs in the portal.
-3. In the blade for the VM, select **Disks** from the menu.
-4. At the top of the **Disks** blade, select **Migrate to managed disks**.
-5. If your VM is in an availability set, there will be a warning on the **Migrate to managed disks** blade that you need to convert the availability set first. The warning should have a link you can click to convert the availability set. Once the availability set is converted or if your VM is not in an availability set, click **Migrate** to start the process of migrating your disks to managed disks.
+1. Select the VM from the list of VMs in the portal.
+1. In the blade for the VM, select **Disks** from the menu.
+1. At the top of the **Disks** blade, select **Migrate to managed disks**.
+1. If your VM is in an availability set, there will be a warning on the **Migrate to managed disks** blade that you need to migrate the availability set first. The warning should have a link you can click to migrate the availability set. Once the availability set is converted or if your VM is not in an availability set, click **Migrate** to start the process of migrating your disks to managed disks.
 
 The VM will be stopped and restarted after migration is complete.
 

articles/virtual-machines/windows/convert-unmanaged-to-managed-disks.md

@@ -1,6 +1,6 @@
 ---
-title: Convert a Windows virtual machine from unmanaged disks to managed disks
-description: How to convert a Windows VM from unmanaged disks to managed disks by using PowerShell in the Resource Manager deployment model
+title: Migrate a Windows virtual machine from unmanaged disks to managed disks
+description: How to migrate a Windows VM from unmanaged disks to managed disks by using PowerShell in the Resource Manager deployment model
 author: roygara
 ms.service: storage
 ms.subservice: disks
@@ -9,11 +9,11 @@ ms.date: 07/12/2018
 ms.author: rogarana
 ---
 
-# Convert a Windows virtual machine from unmanaged disks to managed disks
+# Migrate a Windows virtual machine from unmanaged disks to managed disks
 
 **Applies to:** :heavy_check_mark: Windows VMs 
 
-If you have existing Windows virtual machines (VMs) that use unmanaged disks, you can convert the VMs to use managed disks through the [Azure Managed Disks](../managed-disks-overview.md) service. This process converts both the operating system (OS) disk and any attached data disks.
+If you have existing Windows virtual machines (VMs) that use unmanaged disks, you can migrate the VMs to use managed disks through the [Azure Managed Disks](../managed-disks-overview.md) service. This process converts both the operating system (OS) disk and any attached data disks.
 
 
 ## Before you begin
@@ -25,11 +25,11 @@ If you have existing Windows virtual machines (VMs) that use unmanaged disks, yo
 
 [!INCLUDE [virtual-machines-common-convert-disks-considerations](../../../includes/virtual-machines-common-convert-disks-considerations.md)]
 
-* The original VHDs and the storage account used by the VM before conversion are not deleted. They continue to incur charges. To avoid being billed for these artifacts, delete the original VHD blobs after you verify that the conversion is complete. If you need to find these unattached disks in order to delete them, see our article [Find and delete unattached Azure managed and unmanaged disks](find-unattached-disks.md).
+* The original VHDs and the storage account used by the VM before migration are not deleted. They continue to incur charges. To avoid being billed for these artifacts, delete the original VHD blobs after you verify that the migration is complete. If you need to find these unattached disks in order to delete them, see our article [Find and delete unattached Azure managed and unmanaged disks](find-unattached-disks.md).
 
 
-## Convert single-instance VMs
-This section covers how to convert single-instance Azure VMs from unmanaged disks to managed disks. (If your VMs are in an availability set, see the next section.) 
+## Migrate single-instance VMs
+This section covers how to migrate single-instance Azure VMs from unmanaged disks to managed disks. (If your VMs are in an availability set, see the next section.) 
 
 1. Deallocate the VM by using the [Stop-AzVM](/powershell/module/az.compute/stop-azvm) cmdlet. The following example deallocates the VM named `myVM` in the resource group named `myResourceGroup`: 
 
@@ -39,19 +39,19 @@ This section covers how to convert single-instance Azure VMs from unmanaged disk
    Stop-AzVM -ResourceGroupName $rgName -Name $vmName -Force
    ```
 
-2. Convert the VM to managed disks by using the [ConvertTo-AzVMManagedDisk](/powershell/module/az.compute/convertto-azvmmanageddisk) cmdlet. The following process converts the previous VM, including the OS disk and any data disks, and starts the Virtual Machine:
+2. Migrate the VM to managed disks by using the [ConvertTo-AzVMManagedDisk](/powershell/module/az.compute/convertto-azvmmanageddisk) cmdlet. The following process converts the previous VM, including the OS disk and any data disks, and starts the Virtual Machine:
 
    ```azurepowershell-interactive
    ConvertTo-AzVMManagedDisk -ResourceGroupName $rgName -VMName $vmName
    ```
 
 
 
-## Convert VMs in an availability set
+## Migrate VMs in an availability set
 
-If the VMs that you want to convert to managed disks are in an availability set, you first need to convert the availability set to a managed availability set.
+If the VMs that you want to migrate to managed disks are in an availability set, you first need to migrate the availability set to a managed availability set.
 
-1. Convert the availability set by using the [Update-AzAvailabilitySet](/powershell/module/az.compute/update-azavailabilityset) cmdlet. The following example updates the availability set named `myAvailabilitySet` in the resource group named `myResourceGroup`:
+1. Migrate the availability set by using the [Update-AzAvailabilitySet](/powershell/module/az.compute/update-azavailabilityset) cmdlet. The following example updates the availability set named `myAvailabilitySet` in the resource group named `myResourceGroup`:
 
    ```azurepowershell-interactive
    $rgName = 'myResourceGroup'
@@ -68,7 +68,7 @@ If the VMs that you want to convert to managed disks are in an availability set,
    Update-AzAvailabilitySet -AvailabilitySet $avSet -Sku Aligned
    ```
 
-2. Deallocate and convert the VMs in the availability set. The following script deallocates each VM by using the [Stop-AzVM](/powershell/module/az.compute/stop-azvm) cmdlet, converts it by using [ConvertTo-AzVMManagedDisk](/powershell/module/az.compute/convertto-azvmmanageddisk), and restarts it automatically as apart of the conversion process:
+2. Deallocate and migrate the VMs in the availability set. The following script deallocates each VM by using the [Stop-AzVM](/powershell/module/az.compute/stop-azvm) cmdlet, converts it by using [ConvertTo-AzVMManagedDisk](/powershell/module/az.compute/convertto-azvmmanageddisk), and restarts it automatically as apart of the migration process:
 
    ```azurepowershell-interactive
    $avSet = Get-AzAvailabilitySet -ResourceGroupName $rgName -Name $avSetName
@@ -84,21 +84,21 @@ If the VMs that you want to convert to managed disks are in an availability set,
 
 ## Troubleshooting
 
-- Before converting, make sure all the VM extensions are in the 'Provisioning succeeded' state or the conversion will fail with the error code 409.
-- If there is an error during conversion, or if a VM is in a failed state because of issues in a previous conversion, run the `ConvertTo-AzVMManagedDisk` cmdlet again. A simple retry usually unblocks the situation.
-- If you are converting a Linux VM to managed disks, use the latest version of the Azure Linux Agent. Operations using Azure Linux Agent versions '2.2.0' and earlier will likely fail. Running the conversion on a generalized VM or a VM that belongs to a classic availability set is also not supported.
-- If the conversion fails with the "SnapshotCountExceeded" error, delete some snapshots and attempt the operation again.
+- Before converting, make sure all the VM extensions are in the 'Provisioning succeeded' state or the migration will fail with the error code 409.
+- If there is an error during migration, or if a VM is in a failed state because of issues in a previous migration, run the `ConvertTo-AzVMManagedDisk` cmdlet again. A simple retry usually unblocks the situation.
+- If you are converting a Linux VM to managed disks, use the latest version of the Azure Linux Agent. Operations using Azure Linux Agent versions '2.2.0' and earlier will likely fail. Running the migration on a generalized VM or a VM that belongs to a classic availability set is also not supported.
+- If the migration fails with the "SnapshotCountExceeded" error, delete some snapshots and attempt the operation again.
 
 
-## Convert using the Azure portal
+## Migrate using the Azure portal
 
-You can also convert unmanaged disks to managed disks using the Azure portal.
+You can also migrate unmanaged disks to managed disks using the Azure portal.
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 2. Select the VM from the list of VMs in the portal.
 3. In the blade for the VM, select **Disks** from the menu.
 4. At the top of the **Disks** blade, select **Migrate to managed disks**.
-5. If your VM is in an availability set, there will be a warning on the **Migrate to managed disks** blade that you need to convert the availability set first. The warning should have a link you can click to convert the availability set. Once the availability set is converted or if your VM is not in an availability set, click **Migrate** to start the process of migrating your disks to managed disks.
+5. If your VM is in an availability set, there will be a warning on the **Migrate to managed disks** blade that you need to migrate the availability set first. The warning should have a link you can click to migrate the availability set. Once the availability set is converted or if your VM is not in an availability set, click **Migrate** to start the process of migrating your disks to managed disks.
 
 The VM will be stopped and restarted after migration is complete.