From 8709e68b73a9e3439902313df75e7153eba1b512 Mon Sep 17 00:00:00 2001
From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com>
Date: Mon, 10 Mar 2025 11:46:26 -0400
Subject: [PATCH] Shell Launcher updates

---
 .../configuration/shell-launcher/configure.md  | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/windows/configuration/shell-launcher/configure.md b/windows/configuration/shell-launcher/configure.md
index 95dbe8ea02..d59df53298 100644
--- a/windows/configuration/shell-launcher/configure.md
+++ b/windows/configuration/shell-launcher/configure.md
@@ -231,18 +231,28 @@ Depending on your configuration, you can have a user to automatically sign in to
 
 ## Remove Shell Launcher
 
-Once you no longer need the kiosk configuration, you can remove it.
+Here are the options to remove Shell Launcher, select the method that best fits your needs:
 
-Here's a PowerShell example to remove the Shell Launcher configuration:
+#### [:::image type="icon" source="../images/icons/intune.svg"::: **Intune/CSP**](#tab/intune)
 
-```powershell
+Unassign or delete the policy that contains the configuration.
+
+#### [:::image type="icon" source="../images/icons/provisioning-package.svg"::: **PPKG**](#tab/ppkg)
+
+Uninstall the provisioning package that contains the configuration.
+
+#### [:::image type="icon" source="../../images/icons/powershell.svg"::: **PowerShell**](#tab/ps)
+
+```PowerShell
 $namespaceName="root\cimv2\mdm\dmmap"
 $className="MDM_AssignedAccess"
 $obj = Get-CimInstance -Namespace $namespaceName -ClassName $className
-$obj.ShellLauncher = $null
+$obj.Configuration = $null
 Set-CimInstance -CimInstance $obj
 ```
 
+---
+
 ## Next steps
 
 > [!div class="nextstepaction"]