Merge pull request #298192 from MicrosoftDocs/main

PhilKang0704 · web-flow · commit b8c77ed9ab08 · 2025-04-14T13:30:33.000+08:00
4/14/2025 11:00 AM IST Publish
diff --git a/articles/backup/backup-architecture.md b/articles/backup/backup-architecture.md
@@ -2,7 +2,7 @@
 title: Architecture Overview 
 description: Provides an overview of the architecture, components, and processes used by the Azure Backup service.
 ms.topic: overview
-ms.date: 07/18/2024
+ms.date: 04/14/2025
 ms.service: azure-backup
 author: jyothisuri
 ms.author: jsuri
diff --git a/articles/backup/backup-rbac-rs-vault.md b/articles/backup/backup-rbac-rs-vault.md
@@ -3,7 +3,7 @@ title: Manage Backups with Azure role-based access control
 description: Use Azure role-based access control to manage access to backup management operations in Recovery Services vault.
 ms.reviewer: utraghuv
 ms.topic: how-to
-ms.date: 09/11/2024
+ms.date: 04/14/2025
 ms.service: azure-backup
 author: jyothisuri
 ms.author: jsuri
@@ -40,7 +40,7 @@ The following table captures the Backup management actions and corresponding min
 | | Virtual Machine Contributor | VM resource |  Alternatively, instead of a built-in-role, you can consider a custom role which has the following permissions: Microsoft.Compute/virtualMachines/write Microsoft.Compute/virtualMachines/read Microsoft.Compute/virtualMachines/instanceView/read |
 | On-demand backup of VM | Backup Operator | Recovery Services vault |   |
 | Restore VM | Backup Operator | Recovery Services vault |   |
-| | Contributor | Resource group in which VM will be deployed |   Alternatively, instead of a built-in-role, you can consider a custom role which has the following permissions:  Microsoft.Resources/subscriptions/resourceGroups/write Microsoft.DomainRegistration/domains/write (required only for classic VM restore and not required for managed VMs), Microsoft.Compute/virtualMachines/write Microsoft.Compute/virtualMachines/read Microsoft.Network/virtualNetworks/read Microsoft.Network/virtualNetworks/subnets/read Microsoft.Network/virtualNetworks/subnets/join/action |
+| | Contributor | Resource group in which VM will be deployed |   Alternatively, instead of a built-in-role, you can consider a custom role which has the following permissions: <br><br> - `Microsoft.Resources/subscriptions/resourceGroups/write` <br> - `Microsoft.Resources/subscriptions/resourceGroups/read` - According to validation, this permission is also needed. <br> - `Microsoft.DomainRegistration/domains/write` <br> - `Microsoft.Compute/virtualMachines/write` <br> - `Microsoft.Compute/virtualMachines/read` <br> - `Microsoft.Network/virtualNetworks/read Microsoft.Network/virtualNetworks/subnets/read` <br> - `Microsoft.Network/virtualNetworks/subnets/join/action` <br><br> Additionally, if you want to set custom role despite built-in-role, following permissions are needed on the Staging Location's Storage Account: <br><br> - `Microsoft.Storage/storageAccounts/read` <br> - `Microsoft.Storage/storageAccounts/write` |
 | | Virtual Machine Contributor | Source VM that got backed up |   Alternatively, instead of a built-in-role, you can consider a custom role which has the following permissions: Microsoft.Compute/virtualMachines/write Microsoft.Compute/virtualMachines/read|
 | | Storage Account Contributor | Storage account resource where disks are going to be restored |   Alternatively, instead of a built-in-role, you can consider a custom role which has the following permissions: Microsoft.Storage/storageAccounts/write Microsoft.Storage/storageAccounts/listkeys/action |
 | Restore unmanaged disks VM backup | Backup Operator | Recovery Services vault |
diff --git a/articles/backup/restore-azure-encrypted-virtual-machines.md b/articles/backup/restore-azure-encrypted-virtual-machines.md
@@ -2,7 +2,7 @@
 title: Restore encrypted Azure VMs
 description: Describes how to restore encrypted Azure VMs with the Azure Backup service.
 ms.topic: how-to
