Incubation <50 visitors - VM restore using REST

Author: AbhishekMallick01

articles/backup/backup-azure-arm-userestapi-restoreazurevms.md

@@ -3,17 +3,19 @@ title: Restore Azure VMs using REST API
 description: In this article, learn how to manage to restore operations of Azure Virtual Machine Backup using REST API.
 ms.topic: how-to
 ms.service: azure-backup
-ms.date: 04/24/2024
+ms.date: 01/30/2025
 ms.assetid: b8487516-7ac5-4435-9680-674d9ecf5642
 author: jyothisuri
 ms.author: jsuri
 ---
 
 # Restore Azure Virtual machines using REST API
 
-Once the backup of an Azure virtual machine using Azure Backup is completed, one can restore entire Azure Virtual machines or disks or files from the same backup copy. This article describes how to restore an Azure VM or disks using REST API.
+This article describes how to restore an Azure VM or disks using the REST API.
 
-For any restore operation, one has to identify the relevant recovery point first.
+## Prerequisites
+
+After completing an Azure VM backup with Azure Backup, you can restore entire VMs, disks, or files from the same backup copy. For any restore operation, you have to first identify the relevant recovery point.
 
 ## Select Recovery point
 
@@ -111,7 +113,7 @@ X-Powered-By: ASP.NET
 ......
 ```
 
-The recovery point is identified with the `{name}` field in the above response.
+The recovery point is identified with the `{name}` field in the given response.
 
 ## Restore operations
 
@@ -122,15 +124,15 @@ After selecting the [relevant restore point](#select-recovery-point), proceed to
 > [!IMPORTANT]
 > All details about various restore options and their dependencies are mentioned [here](./backup-azure-arm-restore-vms.md#restore-options). Please review before proceeding to triggering these operations.
 
-Triggering restore operations is a *POST* request. To know more about the API, refer to the ["trigger restore" REST API](/rest/api/backup/restores/trigger).
+Triggering restore operations is a *POST* request. Learn more about the  ["trigger restore" REST API](/rest/api/backup/restores/trigger).
 
 ```http
 POST https://management.azure.com/Subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupFabrics/{fabricName}/protectionContainers/{containerName}/protectedItems/{protectedItemName}/recoveryPoints/{recoveryPointId}/restore?api-version=2019-05-13
 ```
 
 The `{containerName}` and `{protectedItemName}` are as constructed [here](backup-azure-arm-userestapi-backupazurevms.md#responses-to-get-operation). `{fabricName}` is "Azure" and the `{recoveryPointId}` is the `{name}` field of the recovery point mentioned [above](#example-response).
 
-Once the recovery point is obtained, we need to construct the request body for the relevant restore scenario. The following sections outline the request body for each scenario.
+Once the recovery point is obtained, construct the request body for the relevant restore scenario. The following sections outline the request body for each scenario:
 
 - [Restore disks](#restore-disks)
 - [Replace disks](#replace-disks-in-a-backed-up-virtual-machine)
@@ -208,21 +210,21 @@ Since the restore job is a long running operation, it should be tracked as expla
 
 ### Restore disks
 
-If there's a need to customize the creation of a VM from the backup data, you can just restore disks into a chosen storage account and create a VM from those disks according to their requirements. The storage account should be in the same region as the Recovery Services vault and shouldn't be zone redundant. The disks, as well as the configuration of the backed-up VM ("vmconfig.json"), will be stored in the given storage account. As explained [above](#restore-operations), the relevant request body for restore disks is provided below.
+If there's a need to customize the creation of a VM from the backup data, restore the disks into a chosen storage account and create a VM from those disks according to their requirements. The storage account should be in the same region as the Recovery Services vault and shouldn't be zone redundant. The disks, as well as the configuration of the backed-up VM ("vmconfig.json"), is stored in the given storage account. As explained [here](#restore-operations), the relevant request body for restore disks is provided below.
 
 #### Create request body
 
-To trigger a disk restore from an Azure VM backup, following are the components of the request body.
+To trigger a disk restore from an Azure VM backup, following are the components of the request body:
 
 |Name  |Type  |Description  |
 |---------|---------|---------|
 |properties     | [IaaSVMRestoreRequest](/rest/api/backup/restores/trigger#iaasvmrestorerequest)        |    RestoreRequestResourceProperties     |
 
-For the complete list of definitions of the request body and other details, refer to [trigger Restore REST API document](/rest/api/backup/restores/trigger#request-body).
+For the complete list of definitions of the request body and other details, see the [trigger Restore REST API article](/rest/api/backup/restores/trigger#request-body).
 
 ##### Example request
 
-The following request body defines properties required to trigger a disk restore.
+The following request body defines properties required to trigger a disk restore:
 
 ```json
 {
@@ -266,11 +268,11 @@ If you're [selectively backing up disks](backup-azure-arm-userestapi-backupazure
 
 ```
 
-Once you track the response as explained [above](#responses), and the long running job is complete, the disks and the configuration of the backed up virtual machine ("VMConfig.json") will be present in the given storage account.
+Once you track the response as explained [here](#responses), and the long running job is complete, the disks and the configuration of the backed up virtual machine ("VMConfig.json") appears in the given storage account.
 
 ### Replace disks in a backed-up virtual machine
 
-While restore disks creates disks from the recovery point, replace disks replaces the current disks of the backed-up VM with the disks from the recovery point. As explained [above](#restore-operations), the relevant request body for replacing disks is provided below.
+While restore disks creates disks from the recovery point, replace disks replaces the current disks of the backed-up VM with the disks from the recovery point. As explained [here](#restore-operations), the relevant request body for replacing disks is provided below.
 
 #### Create request body
 
@@ -446,7 +448,7 @@ The recovery point is identified with the `{name}` field in the above response.
 
 ### Get access token
 
-To perform cross-region restore, you'll require an access token to authorize your request to access replicated restore points in the secondary region. To get an access token, follow these steps:
+To perform cross-region restore, you require an access token to authorize your request to access replicated restore points in the secondary region. To get an access token, follow these steps:
 
 #### Step 1: