Windows Autopilot is a Microsoft tool that allows companies to achieve Zero Touch Provisioning for Windows devices. Groups seeking to move beyond device imaging need to configure and implement Windows Autopilot.
Notably, Windows Autopilot and Microsoft Intune reduce device provisioning time by 90% over legacy device imaging. Autopilot is a fantastic tool when also considering lifecycle management and accompanying components of resetting, repurposing, and recovering of devices. However, as with most software programs from Microsoft, many have questions about its capabilities, limitations and customizations. Many questions begin with simply setting up Autopilot for success. To make the process clear, we’ve categorized Autopilot setup into the three steps below.
1. Establishing a scope for your environment
Here, you can examine your current configurations to establish a roadmap for which end-users can be automatically enrolled into Intune. Once you’ve formalized your enrollment scope, you can move on to the next step of your Autopilot journey.
2. Launch an Enrollment Status Page
An enrollment status page, also known as an ESP, will allow your team to view the configuration process of devices. Additionally, your ESP will determine what a user sees when they access their device.
3. Start a Deployment Profile
Deployment profiles are typically determined by a user’s role within a company. Autopilot consumes the deployment profile and then sends instructions to the device to configure it accordingly. Autopilot allows IT administrators to create up to 350 unique profiles in the system.
Solutions to Common Autopilot Questions
If you are already on your Autopilot journey, you may have some questions about functionality, capabilities, and customizations. You’re not alone. We often hear many of the same questions from admins seeking solutions with Autopilot. Check out our commonly heard inquiries here.