Home / Companies / Fleet / Blog / Post Details
Content Deep Dive

Autopilot without Autopilot: zero-touch Windows deployment with Fleet

Blog post from Fleet

Post Details
Company
Date Published
Author
Allen Houchins
Word Count
1,265
Company Posts That Month
5
Language
-
Hacker News Points
-
Post removed?
No
Summary

Windows provisioning packages can provide an alternative to Microsoft Autopilot for enrolling new Windows Pro, Enterprise, or Education devices in Fleet before end users reach the desktop. Built with Windows Configuration Designer and applied from a USB drive during initial setup, these packages install Fleet’s agent, allowing devices to enroll once online and later receive Windows MDM policies, disk encryption settings, and updates. The approach avoids Autopilot’s hardware-registration requirements and may eliminate the need for Microsoft Entra ID P1 licenses, which are required for Autopilot or Entra automatic enrollment unless already included in subscriptions such as Microsoft 365 E3 or E5. Resellers, OEMs, or internal IT staff can apply packages before shipping devices, although the process still requires someone to physically handle each device. Key limitations include no Entra ID device join, MDM configuration activation only after the user’s first sign-in, lack of identity verification during enrollment, the need to protect and rotate the package’s enrollment secret, and no MDM support for Windows Home editions.

Trends Found in this Post

No tracked trend matches for this post yet.

Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.