Merge pull request #72366 from ThalathBhagya/master

updated content

Author: ktoliver

articles/backup/backup-azure-move-recovery-services-vault.md

@@ -6,7 +6,7 @@ author: sogup
 manager: vijayts
 ms.service: backup
 ms.topic: conceptual
-ms.date: 03/19/2019
+ms.date: 04/08/2019
 ms.author: sogup
 ---
 
@@ -17,7 +17,9 @@ This article explains how to move a Recovery Services vault configured for Azure
 > [!NOTE]
 > To move a Recovery Services vault and its associated resources to different resource group, you should first [register the source subscription](#register-the-source-subscription-to-move-your-recovery-services-vault).
 
-[!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]
+## Supported geos
+
+Resource move for Recovery Services vault is supported in Australia East, Australia South East, Canada Central, Canada East, South East Asia, East Asia, Central US, North Central US, East US, East US2, South central US, West Central US, West Central US2, West US, Central India, South India, Japan East, Japan West, Korea Central, Korea South, North Europe, West Europe, South Africa North, South Africa West, UK South, UK West, UAE Central and UAE North.
 
 ## Prerequisites for moving a vault
 
@@ -29,12 +31,12 @@ This article explains how to move a Recovery Services vault configured for Azure
 - Currently you can move one Recovery Services vault, per region, at a time.
 - If a VM doesn’t move with the Recovery Services vault across subscriptions, or to a new resource group, the current VM recovery points remain intact in the vault until they expire.
 - Whether the VM is moved with the vault or not, you can always restore the VM from the retained backup history in the vault.
--   The Azure Disk Encryption requires that your key vault and VMs reside in the same Azure region and subscription.
--   To move a virtual machine with managed disks, see this [article](https://azure.microsoft.com/blog/move-managed-disks-and-vms-now-available/).
--   The options for moving resources deployed through the Classic model differ depending on whether you are moving the resources within a subscription, or to a new subscription. For more information, see this [article](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-move-resources#classic-deployment-limitations).
--   Backup policies defined for the vault are retained after the vault moves across subscriptions or to a new resource group.
--   Currently, you cannot move vaults containing the Azure Files, Azure File Sync, or SQL in IaaS VMs across subscriptions and resource groups. Support for these scenarios will be added in future releases.
--   If you move a vault containing VM backup data, across subscriptions, you must move your VMs to the same subscription, and use the same target resource group to continue backups.<br>
+- The Azure Disk Encryption requires that your key vault and VMs reside in the same Azure region and subscription.
+- To move a virtual machine with managed disks, see this [article](https://azure.microsoft.com/blog/move-managed-disks-and-vms-now-available/).
+- The options for moving resources deployed through the Classic model differ depending on whether you are moving the resources within a subscription, or to a new subscription. For more information, see this [article](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-move-resources#classic-deployment-limitations).
+- Backup policies defined for the vault are retained after the vault moves across subscriptions or to a new resource group.
+- Currently, you cannot move vaults containing the Azure Files, Azure File Sync, or SQL in IaaS VMs across subscriptions and resource groups.
+- If you move a vault containing VM backup data, across subscriptions, you must move your VMs to the same subscription, and use the same target resource group to continue backups.<br>
 
 > [!NOTE]
 >
@@ -47,24 +49,24 @@ To register the source subscription to **Move** your Recovery Services vault, ru
 1. Sign in to your Azure account
 
    ```
-   Connect-AzAccount
+   Connect-AzureRmAccount
    ```
 
 2. Select the subscription that you want to register
 
    ```
-   Get-AzSubscription –SubscriptionName "Subscription Name" | Select-AzSubscription
+   Get-AzureRmSubscription –SubscriptionName "Subscription Name" | Select-AzureRmSubscription
    ```
 3. Register this subscription
 
    ```
-   Register-AzProviderFeature -ProviderNamespace Microsoft.RecoveryServices -FeatureName RecoveryServicesResourceMove
+   Register-AzureRmProviderFeature -ProviderNamespace Microsoft.RecoveryServices -FeatureName RecoveryServicesResourceMove
    ```
 
 4. Run the command
 
    ```
-   Register-AzResourceProvider -ProviderNamespace Microsoft.RecoveryServices
+   Register-AzureRmResourceProvider -ProviderNamespace Microsoft.RecoveryServices
    ```
 
 Wait for 30 minutes for the subscription to be whitelisted before you start with the move operation using the Azure portal or PowerShell.
@@ -134,18 +136,18 @@ You can move a Recovery Services vault and its associated resources to a differe
 
 ## Use PowerShell to move a vault
 
-To move a Recovery Services vault to another resource group, use the `Move-AzResource` cmdlet. `Move-AzResource` requires the resource name and type of resource. You can get both from the `Get-AzRecoveryServicesVault` cmdlet.
+To move a Recovery Services vault to another resource group, use the `Move-AzureRMResource` cmdlet. `Move-AzureRMResource` requires the resource name and type of resource. You can get both from the `Get-AzureRmRecoveryServicesVault` cmdlet.
 
 ```
 $destinationRG = "<destinationResourceGroupName>"
-$vault = Get-AzRecoveryServicesVault -Name <vaultname> -ResourceGroupName <vaultRGname>
-Move-AzResource -DestinationResourceGroupName $destinationRG -ResourceId $vault.ID
+$vault = Get-AzureRmRecoveryServicesVault -Name <vaultname> -ResourceGroupName <vaultRGname>
+Move-AzureRmResource -DestinationResourceGroupName $destinationRG -ResourceId $vault.ID
 ```
 
 To move the resources to different subscription, include the `-DestinationSubscriptionId` parameter.
 
 ```
-Move-AzResource -DestinationSubscriptionId "<destinationSubscriptionID>" -DestinationResourceGroupName $destinationRG -ResourceId $vault.ID
+Move-AzureRmResource -DestinationSubscriptionId "<destinationSubscriptionID>" -DestinationResourceGroupName $destinationRG -ResourceId $vault.ID
 ```
 
 After executing the above cmdlets, you will be asked to confirm that you want to move the specified resources. Type **Y** to confirm. After a successful validation, the resource moves.

articles/backup/backup-azure-vms-encryption.md

@@ -1,6 +1,6 @@
 ---
 title: Back up and restore encrypted Azure VMs with Azure Backup
-description: Describes how to back up and restore encrypted Azure VMs with the Azure Backup service. 
+description: Describes how to back up and restore encrypted Azure VMs with the Azure Backup service.
 services: backup
 author: geetha
 manager: vijayts
@@ -25,7 +25,7 @@ Azure Backup supports backup of Azure VMs that have their OS/data disks encrypte
 Azure Backup can back up and restore Azure VMs using ADE with and without the Azure AD app, as summarized in the following table.
 
 **VM disk type** | **ADE (BEK/dm-crypt)** | **ADE and KEK**
---- | --- | --- 
+--- | --- | ---
 **Unmanaged** | Yes | Yes
 **Managed**  | Yes | Yes
 
@@ -89,14 +89,14 @@ In addition, there are a couple of things that you might need to do in some circ
 8. If you're using Azure Key Vault, on the vault page, you see a message that Azure Backup needs read-only access to the keys and secrets in the Key Vault.
 
     - If you receive this message, no action is required.
-    
+
         ![Access OK](./media/backup-azure-vms-encryption/access-ok.png)
-        
+
     - If you receive this message, you need to set permissions as described in the [procedure below](#provide-permissions).
-    
+
         ![Access warning](./media/backup-azure-vms-encryption/access-warning.png)
 
-9. Click **Enable Backup** to deploy the backup policy in the vault, and enable backup for the selected VMs. 
+9. Click **Enable Backup** to deploy the backup policy in the vault, and enable backup for the selected VMs.
 
 
 ## Trigger a backup job
@@ -123,18 +123,18 @@ To set permissions:
 1. In the Azure portal, select **All services**, and search for **Key vaults**.
 2. Select the key vault associated with the encrypted VM you're backing up.
 3. Select **Access policies** > **Add new**.
-4. Select **Select principal**, and then type **Backup Management**. 
+4. Select **Select principal**, and then type **Backup Management**.
 5. Select **Backup Management Service** > **Select**.
 
     ![Backup service selection](./media/backup-azure-vms-encryption/select-backup-service.png)
 
 6. In **Add access policy** > **Configure from template (optional)**, select **Azure Backup**.
     - The required permissions are prefilled for **Key permissions** and **Secret permissions**.
-    - If your VM is encrypted using **BEK only**, remove the selection for **Key permissions** since you only need permissions for secrets. 
+    - If your VM is encrypted using **BEK only**, remove the selection for **Key permissions** since you only need permissions for secrets.
 
     ![Azure backup selection](./media/backup-azure-vms-encryption/select-backup-template.png)
 
-6. Click **OK**. **Backup Management Service** is added to **Access policies**. 
+6. Click **OK**. **Backup Management Service** is added to **Access policies**.
 
     ![Access policies](./media/backup-azure-vms-encryption/backup-service-access-policy.png)
 
@@ -153,6 +153,5 @@ You restore encrypted VMs as follows:
 
 If you run into any issues, review
 
-- [Common errors](backup-azure-vms-troubleshoot.md#troubleshoot-backup-of-encrypted-vms) when backing up and restoring encrypted Azure VMs.
-- [General](backup-azure-vms-troubleshoot.md) Azure VM issues.
+- [Common errors](backup-azure-vms-troubleshoot.md) when backing up and restoring encrypted Azure VMs.
 - [Azure VM agent/backup extension](backup-azure-troubleshoot-vm-backup-fails-snapshot-timeout.md) issues.