Close Menu
Peter Klapwijk – In The Cloud 24-7Peter Klapwijk – In The Cloud 24-7
    Facebook X (Twitter) Instagram
    Peter Klapwijk – In The Cloud 24-7Peter Klapwijk – In The Cloud 24-7
    • Home
    • Intune
    • Windows
      • Modern Workplace
    • macOS
    • Android
    • iOS
    • Automation
      • Logic Apps
      • Intune Monitoring
      • GitHub
    • Security
      • Passwordless
      • Security
    • Speaking
    • About me
    Peter Klapwijk – In The Cloud 24-7Peter Klapwijk – In The Cloud 24-7
    Home»Intune»Setup a Windows 10 Multi App Kiosk device with Microsoft Intune
    Intune

    Setup a Windows 10 Multi App Kiosk device with Microsoft Intune

    Peter KlapwijkBy Peter KlapwijkAugust 6, 2019Updated:January 3, 202095 Mins Read

    A few months ago I wrote this article about setting up a Windows 10 kiosk device using Microsoft Intune and Windows AutoPilot. In that article I used the kiosk single app mode, to restrict the device to run one single app. In Intune we also have the option to setup a kiosk device using the kiosk multi app mode. In multi app mode the logged on user is allowed to run multiple apps, but still runs as a kiosk device. Access to other apps and for example file explorer is still prevented.
    In multiple apps mode we are also able to configure the device to AutoLogon with a (local) kiosk account, but we also have the option to allow Azure AD users to logon to the device and work on the kiosk device with the AAD account. This could be handy when you want to provide a single-sign on experience to applications which are connected to Azure AD.

    In this blog post I won`t show you how to setup Windows AutoPilot in self-deploying mode to automatically enroll a Windows 10 device in Azure AD and Intune, for those steps you can read my previous article. The steps I will show in this article are:

    • Create a customized start layout
    • Get the AppUserModeId (AUMID)
    • Configure the Kiosk multi app Configuration Profile
    • Configure the Device Restrictions Profile (Optional)
    • End-user experience

    Create a customized start layout

    Because the kiosk device is running multiple apps, we need to present these apps to the end-user in a nice way. In my opinion the way to do that is with a customized Start layout.
    Sign in to a Windows 10 (test) device and set the device in tablet mode.

    Configure the start menu as you like it, containing the applications the kiosk device will be running.

    To export the customized start layout open PowerShell. Use the Export-StartLayout command to export the start layout like in the screen below:
    Export-StartLayout -Path C:\Temp\InTheCloud247Kiosk.xml
    In a next step we upload the xml file to Intune.

    Get the AppUserModeId (AUMID)

    For every application we make available on the kiosk device, we need the Application ID (AppUserModeId or AUMID). There are several ways to retrieve the AUMID like using a PowerShell script, but I will show how to retrieve it using file explorer.
    Open the RUN dialog (WIN + R), Enter shell:AppsFolder and hit Enter.

    Hit F10, click View and Choose details…

    Check AppUserModeId and click OK

    Make sure Folder view is set to Details.
    Search for the applications you want to publish to the kiosk device and note the AppUserModeId.

    Configure the Kiosk multi app Configuration Profile

    We have created the customized start layout file and collected the AppUserModeId`s, time to create the configuration policy with this information.

    • Sign-in to the Device Management Portal
    • Browse to Device Configuration – Profiles
    • Click Create Profile
    • Give the policy a Name
    • Fill in the Description (optional)
    • Choose Windows 10 and later as Platform
    • Choose Kiosk as Profile type
    • Click the Settings tab
    • Choose Multi app kiosk as Kiosk mode
    • Choose No for the Windows 10 in S mode
    • Choose the Logon type of your choice (you can choose Autologon, but also select an Azure AD user or Group)
      Here you can also add the various types of applications; Store apps, Win32 apps or apps by AUMID.
      If you want a default browser, just click Add Microsoft Edge or click Add Kiosk Browser.

    Below is an example how to add a Win32 app;
    Application name: Google Chrome
    Local path to executable: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
    AUMID: Chrome

    Back at the Settings tab we set the Start Layout.

    • At Use alternative Start layout choose Yes
    • Click the Folder icon
    • Browse to the previously created xml file and select the file
    • Choose the other options which you want to set
    • Click OK and click Create to create the profile
      Don`t forget to assign the policy to a group.

    Configure the Device Restrictions Profile (Optional)

    Creating a Device Restrictions profile is optional. In this example I used it to further configure the Edge browser and to set a custom background.

    • Browse Device Configuration – Profiles
    • Click Create Profile
    • Give the policy a Name
    • Fill in the Description (optional)
    • Choose Windows 10 and later as Platform
    • Choose Device Restrictions as Profile type
    • Click the Settings tab
    • Click the Microsoft Edge browser tab
    • Choose Normal mode (multi-app kiosk)

    Configure the required settings on the several tabs, like setting the Start page.

    • If you want to set a custom background browse to the Personalization tab
    • Fill in the url to the background image
    • Click OK.
    • Click Create to create the profile
      Don`t forget to assign the profile to a security group.

    End-user Experience

    After enrolling the device to Azure AD and Intune and the confiuration profiles are set, you`re kiosk multi app device is ready. Depending on the choice you made for the User logon type the kiosk user is logged on automatically or a user needs to logon manually.
    I have set the Edge browser to Autolaunch, so the Edge browser is started directly after loggin on to the device.

    If you close the application, you are presented the customized Start menu and see the custom background.

    Autopilot Azure AD Browser Edge EMS Intune KIOSK MEM Microsoft 365 Microsoft Edge Microsoft Endpoint Manager Windows10
    Share. Facebook Twitter LinkedIn Email WhatsApp
    Peter Klapwijk
    • Website
    • X (Twitter)
    • LinkedIn

    Peter is a Security (Intune) MVP since 2020 and is working as Modern Workplace Engineer at Wortell in The Netherlands. He has more than 15 years of experience in IT, with a strong focus on Microsoft technologies like Microsoft Intune, Windows, and (low-code) automation.

    Related Posts

    Manage Edge Tracking prevention settings with Microsoft Intune

    December 6, 2019

    How to setup an Android Enterprise kiosk device with Microsoft Intune

    April 25, 2019

    How to start with Android Enterprise Corporate owned dedicated devices in Microsoft Intune

    April 24, 2019
    View 9 Comments

    9 Comments

    1. Denzel Marimuthu on October 23, 2019 14:44

      Hi,
      Thanks for this post. Did you run into an issue of the “Kiosk” keeps signing out when trying to login.
      I have this issue when using kiosk in multi mode.

      Regards
      Denzel

      Reply
      • Peter Klapwijk on October 23, 2019 15:08

        On hardware have no issues. When first testing Kiosk mode using VMs I had issues like the device isn`t locked as Kiosk machine and the auto logon didn`t work. But no issue that signs me out.

        Reply
      • André Mieth on October 31, 2019 10:23

        Hi Denzel,
        I know this issue. There is a timing issue in applying the policy and getting the device ready. Be sure to use the latest 1903 build, add some more store apps to your kiosk policy (to get more “time”, e.g. Maps, OneNote..) and try it again.

        BR
        André

        Reply
    2. Bill on November 11, 2021 09:20

      Hi Peter, Thanks for this but I am running into some issues, when I go onto the device I have logged in with my AAD account I cant seem to open the apps which I have allowed I get the error: We cant open (then location address) Your school has blocked it. How do I allow this to open and work correctly! Any ideas?

      Reply
      • Peter Klapwijk on November 11, 2021 13:57

        You might want to start with reviewing the AppLocker events as the lockdown of the device is based on AppLocker. One of these events might show you what process is started and blocked.

        Reply
    3. D Khandwala on December 2, 2021 16:49

      Nice

      Reply
    4. Lajos on July 24, 2022 18:49

      Hi,

      How is possible to start a simple exe as a custom application (without AMUID)

      Thanks,

      Reply
      • Jacqui on August 17, 2022 19:18

        I would love to know the answer to this too. I have an app from a supplier which has no installation process, just copying files, then running the EXE. The app is delivered via Intune/Powershell script wrapped into a Win32 app. Can this app be run in Kiosk mode?

        Reply
        • Will on May 10, 2023 17:39

          I had a similar issue, I packaged the exe as a Win32 app that copied it to a known folder. for the multiapp kiosk policy I set the ‘AUMID\PATH’ and ‘DesktopApplicationId/AUMID for the Win32 app’ as the path to the exe. logging in ran the app

          Reply
    Leave A Reply Cancel Reply

    Peter Klapwijk

    Hi! Welcome to my blog post.
    I hope you enjoy reading my articles.

    Hit the About Me button to get in contact with me or leave a comment.

    Awards
    Sponsor
    Latest Posts

    Update Windows Defender during Windows Autopilot enrollments

    May 16, 2025

    Hide the “Turn on an ad privacy feature” pop-up in Chrome with Microsoft Intune

    April 19, 2025

    How to set Google as default search provider with Microsoft Intune

    April 18, 2025

    Using Windows Autopilot device preparation with Windows 365 Frontline shared cloud PCs

    April 13, 2025
    follow me
    • Twitter 4.8K
    • LinkedIn 6.1K
    • YouTube
    • Bluesky 1.5K
    Tags
    Administrative Templates Android Automation Autopilot Azure Azure AD Browser Conditional Access Edge EMS Exchange Online Feitian FIDO2 Flow Google Chrome Graph Graph API Identity Management Intune Intune Monitoring iOS KIOSK Logic Apps macOS MEM MEMMonitoring Microsoft 365 Microsoft Edge Microsoft Endpoint Manager Modern Workplace Office 365 OneDrive for Business Outlook Passwordless PowerApps Power Automate Security SharePoint Online Teams Windows Windows 10 Windows10 Windows 11 Windows Autopilot Windows Update
    Copy right

    This information is provided “AS IS” with no warranties, confers no rights and is not supported by the authors, or In The Cloud 24-7.

     

    Copyright © 2025 by In The Cloud 24-7/ Peter Klapwijk. All rights reserved, No part of the information on this web site may be reproduced or posted in any form or by any means without the prior written permission of the publisher.

    Shorthand; Don’t pass off my work as yours, it’s not nice.

    Recent Comments
    • Adam on Get notified on expiring Azure App Registration client secrets
    • Peter Klapwijk on Update Windows Defender during Windows Autopilot enrollments
    • Rob van de Ven on Add a certificate to the Trusted Publishers with Intune without reporting errors
    • Carl on Update Windows Defender during Windows Autopilot enrollments
    • Peter Klapwijk on The next step in a passwordless Windows experience
    most popular

    Application installation issues; Download pending

    October 1, 2024

    Restrict which users can logon into a Windows 10 device with Microsoft Intune

    April 11, 2020

    How to change the Windows 11 language with Intune

    November 11, 2022

    Update Microsoft Edge during Windows Autopilot enrollments

    July 9, 2024
    Peter Klapwijk – In The Cloud 24-7
    X (Twitter) LinkedIn YouTube RSS Bluesky
    © 2025 ThemeSphere. Designed by ThemeSphere.

    Type above and press Enter to search. Press Esc to cancel.

    Manage Cookie Consent
    To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
    Functional Always active
    The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
    Preferences
    The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
    Statistics
    The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
    Marketing
    The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
    Manage options Manage services Manage {vendor_count} vendors Read more about these purposes
    View preferences
    {title} {title} {title}