Windows 11 Kiosk Configuration Warning: Don't Use Intune's "Kiosk" Template

This is important information to be aware of.

Turning a Windows device with a fixed purpose into a kiosk device that can be used by an unspecified number of people is a common and important requirement — for service counters, retail stores, factories, reception desks, and similar settings.

🤖✍️ This article was co-written with AI — the AI organized primary sources and drafted the content, and Ebisuda verified the evidence and final quality.

* A kiosk is a configuration designed to provide a uniform service by allowing only approved apps to be used.

* On Windows 11, both single-app and multi-app kiosks can be configured using Assigned Access. For custom desktop apps, Shell Launcher is also an option.

* The most important thing to note is that Microsoft Japan has stated that Intune's "Kiosk" template may not behave as intended on Windows 11.

* When deploying to Windows 11 via Intune, instead of using that template, it's recommended to distribute the XML via a custom configuration profile (OMA-URI).

* The primary source covers everything from XML examples and verification to Intune deployment and troubleshooting.

If Intune's screen has a dedicated kiosk profile, you'd naturally assume selecting it is the right choice.

However, the primary source casually notes that "it may not behave as intended on Windows 11." That's the alarming part.

If you're planning a Kiosk deployment on Windows 11 using Intune, the one thing to watch out for is: use "Custom," not "Kiosk."

* How to Configure a Kiosk for Windows 11 (Microsoft Japan Windows Support)

* Configure kiosks on Windows clients (Microsoft Learn)

* AssignedAccess CSP (Microsoft Learn)

*

I use the paid plugin Ebi Workspace for organizing and recording notes. Multi-AI coordination from Discord is powered by the OSS project Ebi Agent Chat Relay (GitHub). It's currently transitioning from its former name, CCDB.