Update Assigned Access references to Shell Launcher

.openpublishing.redirection.windows-configuration.json

@@ -754,6 +754,51 @@
       "source_path": "windows/configuration/kiosk/lock-down-windows-11-to-specific-apps.md",
       "redirect_url": "/windows/configuration/kiosk/create-xml",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "windows/configuration/kiosk/kiosk-additional-reference.md",
+      "redirect_url": "/windows/configuration/kiosk",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "windows/configuration/kiosk/kiosk-mdm-bridge.md",
+      "redirect_url": "/windows/configuration/kiosk/assigned-access-quickstart-kiosk",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "windows/configuration/kiosk/kiosk-policies.md",
+      "redirect_url": "/windows/configuration/kiosk/assigned-access-policy-settings",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "windows/configuration/kiosk/kiosk-shelllauncher.md",
+      "redirect_url": "/windows/configuration/kiosk/shell-launcher-configure",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "windows/configuration/kiosk/kiosk-validate.md",
+      "redirect_url": "/windows/configuration/kiosk",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "windows/configuration/kiosk/kiosk-xml.md",
+      "redirect_url": "/windows/configuration/kiosk/assigned-access-configuration-file",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "windows/configuration/kiosk/setup-digital-signage.md",
+      "redirect_url": "/windows/configuration/kiosk/assigned-access-configure",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "windows/configuration/kiosk/kiosk-single-app.md",
+      "redirect_url": "/windows/configuration/kiosk/assigned-access-configure",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "windows/configuration/kiosk/kiosk-methods.md",
+      "redirect_url": "/windows/configuration/kiosk",
+      "redirect_document_id": false
     }
   ]
 }

windows/configuration/assigned-access/assigned-access-configuration-file.md

@@ -1,7 +1,7 @@
 ---
 title: Create an Assigned Access configuration file
 description: Learn how to create an XML file to configure a kiosk device.
-ms.date: 02/12/2024
+ms.date: 02/26/2024
 ms.topic: how-to
 zone_pivot_groups: windows-versions-11-10
 appliesto:
@@ -217,7 +217,7 @@ The easiest way to create a customized Start layout is to configure the Start me
 
 > [!NOTE]
 > - The test device on which you customize the Start layout should have the same OS version that is installed on the device where you plan to deploy the Assigned Access configuration
-> - There are no apps pinned on the taskbar in the multi-app mode, and it's not supported to configure Taskbar layout using the <CustomTaskbarLayoutCollection> tag in a layout modification XML as part of the Assigned Access configuration
+> - There are no apps pinned on the taskbar in the multi-app mode, and it's not supported to configure Taskbar layout using the `<CustomTaskbarLayoutCollection>` tag in a layout modification XML as part of the Assigned Access configuration
 
 The following example pins Calculator, Photos, Weather, Calculator, Command Prompt, and Windows PowerShell apps to the Start menu.
 
@@ -296,11 +296,15 @@ Define whether you want to have the taskbar present in the kiosk device. For tab
 
 The following example exposes the taskbar to the end user:
 
+```xml
 <Taskbar ShowTaskbar="true"/>
+```
 
 The following example hides the taskbar:
 
+```xml
 <Taskbar ShowTaskbar="false"/>
+```
 
 > [!NOTE]
 > This is different from the **Automatically hide the taskbar** option in tablet mode, which shows the taskbar when swiping up from or moving the mouse pointer down to the bottom of the screen. Setting **ShowTaskbar** as **false** will always keep the taskbar hidden.
@@ -309,7 +313,7 @@ The following example hides the taskbar:
 
 ### KioskModeApp
 
