AssignedAccess XML Builder Make Kiosks Simple Again

Configuration

1. Setup
Profile + account
2. Apps
Allowed apps
3. Pins
Start + taskbar
4. System
Optional controls
5. Export
Validate & export

Step 1: Choose kiosk mode, set profile details, then pick the account type.

Kiosk Mode

Single-App: Runs one app fullscreen (e.g., Edge kiosk)
Multi-App: Allows multiple apps with custom Start menu
Restricted User: Desktop with limited apps, supports user groups

Example Configurations
These presets are starting points. Update names, URLs, and account details before exporting.
Start here
Pick your kiosk mode first. It controls which tabs and options show up.
Profile
Account

Step 2: Add allowed apps and configure auto-launch if needed.

Single-App Settings

Step 3: Add Start menu pins and optional shortcuts.

Start Menu Pins
Pins shape the on-device experience. Add a few so users can navigate quickly.
Why this matters: Start pins are shortcuts. If a .lnk does not exist on the device, run the Shortcut Creator after export.
DesktopAppLink pins reference .lnk files. If the shortcut doesn’t already exist on the device, you’ll need to run the Shortcut Creator script after exporting.
Assigned Access may ignore custom name/icon for Edge-backed shortcuts. Use Edge 'secondary tile' Start pins for site-specific names.
desktopAppLink (?)
Assigned Access may ignore custom name/icon for Edge-backed shortcuts. Use Edge 'secondary tile' Start pins for site-specific names.
Note: Provide the icon file on the target device. This tool creates shortcuts but does not supply icon files.
DesktopAppLink pins reference .lnk files. If the shortcut doesn’t already exist on the device, you’ll need to run the Shortcut Creator script after exporting.
Note: Secondary tiles use the normal Edge profile (not InPrivate by default). Apply Edge policies if you need private-session behavior.
No pins added yet

Step 4: Choose taskbar visibility and File Explorer restrictions.

Taskbar & File Explorer
Taskbar Layout (Optional)
Why this matters: Taskbar pins support packaged app IDs or .lnk shortcuts only.
Assigned Access may ignore custom name/icon for Edge-backed shortcuts. Use Edge 'secondary tile' Start pins for site-specific names.
desktopAppLink (?)
Assigned Access may ignore custom name/icon for Edge-backed shortcuts. Use Edge 'secondary tile' Start pins for site-specific names.
Note: Provide the icon file on the target device. This tool creates shortcuts but does not supply icon files.
No taskbar pins configured

Step 5: Review the summary and export your configuration.

Configuration Summary
Once the summary looks right, download the XML or helper scripts from the left sidebar.
Deployment tip: The XML output is used as the String value for the AssignedAccess OMA-URI in Intune. The PowerShell script applies the configuration on-demand to a local device.

XML Preview