Merge pull request #295927 from AbhishekMallick01/Mar-7-2025-EEE5

Addressed EEE doc ask #29294173

Author: prmerger-automator[bot]

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

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.