Home › Knowledgebase › KB-1133

Simplify New Hire Setup: Using Microsoft Autopilot and Intune for Instant Employee Onboarding

Summary

This guide helps you troubleshoot and resolve: Simplify New Hire Setup: Using Microsoft Autopilot and Intune for Instant Employee Onboarding. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

Simplify New Hire Setup: Using Microsoft Autopilot and Intune for Instant Employee Onboarding

Setting up a new laptop for a new hire often involves hours of manual configuration, software installation, and security hardening. With Microsoft Intune and Windows Autopilot, small business owners can automate this entire process. Instead of preparing devices on-site, new employees can simply open a sealed laptop, log in with their corporate credentials, and find their work environment already configured and secured.

This guide is written for Australian small businesses purchasing devices from local vendors or resellers. It assumes your tenant data resides in Australian Microsoft datacentres where available.

Prerequisites

Before beginning, ensure your environment meets the following requirements:

  • Licensing: Each user requires a licence that includes Microsoft Intune and Microsoft Entra ID (formerly Azure AD) Premium P1 or P2. Microsoft 365 Business Premium typically satisfies this requirement for small businesses.
  • Join type: Devices must support Microsoft Entra Join or Hybrid Microsoft Entra Join. Standalone workgroup devices without cloud identity integration cannot complete Autopilot enrollment.
  • Intune enrollment: Automatic MDM enrollment must be enabled in the Microsoft Intune admin centre for the relevant user or device groups.
  • User accounts: The new employee’s user account must be created in Microsoft 365 or Microsoft Entra ID before the device is first powered on.
  • Internet connectivity: The device must connect to the internet during the Windows Out-of-Box Experience (OOBE) to contact Autopilot and Intune services.
Important: Obtain the hardware hash CSV file from your Australian vendor or reseller before shipping the sealed device to the employee. Without the hardware hash imported into Intune, Autopilot will not recognise the device.
Important: Create the employee’s user account in Microsoft 365 before they attempt to log in. Autopilot cannot enroll a device for a user who does not exist in your tenant.

Detailed Instructions

1. Assign Licences to Users

  1. Log in to the Microsoft 365 admin centre.
  2. Navigate to Users > Active users.
  3. Select the new employee’s user account.
  4. Under the Licences and apps tab, ensure Microsoft Intune and Microsoft Entra ID Premium are enabled.
  5. Click Save changes.

2. Create an Autopilot Deployment Profile

  1. Log in to the Microsoft Intune admin centre.
  2. Navigate to Devices > Windows > Windows enrolment > Deployment profiles.
  3. Click Create profile and select Windows Autopilot.
  4. Choose the deployment mode:
    • User-driven mode: The employee signs in with their corporate credentials during setup. Suitable for most small business onboarding.
    • Self-deploying mode: The device enrolls without user interaction. Requires additional Entra ID configuration and is typically used for shared or kiosk devices.
  5. Configure settings such as language, region (set to English (Australia) where applicable), and user account type.
  6. Assign the profile to a group, such as All New Hires or Autopilot Devices.
  7. Click Create.

3. Configure the Enrollment Status Page (ESP)

  1. In the Intune admin centre, navigate to Devices > Windows > Windows enrolment > Enrollment status page.
  2. Click Create.
  3. Configure the page to show installation progress for apps, profiles, and certificates during Autopilot enrollment.
  4. Set options to block device use until all required apps and profiles are installed, if desired.
  5. Assign the ESP to the same user or device group as your Autopilot deployment profile.
  6. Click Create.

The ESP gives the new employee visibility into setup progress instead of a blank or frozen screen during enrollment.

4. Register Devices for Autopilot

  1. Obtain the hardware hash CSV file from your device vendor or Australian reseller.
  2. In the Intune admin centre, go to Devices > Windows > Windows enrolment > Devices.
  3. Click Import and upload the CSV file containing the hardware hashes.
  4. Once imported, the devices appear in your Autopilot device list and are linked to your deployment profile.

5. Create Configuration Profiles

  1. In the Intune admin centre, navigate to Devices > Configuration profiles.
  2. Click Create profile.
  3. Select Windows 10 and later as the platform and Settings catalog as the profile type.
  4. Configure required settings, such as security baselines, bitlocker encryption, and browser restrictions.
  5. To deploy Wi-Fi settings, use the Settings catalog to add shared key or certificate-based Wi-Fi profiles. Avoid embedding plain-text Wi-Fi passwords where possible; use certificates for stronger security.
  6. Assign the profile to the All New Hires group.
  7. Click Create.

6. Assign Applications

  1. Navigate to Apps > All apps > Add.
  2. Select the application type (e.g., Microsoft Store app or Win32 app).
  3. For Win32 applications, use the Intune Win32 content prep tool to prepare the application files into a .intunewin package before uploading.
  4. Upload the application package and configure the installation settings.
  5. Assign the app as Required for the target user or device group.

7. The Employee Onboarding Experience

  1. Ship the sealed device directly to the new employee’s home or office.
  2. The employee powers on the device and connects to a Wi-Fi network during OOBE. An internet connection is mandatory for Autopilot to contact Intune.
  3. They enter their corporate email address and password.
  4. Windows Autopilot detects the registered device, applies the assigned deployment profile, and enrolls the device in Intune.
  5. The Enrollment Status Page displays progress while profiles and required applications install.
  6. Once complete, the user is logged into a fully configured desktop ready for work.

Troubleshooting Common Autopilot Issues

Device not recognised in Autopilot

  • Confirm the hardware hash CSV was imported successfully into the Intune admin centre.
  • Verify the device serial number appears in the Autopilot device list before shipping.
  • Ensure the device is connected to the internet during OOBE.

Licence not assigned

  • Check that the user has an active Microsoft Intune and Microsoft Entra ID Premium P1 or P2 licence in the Microsoft 365 admin centre.
  • If the licence was assigned recently, wait several minutes and restart the enrollment process.

Network blocking Intune endpoints

  • Ensure the network allows traffic to required Microsoft Intune and Autopilot endpoints.
  • If the employee is behind a strict firewall or corporate proxy, test connectivity from another device on the same network.

Autopilot profile not applying

  • Confirm the deployment profile is assigned to the correct user or device group.
  • Verify the device hardware hash is linked to the profile in Intune.
  • Check that the Enrollment Status Page is assigned to the same group and is not blocking completion due to missing app installations.

MFA prompts during OOBE

  • Ensure the user has their multi-factor authentication method available before starting setup.
  • Review Conditional Access policies in the Microsoft Entra admin centre, as these may require MFA during device registration.
  • App passwords are not used for Windows Autopilot enrollment; the user must complete interactive MFA with their registered method.

Tip: Always test your Autopilot deployment with a single device before rolling it out to all new hires to ensure your configuration profiles and Enrollment Status Page are correct.

If you encounter issues during setup or need assistance configuring your tenant, Open a Ticket with the 220 Internet Services support team.

Still Having Issues?

Need more help? If the issue persists after trying these steps, please open a support ticket and our team will assist you.

💻 Open a Ticket