deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-15 18:33:43 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Fix broken links in configuration files

Browse Source
This commit is contained in:
Paolo Matarazzo
2024-02-29 08:05:30 -05:00
parent 1cc84d6825
commit 28667c4d3a
3 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
windows/configuration/assigned-access/shell-launcher/configuration-file.md
View File

@ -191,7 +191,7 @@ Allowed values are `Desktop` and `UWP`.
## Kiosk example
[!INCLUDE [quickstart-xml](../includes/quickstart-xml.md)]
[!INCLUDE [quickstart-xml](includes/quickstart-xml.md)]

4
windows/configuration/assigned-access/shell-launcher/index.md
View File

@ -35,14 +35,14 @@ Here are some limitations to consider when using Shell Launcher:
[!INCLUDE [tab-intro](../../../../includes/configure/tab-intro.md)]
#### [:::image type="icon" source="../images/icons/intune.svg"::: **Intune/CSP**](#tab/intune)
#### [:::image type="icon" source="../../images/icons/intune.svg"::: **Intune/CSP**](#tab/intune)
You can configure devices using a [custom policy][MEM-1] with the [AssignedAccess CSP][WIN-3].
- **Setting:** `./Vendor/MSFT/AssignedAccess/ShellLauncher`
- **Value:** content of the XML configuration file
#### [:::image type="icon" source="../images/icons/powershell.svg"::: **PowerShell**](#tab/ps)
#### [:::image type="icon" source="../../images/icons/powershell.svg"::: **PowerShell**](#tab/ps)
---

10
windows/configuration/assigned-access/shell-launcher/quickstart-kiosk.md
View File

@ -26,14 +26,14 @@ The examples can be modified to fit your specific requirements. For example, you
[!INCLUDE [tab-intro](../../../../includes/configure/tab-intro.md)]
#### [:::image type="icon" source="../images/icons/intune.svg"::: **Intune/CSP**](#tab/intune)
#### [:::image type="icon" source="../../images/icons/intune.svg"::: **Intune/CSP**](#tab/intune)
> [!TIP]
> Use the following Graph call to automatically create a custom policy in your Microsoft Intune tenant without assignments nor scope tags.
>
> When using this call, authenticate to your tenant in the Graph Explorer window. If it's the first time using Graph Explorer, you may need to authorize the application to access your tenant or to modify the existing permissions. This graph call requires *DeviceManagementConfiguration.ReadWrite.All* permissions.
[!INCLUDE [quickstart-intune](../includes/quickstart-intune.md)]
[!INCLUDE [quickstart-intune](includes/quickstart-intune.md)]
[!INCLUDE [intune-custom-settings-2](../../../../includes/configure/intune-custom-settings-2.md)]
@ -42,13 +42,13 @@ Alternatively, you can configure devices using a [custom policy][MEM-1] with the
- **Setting:** `./Vendor/MSFT/AssignedAccess/ShellLauncher`
- **Value:**
[!INCLUDE [quickstart-xml](../includes/quickstart-xml.md)]
[!INCLUDE [quickstart-xml](includes/quickstart-xml.md)]
#### [:::image type="icon" source="../images/icons/powershell.svg"::: **PowerShell**](#tab/ps)
#### [:::image type="icon" source="../../images/icons/powershell.svg"::: **PowerShell**](#tab/ps)
[!INCLUDE [powershell-wmi-bridge-1](../../../../includes/configure/powershell-wmi-bridge-1.md)]
[!INCLUDE [quickstart-ps](../includes/quickstart-ps.md)]
[!INCLUDE [quickstart-ps](includes/quickstart-ps.md)]
[!INCLUDE [powershell-wmi-bridge-2](../../../../includes/configure/powershell-wmi-bridge-2.md)]