-**KioskModeApp** is used for a [kiosk profile](#profile) only. Enter the AUMID for a single app. You can only specify one kiosk profile in the XML.
+**KioskModeApp** is used for a kiosk profile only. Enter the AUMID for a single app. You can only specify one kiosk profile in the XML.
 
 ```xml
 <KioskModeApp AppUserModelId="Microsoft.WindowsCalculator_8wekyb3d8bbwe!App"/>

windows/configuration/assigned-access/assigned-access-configure.md

@@ -5,7 +5,7 @@ ms.date: 05/12/2023
 ms.topic: how-to
 ---
 
-## Configure Assigned Access
+# Configure Assigned Access
 
 ## Configure a kiosk in Microsoft Intune
 
@@ -18,9 +18,9 @@ To configure a kiosk in Microsoft Intune, see:
 
 Process:
 
-1. [Create XML file](#create-xml-file)
+1. Create XML file
-1. [Add XML file to provisioning package](#add-xml)
+1. Add XML file to provisioning package
-1. [Apply provisioning package to device](#apply-ppkg)
+1. Apply provisioning package to device
 
 Watch how to use a provisioning package to configure a multi-app kiosk.
 
@@ -29,14 +29,14 @@ Watch how to use a provisioning package to configure a multi-app kiosk.
 An assigned access multi-app kiosk runs one or more apps from the desktop. People using the kiosk see a customized Start that shows only the apps that are allowed. With this approach, you can configure a locked-down experience for different account types. A multi-app kiosk is appropriate for devices that are shared by multiple people. Here's a guide on how to set up a multi-app kiosk.
 
 > [!WARNING]
-> The assigned access feature is intended for corporate-owned fixed-purpose devices, like kiosks. When the multi-app assigned access configuration is applied on the device, [certain policies](kiosk-policies.md) are enforced system-wide, and will impact other users on the device. Deleting the kiosk configuration will remove the assigned access lockdown profiles associated with the users, but it cannot revert all the enforced policies (such as Start layout). A factory reset is needed to clear all the policies enforced via assigned access.
+> The assigned access feature is intended for corporate-owned fixed-purpose devices, like kiosks. When the multi-app assigned access configuration is applied on the device, [certain policy settings](assigned-access-policy-settings.md) are enforced system-wide, and will impact other users on the device. Deleting the kiosk configuration will remove the assigned access lockdown profiles associated with the users, but it cannot revert all the enforced policies (such as Start layout). A factory reset is needed to clear all the policies enforced via assigned access.
 
 > [!TIP]
 > Be sure to check the [configuration recommendations](kiosk-prepare.md) before you set up your kiosk.
 
 ### Provisioning package
 
-Before you add the XML file to a provisioning package, you can [validate your configuration XML against the XSD](kiosk-xml.md#xsd-for-assignedaccess-configuration-xml).
+Before you add the XML file to a provisioning package, you can [validate your configuration XML against the XSD](assigned-access-xsd.md).
 
 Use the Windows Configuration Designer tool to create a provisioning package. [Learn how to install Windows Configuration Designer.](../provisioning-packages/provisioning-install-icd.md).
 
@@ -150,11 +150,6 @@ You have several options for configuring your single-app kiosk.
   - Windows 10 Pro version 1709+, Enterprise, and Education
   - Windows 11
 
-> [!TIP]
-> You can also configure a kiosk account and app for single-app kiosk within [XML in a provisioning package](lock-down-windows-10-to-specific-apps.md) by using a [kiosk profile](lock-down-windows-10-to-specific-apps.md#profile).
-
->
-> Be sure to check the [configuration recommendations](kiosk-prepare.md) before you set up your kiosk.
 
 ## Set up a kiosk in local Settings
 
@@ -212,8 +207,8 @@ To configure a device using the Windows PowerShell cmdlet:
 
 For more innformation:
 
-- [Learn how to get the AUMID](./find-the-application-user-model-id-of-an-installed-app.md)
+- [Find the Application User Model ID of an installed app](./find-aumid.md)
-- [Learn how to get the AppName](/powershell/module/assignedaccess/set-assignedaccess)
+- [Set-AssignedAccess](/powershell/module/assignedaccess/set-assignedaccess)
 
 To remove assigned access, using PowerShell, run the following cmdlet:
 

windows/configuration/assigned-access/assigned-access-quickstart-kiosk.md

@@ -100,7 +100,7 @@ After the settings are applied, reboot the device. A local user account is autom
 > [!div class="nextstepaction"]
 > Learn more how to configure Windows to run a single app or multiple apps with Assigned Access:
 >
-> [Create an Assigned Access configuration file](create-assigned-access-configuration.md)
+> [Configure Assigned Access](assigned-access-configure.md)
 
 <!--links-->
 

windows/configuration/assigned-access/assigned-access-quickstart-restricted-experience.md

@@ -111,7 +111,7 @@ After the settings are applied, reboot the device. A local user account is autom
 > [!div class="nextstepaction"]
 > Learn more how to configure Windows to run a single app or multiple apps with Assigned Access:
 >
-> [Create an Assigned Access configuration file](create-assigned-access-configuration.md)
+> [Configure Assigned Access](assigned-access-configure.md)
 
 <!--links-->
 

windows/configuration/assigned-access/shell-launcher-xsd.md

@@ -1,5 +1,5 @@
 ---
-title: Assigned Access XML Schema Definition (XSD)
+title: Shell Launcher XML Schema Definition (XSD)
 description: Shell Launcher XSD reference article.
 ms.topic: reference
 ms.date: 02/15/2024

windows/configuration/assigned-access/toc.yml

@@ -27,8 +27,6 @@ items:
       href: shell-launcher-configuration-file.md
     - name: Find the AUMID of an installed app
       href: find-aumid.md
-    - name: Use Shell Launcher to create a Windows client kiosk
-      href: kiosk-shelllauncher.md
 - name: Reference
   items:
     - name: Assigned Access CSP