-ms.date: 03/27/2025
+ms.date: 04/14/2025
 author: jyothisuri
 ms.author: jsuri
 ---
@@ -21,6 +21,7 @@ Review the known limitations before you start restore of an encrypted VM
 - Azure Backup supports VMs encrypted using standalone keys. Any key that's a part of a certificate used to encrypt a VM isn't currently supported.
 - ADE encrypted VMs can’t be recovered at the file/folder level. You need to recover the entire VM to restore files and folders.
 - When restoring a VM, you can't use the [replace existing VM](backup-azure-arm-restore-vms.md#restore-options) option for ADE encrypted VMs. This option is only supported for unencrypted managed disks.
+- - During Azure VM restore, the encryption settings appear only when the vault is CMK encryption enabled.
 
 
 ## Restore an encrypted VM
@@ -64,7 +65,7 @@ Azure Backup supports Cross Region Restore of encrypted Azure VMs to the [Azure
 
 ## Move an encrypted Azure VM
 
-Moving an encrypted VM across vault or resource group is same as moving a backed up Azure Virtual machine. See,
+Moving an encrypted VM across vault or resource group is same as moving a backed-up Azure Virtual machine. See,
 
 - [Steps to move an Azure virtual machine to a different recovery service vault](backup-azure-move-recovery-services-vault.md#move-an-azure-virtual-machine-to-a-different-recovery-service-vault)
 - [Steps to move an Azure virtual machine to different resource group or subscription](../azure-resource-manager/management/move-resource-group-and-subscription.md)
diff --git a/articles/cost-management-billing/manage/programmatically-create-subscription-enterprise-agreement.md b/articles/cost-management-billing/manage/programmatically-create-subscription-enterprise-agreement.md
@@ -1,13 +1,13 @@
 ---
 title: Programmatically create Azure Enterprise Agreement subscriptions with the latest APIs
 description: Learn how to create Azure Enterprise Agreement subscriptions programmatically using the latest versions of REST API, Azure CLI, Azure PowerShell, and Azure Resource Manager templates.
-author: prashantsaini4
+author: preetione
 ms.service: cost-management-billing
 ms.subservice: billing
 ms.topic: how-to
-ms.date: 01/22/2025
-ms.reviewer: prsaini
-ms.author: prsaini
+ms.date: 04/14/2025
+ms.reviewer: presharm
+ms.author: presharm
 ms.custom: devx-track-azurepowershell, devx-track-azurecli, devx-track-arm-template, devx-track-bicep
 ---
 
diff --git a/includes/azure-vm-backup-process.md b/includes/azure-vm-backup-process.md
@@ -2,7 +2,7 @@
 author: v-amallick
 ms.service: Azure Backup  
 ms.topic: include
-ms.date: 03/15/2024
+ms.date: 04/14/2025
 ms.author: v-amallick
 ---
 
@@ -18,7 +18,7 @@ ms.author: v-amallick
     - By default, Backup takes full VSS backups.
     - If Backup can't take an app-consistent snapshot, then it takes a file-consistent snapshot of the underlying storage (because no application writes occur while the VM is stopped).
 1. For Linux VMs, Backup takes a file-consistent backup. For app-consistent snapshots, you need to manually customize pre/post scripts.
-1. For Windows VMs, **Microsoft Visual C++ 2013 Redistributable (x64) version 12.0.40660** is installed, the startup of Volume Shadow Copy Service (VSS) is changed to *automatic*, and a Windows Service **IaaSVmProvider** is added.
+1.  For Windows VMs, **Microsoft Visual C++ 2015 Redistributable (x64) version 14.40.33810.0** is installed, the startup of Volume Shadow Copy Service (VSS) is changed to automatic, and a Windows Service **IaaSVmProvider** is added.
 1. After Backup takes the snapshot, it transfers the data to the vault.
     - The backup is optimized by backing up each VM disk in parallel.
     - For each disk that's being backed up, Azure Backup reads the blocks on the disk and identifies and transfers only the data blocks that changed (the delta) since the previous backup.
