Windows Autopilot and Intune Basics: Zero-Touch Laptop Setup for SMBs
A new laptop arrives at a staff member's desk and enrols itself. That's Autopilot. Here's how it actually works and what's involved in setting it up.
Setting up a laptop for a new staff member used to mean a few hours of tech time — unbox, install Windows updates, join to the domain, install Office, install line-of-business apps, configure VPN, apply security policy, ship the device to the user, hope you didn’t miss anything.
Windows Autopilot, combined with Microsoft Intune, replaces that whole process with a workflow where the laptop ships directly from the supplier to the staff member, and sets itself up the first time they sign in. No IT touch, no SOE imaging, no domain join.
Here’s what’s actually involved.
What Autopilot does
Autopilot is a Microsoft cloud service that preconfigures new Windows 11 devices for your business. When a staff member turns the laptop on and signs in with their work email:
- Autopilot recognises the device and associates it with your company’s tenant
- The device automatically joins Entra ID (formerly Azure AD)
- It enrols in Intune (or your chosen MDM)
- Intune applies your security policies, compliance rules, and configuration
- Required apps are installed (Office 365, line-of-business apps, etc.)
- The staff member is dropped on the desktop ready to work
Total time: typically 20-40 minutes depending on download speed and app size. No tech needs to touch the device.
What Intune does
Intune is Microsoft’s Mobile Device Management platform — it’s the thing that tells your devices what to do. Once devices are enrolled, Intune continuously:
- Enforces security policy. Disk encryption, firewall, antivirus, password requirements, auto-lock, USB restrictions.
- Manages applications. Installs required apps, updates them, and removes them when staff leave.
- Enforces compliance. Flags devices that are missing patches, have antivirus disabled, or are running out-of-date OS versions.
- Reports fleet status. A dashboard showing which devices are compliant, patched, and healthy.
- Enables Conditional Access. Integrates with Entra ID so non-compliant devices are blocked from accessing company resources.
Intune is part of Microsoft 365 Business Premium and the E3/E5 enterprise SKUs — most businesses already have the licence and just aren’t using it.
The setup process
Rolling out Autopilot for a business fleet isn’t a long project, but it has several steps that need to happen in order.
1. Tenant prep
- Set up Microsoft 365 tenant (if not already)
- Configure Entra ID for device registration
- Licence staff with at least Business Premium / E3
- Set up Intune and define the baseline security profile
2. Device identity registration
Every Autopilot-managed device needs a hardware hash registered in your tenant. There are two ways this happens:
- Supplier does it at purchase. Large resellers (and CDW, Dicker Data, Ingram, Synnex) can register devices to your tenant as part of the order. This is the smooth path for new orders going forward.
- You do it for existing devices. A PowerShell script captures the hardware hash; you upload it to Intune. More fiddly but works for devices already on hand.
3. Group design
Devices get assigned to Autopilot deployment profiles based on Entra ID groups. A typical setup has:
- A default profile for general knowledge worker laptops
- A separate profile for executives or specific roles with different apps
- A profile for BYOD or kiosk devices if needed
4. App packaging
Every app your staff need — Office, Teams, Adobe, line-of-business apps, VPN clients — gets packaged in Intune for silent install. Microsoft Store apps are easy; traditional MSI/EXE installers take more work.
For many SMBs, this is the part of the project that takes the most effort. The payoff is that every device from then on gets set up identically.
5. Security baseline
Intune ships with a Microsoft-recommended security baseline. Most businesses customise this to suit their risk profile:
- BitLocker encryption enforcement
- Local admin password rotation
- Defender policies
- Firewall and network protection
- Password complexity and account lockout
- Attack Surface Reduction rules
6. Pilot
A small group of devices (5-10) across different roles go through the full Autopilot experience. Every app is tested, every policy is validated. Adjustments are made before the wider rollout.
7. Rollout
Going forward, new devices ship direct from the supplier to the staff member. For existing devices, a wipe + Autopilot re-enrolment gives them the same treatment.
Day-to-day benefits
Once Autopilot and Intune are in place, day-to-day benefits accrue:
Staff onboarding is faster. A new hire starts on Monday; their laptop ships directly to their home address Friday; they sign in and it sets itself up. No manual provisioning.
Staff offboarding is cleaner. HR kicks off departure; Intune remote-wipes the device; the hardware is ready to reissue or dispose of.
Lost devices are controllable. A lost or stolen laptop can be locked or wiped remotely.
Compliance visibility is real. You know exactly which devices are patched, encrypted, and protected — and which aren’t.
The fleet stays current. Policy and app changes propagate automatically to every device.
Common SMB concerns
“Our devices are older and not Autopilot-friendly.” Devices from the last 5 years with TPM 2.0 generally work fine. Windows 10 devices after October 2025 shouldn’t be in the fleet anyway.
“We use a line-of-business app that won’t package cleanly.” Most things can be packaged with some work. Some legacy apps genuinely don’t cope. Those are usually candidates for replacement anyway, but Intune can run a manual install script as a last resort.
“We don’t have Intune licensing.” Business Premium includes it. E3 and E5 include it. Business Basic does not. If you’re on Basic, the licensing uplift is worth the capability.
“We still have a domain.” Intune and on-prem Active Directory can coexist. Hybrid join is a supported path for businesses that aren’t ready to go cloud-only.
The bottom line
Autopilot + Intune is genuinely transformative for Australian SMBs. It removes a big chunk of manual IT work, improves security posture, and makes the whole fleet manageable from one console.
The initial setup takes effort — typically 3-6 weeks for a well-run project — but the benefit compounds. Every new device after that is zero-touch.
If you’re still manually provisioning laptops, or you’ve got Intune licensed but not set up, get in touch. We can scope a realistic project, handle the app packaging and policy work, and hand over a fleet that manages itself.
