🚀Autopilot DP - User Driven with Local Admin
📄 What this profile is about​
This profile is for assigned devices where the primary user must have local admin rights — test environments, functional admins, or specific engineering roles.
🛠️ Configuration Table​
| Setting | Value | Additional Info |
|---|---|---|
| Name | 🚀Autopilot DP - User Driven with Local Admin | For assigned devices that require local admin rights |
| Description | Grants admin rights during deployment | Used for roles that require elevated permissions by design |
| Convert all targeted devices to Autopilot | No | Only designated admin devices should land here |
| Deployment mode | User-Driven | |
| 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 | Administrator | |
| Allow pre-provisioned deployment | Yes | |
| 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​
❌ Excluded​
- (none)
💬 Real-world scenario​
Your engineering team needs admin rights to run scripts and install dev tools.
Instead of handing them a random admin account or creating exceptions on the fly, you give them a clean, fully documented Autopilot build that grants those rights from day one.
No surprises, no workarounds, no shadow IT.
🔗 Related​
- Explainer blog: 🚀 Autopilot – One Framework to Manage Them All