Windows deployment with the next generation of Windows Autopilot
Device deployment: read, write, repeat
For years the process of provisioning a new laptop or PC for a corporate end user was labor intensive. It required physical space for you to house devices and infrastructure to build and maintain device images.
Since its introduction in 2017, Windows Autopilot has revolutionized device deployment, introducing a direct-to-user, zero-touch experience. As Hervé Janmot, Deputy Global Head of Digital Workplace Architecture, Security, and Transformation at Société Générale put it:
“It’s a game-changer for the employee experience and a powerful productivity tool for our team and the employees we serve.”
Changing the game again
Today, we’re excited to announce the first of many exciting releases on the journey to the next generation experience of Windows Autopilot: device preparation.
We based this new capability on re-engineered architecture that will allow us to accommodate more devices, deliver more efficient results, and allow provisioning of cloud instances like Windows 365 and Azure Virtual Desktops. This new foundation will also expand our service to government cloud customers for the first time.
To keep delivering Windows Autopilot to existing users without disruption, this next iteration was built alongside the current Windows Autopilot technology. The features you know and love in Windows Autopilot aren’t going anywhere! We’re offering the reliability of it and innovations of device preparation in tandem until the experience can be totally unified with the new, more capable architecture.
For those ready to use Windows Autopilot device preparation, you’ll find the entire deployment experience streamlined. As you’ll see, profiles are now configured from a single screen:
Adding devices to groups is simpler and faster. We’ve replaced dynamic grouping with enrollment time grouping, so devices get assigned apps policies and scripts more efficiently.
Reporting is much more detailed and is available in near-real time.
Reports also offer more granular detail and facilitate troubleshooting with links to devices, policies, and even scripts that impact failed deployments.
Admins can define apps to be installed during the out-of-box experience (OOBE). For example, admins can make sure that Microsoft Defender is installed before users can get to work while specifying that other less critical apps are installed in the background. This allows users to be productive once their device is more secure. For more details, find them in the release announcement.
End users will get a re-designed OOBE with clearer indications of how close the setup process is to completion and more resilient recovery options that help them resolve issues without calling the Help Desk.
See what’s to come
We’re eager to share some of the capabilities coming to the new Windows Autopilot device preparation experience! We’ll update you with release dates soon of the following features:
Customize OOBE and rename devices during provisioning based on organizational structure.
Self-deploying and pre-provisioning mode.
Additional admin-specified configurations delivered before allowing desktop access.
Enhanced optional desktop onboarding experience inside the Windows Company Portal app.
The ability to associate a device with a tenant.
Help shape the future
While there’s a lot more still in development already, you can influence what’s next for Windows Autopilot by working with the technology and giving your feedback and suggestions to our team. Let us know how you use and how you wish you could use Windows Autopilot. Add your comments and requests to this blog post or upvote an existing comment to vote for it. Our product teams are passionate about building products that meet real-world needs.
Stay up to date! Bookmark the Microsoft Intune Blog and follow us on LinkedIn or @MSIntune on X to continue the conversation.
Microsoft Tech Community – Latest Blogs –Read More