Merge pull request #301290 from AbhishekMallick01/Jun-13-2025-UUF

Addressed UUF #354386

Author: prmerger-automator[bot]

articles/backup/manage-recovery-points.md

@@ -2,7 +2,7 @@
 title: Manage recovery points
 description: Learn how the Azure Backup service manages recovery points for virtual machines
 ms.topic: how-to
-ms.date: 03/27/2025
+ms.date: 06/13/2025
 author: jyothisuri
 ms.author: jsuri
 ---
@@ -96,10 +96,16 @@ There are two ways to stop protecting a VM:
 
 ## Impact of deleting a VM without stop protection
 
-Deleting a VM without stop protection has impact on recovery points, and is an undesirable scenario. Ideally backups should be stopped before deleting the virtual machine. Since the resource doesn't exist, no further backups will be triggered and the item will still show as Healthy. If a manual backup is triggered, this will force a check on the VM and the job will fail with the [VMNotFoundV2 error](backup-azure-vms-troubleshoot.md#320001-resourcenotfound---could-not-perform-the-operation-as-vm-no-longer-exists--400094-bcmv2vmnotfound---the-virtual-machine-doesnt-exist--an-azure-virtual-machine-wasnt-found). The recovery points will be cleaned periodically according to the retention policy, but the last copy of the virtual machine will remain forever and you'll be billed accordingly. Depending on your scenario, you have the following two options:
+Deleting a virtual machine (VM) without first stopping protection can impact recovery points and isn't recommended. Ideally, backups should be stopped before deleting the VM. After the VM is deleted, no further backups are triggered, but the backup item still appears as **Healthy** in the Recovery Services vault. If a manual backup is attempted after deletion, the backup job forces a check on the VM and fails with a [**VMNotFoundV2** error](backup-azure-vms-troubleshoot.md#320001-resourcenotfound---could-not-perform-the-operation-as-vm-no-longer-exists--400094-bcmv2vmnotfound---the-virtual-machine-doesnt-exist--an-azure-virtual-machine-wasnt-found). Although recovery points are cleaned periodically according to the retention policy, the last copy of the VM remains indefinitely.
 
-- **Option 1:** Restore the VM using any of the recovery points. If you want to recover the deleted VM, restore using the same name and in the same resource group. If you protect the restored VM to the same vault, then the existing recovery points will automatically get attached.
-- **Option 2:** Go to the Recovery Services vault and stop protection with delete data.
+Depending on your scenario, you have the following options:
+
+- **Restore the VM**: You can restore the VM using any of the available recovery points. To ensure continuity, restore the VM using the same name and place it in the same resource group. If you then protect the restored VM using the same vault, the existing recovery points automatically reattach.
+
+- **Stop VM protection and delete data**: You can go to the Recovery Services vault and choose to stop protection with delete data, which removes the backup item and associated recovery points.
+
+>[!Note]
+>Even after the VM is deleted, the last recovery point is retained indefinitely unless protection is explicitly stopped with data deletion. As a result, billing continues for the retained backup data. Learn about [stop protecting a VM](backup-azure-manage-vms.md#stop-protecting-a-vm).
 
 ### Impact of expired recovery points for items in soft deleted state