Windows Autopilot lets a small business ship a new laptop straight to an employee, who signs in with a work account and ends up with a fully configured, managed PC. It works well for organization-owned Windows devices, and it replaces most of the old routine of building and maintaining a master image. It only stays reliable when someone owns the licensing, the profiles, the security groups and the policies behind it, and that ongoing ownership is the real work for a 10 to 100 person company. We are a managed IT provider in West Bend serving Southeastern Wisconsin, and this guide covers what Autopilot does, what it requires, how to set it up and where it goes wrong.
TL;DR
- Autopilot uses the Windows installation already on the device and applies your settings, policies and apps over the internet. There is no custom image to build or maintain.
- It needs Microsoft Entra ID, an MDM such as Intune, a supported Windows version and the right licensing. Microsoft 365 Business Premium is one qualifying path.
- It is built for company-owned devices, not personal or BYOD machines.
- Most failed rollouts trace back to licensing, automatic enrollment, network access or profile assignment, not to Autopilot itself.
- Imaging still has a place for offline or urgent rebuilds, but for a connected, cloud-managed office Autopilot is the simpler default.
Table of Contents
- What Windows Autopilot is, in plain terms
- When Autopilot fits a small business
- What you need before you start
- How to set up Autopilot, step by step
- Autopilot vs. imaging
- Troubleshooting common failures
- What this means for Wisconsin manufacturers, law firms and dental practices
- Where a managed provider changes the equation
- Get a clear picture of your setup first
- FAQ
- Sources
What Windows Autopilot is, in plain terms
Autopilot is a cloud-based way to set up, preconfigure, reset and repurpose Windows devices with little infrastructure to manage. An MDM (mobile device management service, the system that pushes settings and apps to devices) does the configuring. For most small businesses that MDM is Microsoft Intune.
Traditionally, IT built a "golden image": a Windows install with apps, drivers and settings, then wiped each new PC and copied it on. Someone had to rebuild that image whenever Windows, drivers or apps changed. Autopilot skips the wipe. The device ships with the manufacturer's optimized Windows, and your organization's configuration is layered on at first sign-in.
The result for the employee: they unbox the laptop, connect to Wi-Fi, sign in with their work email and password, and wait while the device joins your Microsoft Entra ID tenant (your company's cloud directory of users and devices), enrolls in management and installs what you assigned. Nobody in IT touches the machine.
When Autopilot fits a small business
Autopilot is a good fit when:
- You buy company-owned Windows laptops and desktops, including for remote or hybrid staff. Microsoft's guide says manufacturers or partners can ship devices directly to remote users.
- You already use Microsoft 365 and want one place to manage devices and security settings.
- You replace or add machines regularly, so a hands-on build for each one adds up.
- You want every machine to look the same on day one: same encryption, same security baseline, same apps.
It is a poor fit for personal devices. Microsoft states Autopilot is intended for organization-owned Windows devices, not personal or BYOD machines. A device already managed by another MDM has to be unenrolled before Intune can fully manage it.
Shared devices are covered too. Microsoft's FAQ describes a self-deploying mode where powering on the device is all the user does, which suits kiosks or a shop-floor terminal where no individual user account is needed. For a manufacturer, that can mean a floor workstation that arrives, joins and configures itself.
What you need before you start
Most of the effort sits here, not in the Autopilot screens. According to Microsoft's requirements page, you need:
- A supported Windows version with internet access. Supported Windows 11 editions include Pro, Pro Education, Pro for Workstations, Enterprise, Education and Enterprise LTSC. Windows 11 IoT Enterprise is supported only for Teams Rooms devices.
- Microsoft Entra ID and an MDM. Intune is the usual choice.
- Licensing. Microsoft lists Microsoft 365 Business Premium, or Entra ID P1/P2 with Intune or another MDM, among the qualifying paths. User licenses must be assigned.
- Automatic MDM enrollment configured in Entra, so a device joining the directory enrolls without anyone clicking through.
- Permission to join devices. Where it applies, the first user needs permission to join devices to Entra ID.
- Network access. DNS must resolve internet names, and ports 80, 443 and UDP 123 must be reachable.
- Devices from a supplier that supports Autopilot. That means a manufacturer that supports the service, or a reseller or distributor in the Cloud Solution Partners program, per Microsoft's enrollment guide.
If you run Microsoft 365 already, you may hold most of this. Microsoft 365 Business Premium is part of our standard managed stack, and our Microsoft 365 cloud management work covers the tenant these devices join.
How to set up Autopilot, step by step
The sequence below follows Microsoft's documentation. At each step we note where small businesses tend to stumble.
Step 1: Prepare the tenant
Confirm licensing, then turn on automatic MDM enrollment in Microsoft Entra. Assign licenses to every user who will sign in on an Autopilot device.
Where it goes wrong: licenses assigned to the wrong people, or to nobody, are the most common reason a device reaches the sign-in screen and then fails to enroll. Fix the licensing before you buy hardware, not after.
A tenant is also only as safe as its sign-in rules. Enforcing multifactor authentication before you roll out devices means every new laptop starts in a protected environment. Our MFA setup guide for Microsoft 365 walks through it.
Step 2: Register the devices
A device must be known to Autopilot before it can be used. Microsoft's guide says an Autopilot administrator registers devices in the Intune admin center. When you order through a supported manufacturer or reseller, registration can be handled at the point of sale, so devices arrive already known to your tenant.
Where it goes wrong: ordering from a supplier that cannot register devices for you turns a zero-touch process into a manual one. Settle this in the purchase order.
Step 3: Create groups and a deployment profile
The deployment profile decides how the first-run experience behaves: what screens the user sees, whether they get local admin rights, and how the device joins. Per Microsoft, you create the profile and assign it to Microsoft Entra security groups, then configure the out-of-box experience and startup behavior. Intune can automate profile assignment, which keeps a growing fleet from becoming a spreadsheet exercise.
Where it goes wrong: a device that is registered but not in a group with a profile assigned will boot into ordinary Windows setup. Check group membership first when a laptop behaves as if Autopilot does not exist. Standard users without admin rights is the safer default for most offices.
Step 4: Assign apps, policies and security settings
This is where "configured" becomes "ready to work." Assign your line-of-business apps, Microsoft 365 apps, endpoint protection, update rules and encryption. Disk encryption belongs here: our guide to BitLocker for small business covers policy and recovery keys, which matter a great deal if a laptop is lost.
Where it goes wrong: every app you require during setup lengthens the wait and adds a way for the process to fail. Require only what a person needs to start working, and deliver the rest after sign-in.
Step 5: Run a pilot, then roll out
Test with one device and one real user before ordering ten. Walk through the full first-run on the same kind of network the employee will use, which for remote staff is a home connection, not your office.
Where it goes wrong: pilots done only in the office miss firewall and filtering problems that appear elsewhere.
Step 6: Hand it to the user
The employee powers on, connects to a network and signs in. Per Microsoft, when the user signs in with an organization account, the device enrolls automatically, with no wipe or custom OS image. Updates may also run during setup. Petri reported that Microsoft planned a policy letting admins control cumulative updates during the out-of-box experience, with critical updates still automatic and an average update process of about 20 minutes, depending on download size, network and hardware. Tell new hires to expect a wait.
Autopilot vs. imaging
Imaging means maintaining a master build and copying it to each device. Autopilot means configuring the manufacturer's Windows through cloud policy. The practical differences:
| Autopilot | Imaging | |
|---|---|---|
| Build effort | No custom image or driver set to maintain | Image and drivers rebuilt as Windows and apps change |
| Where devices start | Manufacturer's optimized Windows | Wiped and rewritten |
| Shipping to remote staff | Device can go directly from supplier to user | Usually passes through IT first |
| Dependency | Needs internet and cloud services | Can work offline |
| Ongoing control | Policies and apps managed centrally in Intune | Baseline fixed at the time the image was made |
Microsoft says Autopilot avoids maintaining custom images and drivers by transforming the preinstalled Windows through settings, policies and apps. Its comparison page also notes that the newer Autopilot device preparation option is positioned around faster, more consistent provisioning and near-real-time monitoring, while classic Autopilot supports more device types and customization options. Picking between the two is a decision to make with your actual hardware in mind.
For a connected office on Microsoft 365, Autopilot wins on effort and consistency. Imaging keeps one advantage: it can rebuild a machine with no network. That matters for a plant floor with restricted connectivity, so a rare offline rebuild is worth planning for. Whichever route you use, keeping Windows updates and drivers current after the first sign-in is what keeps a standard build standard.
Troubleshooting common failures
Microsoft's own checklist is a good first pass when a device stalls. Work through it in this order:
- Windows version. Is it a supported edition and channel?
- Network. Does DNS resolve, and are ports 80, 443 and UDP 123 open? Microsoft's requirements page lists these.
- Automatic MDM enrollment. Is it configured in Entra?
- Licensing. Does the signing-in user hold the right license?
- Join permissions. Is the user allowed to join devices where that applies?
- Registration and profile. Is the device registered, in the right group, with a profile assigned?
If all of that checks out, look at Microsoft's known issues list, which documents problems the vendor already recognizes. Its deployment report measures how long a device takes from enrollment through the Account setup phase of the Enrollment Status Page, which helps you spot slow rollouts. One Microsoft Q&A thread describes devices stuck on "Identifying" while applying a security policy, with a recommendation to collect Autopilot MDM logs to investigate.
Notice the pattern: almost everything on that list is about the environment around the device. That is why Autopilot rewards businesses with someone watching the tenant continuously, rather than someone called only after a laptop sticks.
What this means for Wisconsin manufacturers, law firms and dental practices
The same technology serves different priorities.
- Manufacturers care about downtime and security. A new workstation that comes up with the right policies and encryption removes a day of hand-building, and self-deploying mode suits shared floor devices. Offline recovery deserves a written plan.
- Law firms and financial firms need documentation. Standardized, policy-driven devices make it easier to show that every machine met the same baseline.
- Dental practices run a mix of front-desk and clinical workstations. Consistent configuration and encryption on every device reduces the number of one-off machines that someone has to remember.
In each case the benefit comes from the standard being enforced continuously, not from the first-run experience alone.
Where a managed provider changes the equation
The screens in Intune are not hard. The difficulty is that profiles, groups, licenses, app assignments and security policies all need an owner after launch. Windows changes, staff come and go, and one forgotten license leaves a new hire staring at a stalled setup on their first morning.
That is the problem our model is built around. Collett Systems provides managed IT for small and mid-sized businesses at a fixed cost per user, with 24/7 monitoring, proactive support, full infrastructure management and unlimited help desk. The same fixed-price, fully loaded stack goes to every client, and Microsoft 365 Business Premium is part of it. When device setup is part of an ongoing arrangement rather than a project, there are no hourly surprises when you hire three people in a month. For firms that already have an internal IT person, our co-managed IT services share the load.
Our perspective
Most small businesses we meet do not have an Autopilot problem. They have an ownership problem. The first rollout goes fine, then nobody is responsible for the licensing, the groups or the policy changes that follow, and six months later a new laptop will not finish setting up.
We treat IT as infrastructure, not as a pile of tickets. That is why we price per user, with one standardized stack for everyone, rather than tiers or hourly work. A device that enrolls cleanly, encrypts itself, and checks in with monitoring from day one is what a fixed-cost, proactive model is meant to produce.
If you are a manufacturer, a law firm or a dental practice in Wisconsin, the question to ask is not whether Autopilot can be configured. It is who is accountable when it stops working at 7:45 on a Monday. Our answer is a local team with defined service levels, and over 150 local organizations already rely on us for that.
Dustin Collett
Get a clear picture of your setup first
Before buying devices or changing how you provision them, we recommend starting with an honest look at your tenant, licensing, security settings and device inventory. Our IT & Security Assessment does that and gives you a documented starting point. If you want to talk about ongoing device management as part of a fixed per-user plan, start with our managed IT services, or book the IT & Security Assessment.
For a quick first read on your exposure, the free IT Risk Score takes about a minute.
FAQ
Does Windows Autopilot cost extra?
Autopilot itself is a Windows capability, but you need the licensing and management service around it. Microsoft lists Microsoft 365 Business Premium or Entra ID P1/P2 with Intune among the qualifying paths. Many small businesses already hold one of these for email and security. Check your assigned user licenses before you plan a rollout.
Can I use Autopilot on personal or employee-owned laptops?
No. Microsoft says Autopilot is intended for organization-owned devices, not personal or BYOD machines. Buy company devices from a supplier that supports Autopilot, and keep personal devices on a separate policy.
Does Autopilot wipe the device or install an image?
No. Autopilot uses the factory-installed Windows client and does not require wiping the device or applying a custom image. Your settings, policies and apps are applied on top when the user first signs in.
How long does first-time setup take?
It depends on the apps you require, the network and the hardware. Petri reported an average update process of about 20 minutes during setup, dependent on download size, network and hardware. Keeping required apps to the essentials shortens the wait.
What should I check first if a device gets stuck?
Start with the basics: a supported Windows version, DNS and open ports 80, 443 and UDP 123, automatic MDM enrollment, user licensing, device registration and profile assignment. Microsoft's requirements page lists each one. If the checks pass, review the known issues list and collect Autopilot MDM logs.
Sources
- Overview of Windows Autopilot, Microsoft Learn
- Windows Autopilot requirements, Microsoft Learn
- Windows Autopilot FAQ, Microsoft Learn
- Windows Device Enrollment Guide for Microsoft Intune
- Compare Windows Autopilot device preparation and Windows Autopilot, Microsoft Learn
- Windows Autopilot known issues, Microsoft Learn
- Autopilot issue on device set up "Identifying", Microsoft Q&A
- New Policy to Let IT Admins Manage Windows 11 Updates, Petri
