diff --git a/windows/configuration/assigned-access/configuration-file.md b/windows/configuration/assigned-access/configuration-file.md
index 5b08cbb1fd..b0d7fd9e91 100644
--- a/windows/configuration/assigned-access/configuration-file.md
+++ b/windows/configuration/assigned-access/configuration-file.md
@@ -379,7 +379,7 @@ The following example shows how to specify an account to sign in automatically,
```xml
-
+
@@ -440,7 +440,7 @@ Microsoft Entra accounts must be specified with the format: `AzureAD\{UPN}`. `Az
Group accounts are specified using ``. Nested groups aren't supported. For example, if *User A* is member of *Group A*, *Group A* is member of *Group B*, and *Group B* is used in ``, *User A* doesn't have the kiosk experience.
-##### Local group
+#### Local group
Specify the group type as `LocalGroup` and add the group name in the `Name` attribute.
diff --git a/windows/configuration/assigned-access/shell-launcher/configuration-file.md b/windows/configuration/assigned-access/shell-launcher/configuration-file.md
index 9d8395b146..0b98521b96 100644
--- a/windows/configuration/assigned-access/shell-launcher/configuration-file.md
+++ b/windows/configuration/assigned-access/shell-launcher/configuration-file.md
@@ -15,7 +15,7 @@ Let's start by looking at the basic structure of the XML file. A Shell Launcher
- One or multiple `profiles`. Each `profile` defines:
- the application that replaces the standard Windows shell (`Explorer.exe`), which is executed when a user signs in
- - default action to be taken when the application exits, and actions to be taken when the application exits with a specific return code
+ - the default action to take when the application exits, and actions when the application exits with a specific return code
- One or multiple `configs`. Each `config` associates a user account to a `profile`
> [!NOTE]
@@ -137,7 +137,6 @@ In this example, Microsoft Edge is executed in full screen, opening a website. T
```
-
**UWP application**
In this example, the Weather app is executed in full screen.
@@ -161,19 +160,107 @@ xmlns:V2="http://schemas.microsoft.com/ShellLauncher/2019/Configuration">
Under `Configs`, define one or more user accounts and their association with a profile.
-You can specify a name, SID or AutologonAccount
+Individual accounts are specified using ``.
+
+> [!IMPORTANT]
+> Before applying the Shell Launcher configuration, make sure the specified user account is available on the device, otherwise it fails.
+>
+> For both domain and Microsoft Entra accounts, as long as the device is Active Directory joined or Microsoft Entra joined, the account can be discovered in the domain forest or tenant that the device is joined to. For local accounts, it is required that the account exist before you configure the account for Shell Launcher.
+
+#### Local user
+
+Local account can be entered as `devicename\user`, `.\user`, or just `user`.
+
+```xml
+
+
+
+
+```
+
+#### Active Directory user
+
+Domain accounts must be entered using the format `domain\samAccountName`.
+
+```xml
+
+
+
+
+```
+
+#### Microsoft Entra user
+
+Microsoft Entra accounts must be specified with the format: `AzureAD\{UPN}`. `AzureAD` must be provided *as is*, then follow with the Microsoft Entra user principal name (UPN).
+
+```xml
+
+
+
+
+```
When the user account signs in, the associated Shell Launcher profile is applied, loading the application specified in the profile.
```xml
+
-
+
+
+
+
+
+
+
+
+
+
+
```
## Example
-[!INCLUDE [quickstart-xml](includes/quickstart-xml.md)]
+```xml
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+```