🚀Autopilot DP - Self Deploy
📄 What this profile is about​
This profile is designed for always-on and multi-user devices — think kiosks, reception PCs, and shared meeting room machines.
They must be ready to go without any user input at OOBE, and stay locked down so the next person gets the same experience every time.
🛠️ Configuration Table​
| Setting | Value | Additional Info |
|---|---|---|
| Name | 🚀Autopilot DP - Self Deploy | For always-on and multi-user devices (Kiosk/Shared) |
| Description | Zero user input at OOBE, locked-down and ready to go | Prevents manual config mistakes |
| Convert all targeted devices to Autopilot | No | Already tagged and known; no need to auto-convert |
| Deployment mode | Self-Deploying | |
| Join to Microsoft Entra ID as | Microsoft Entra joined | |
| Language (Region) | Operating system default | |
| Automatically configure keyboard | Yes | |
| Microsoft Software License Terms | Hide | |
| Privacy settings | Hide | |
| Hide change account options | Hide | |
| User account type | Standard | |
| Allow pre-provisioned deployment | No | |
| Apply device name template | Yes | |
| Name template | %SERIAL% | Can be dynamically adjusted per customer using a SuperVision tag (e.g., prefix like ABC-%SERIAL%). See docs.supervision.nl for details. |
👥 Group Assignments​
✅ Included​
- 🛡️🪟💻⛓️Group - Autopilot Devices - Kiosk
- 🛡️🪟💻⛓️Group - Autopilot Devices - Shared
❌ Excluded​
- (none)
💬 Real-world scenario​
Your reception kiosk gets reset overnight.
You walk in, turn it on, and instead of being asked for an account or MFA, it boots straight into the kiosk app.
No login drama, no “last user left their Teams open” moments — just instant, predictable readiness for the next person.
This is why Self Deploy exists: to keep shared devices simple, consistent, and hassle-free.
🔗 Related​
- Explainer blog: 🚀 Autopilot – One Framework to Manage Them All