From 869ad3f27dafdbf89a7e2318ea30cf78a78de4dd Mon Sep 17 00:00:00 2001
From: Doug Eby <17034284+dougeby@users.noreply.github.com>
Date: Fri, 11 Oct 2024 10:53:27 -0700
Subject: [PATCH] Revert "Update azure-virtual-desktop-multi-session.md"

---
 .../intune/fundamentals/azure-virtual-desktop-multi-session.md  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/memdocs/intune/fundamentals/azure-virtual-desktop-multi-session.md b/memdocs/intune/fundamentals/azure-virtual-desktop-multi-session.md
index 9c5bc23c4fe..9c207d54018 100644
--- a/memdocs/intune/fundamentals/azure-virtual-desktop-multi-session.md
+++ b/memdocs/intune/fundamentals/azure-virtual-desktop-multi-session.md
@@ -223,7 +223,7 @@ The following Windows 10 or Windows 11 desktop device remote actions aren't supp
 
 ## Retirement
 
-Deleting VMs from Azure will leave orphaned device records in the Microsoft Intune admin center. AVD machines will be soft deleted after 30 days of inacitivty and removed permanently after 60 days. For more information, see [Using Intune device cleanup rules](https://techcommunity.microsoft.com/t5/device-management-in-microsoft/using-intune-device-cleanup-rules-updated-version/ba-p/3760854).
+Deleting VMs from Azure will leave orphaned device records in the Microsoft Intune admin center. They'll be automatically cleaned up according to the cleanup rules configured for the tenant.
 
 ## Security baselines