This commit is contained in:
Paolo Matarazzo
2025-02-26 16:40:37 -05:00
parent 5f42050e7e
commit 9ef571e5f5
9 changed files with 30 additions and 28 deletions

View File

@ -98,7 +98,7 @@ After the settings are applied, reboot the device. A local user account is autom
> [!div class="nextstepaction"]
> Learn more about Assigned Access and how to configure it:
>
> [Assigned Access overview](overview.md)
> [Assigned Access overview](index.md)
[WIN-3]: /windows/client-management/mdm/assignedaccess-csp
[MEM-1]: /mem/intune/configuration/custom-settings-windows-10

View File

@ -85,7 +85,7 @@ After the settings are applied, reboot the device. A local user account is autom
> [!div class="nextstepaction"]
> Learn more about Assigned Access and how to configure it:
>
> [Assigned Access overview](overview.md)
> [Assigned Access overview](index.md)
<!--links-->

View File

@ -20,7 +20,7 @@ Consider enabling *automatic sign-in* for your kiosk device. When the device res
You can configure the Assigned Access and Shell Launcher XML files with an account to sign-in automatically. For more information, review the articles:
- [Create an Assigned Access configuration XML file](configuration-file.md)
- [Create a Shell Launcher configuration file](shell-launcher/configuration-file.md)
- [Create a Shell Launcher configuration file](../shell-launcher/configuration-file.md)
Alternatively, you can edit the Registry to have an account sign in automatically: