How to Automatically Provision Win10 Autopilot Devices – Part 2


You have an autopilot demonstration environment running of Hyper-V. Considering the environment dynamics, you need to automate the VM provisioning. Manual approach is no longer feasible – “when you do something more than 2 times the same way, it is time to automate …”


  • Prepare a golden image you can use to clone new VM.
  • From the Hype-V host start VM provisioning, upload Autopilot data to Intune and invoke remote wipe of the new clone to prepare it for Autopilot OOBE experience

In this post you will prepare the Hyper-V host to control the Autopilot VM creation based on the golden image we created earlier


  • Configure AutoPilot profile assignment using a dynamic device group
  • Create the PS script
  • Run the automation …. wait ….. yeeeey! 😊

Let’s configure the deployment profile auto-assignment.

  • Open the Azure portal and login to your tenant
  • Go to Intune > Groups
  • Click new group
  • Set group type to Security
  • Group Name to AutoPilotDevices
  • Membership type is Dynamic Device
  • Open Dynamic Device membership blade click advanced rule

Enter the following rule to add all new devices to the group :

  •  Click Add Query
  • Create

Now, we have a group that will contain all devices we upload as autopilot devices. It is time to create and assign a profile

  • Go to Intune > Device enrollment -> Windows Enrollment – Deployment Profiles
  • Click Create profile
  • In the Create profile blade
  • Enter name – e.g  WinAutoPilotProfile
  • Deployment mode remains User-Driven
  • Set Join to Azure Ad as Azure AD joined
  • Click Out-of-box experience and set the following
  • Leave defaults for the 4 settings
  • Set computer template to WinAP-%RAND:3%. This is not necessary required for our demo but is fun 😊. When you enroll the device in Intune, the device will get a name based on template
  • Click Save then Create  

Now it is time to assign the profile to devices. As you remember, we created a device group that will dynamically contain all autopilot devoices

  • In the windows Autopilot deployment profiles blades
  • Select the newly created profile
  • Click on assignment
  • Click select groups to include
  • Click the group we created before
  • Click select then save

Note: before moving further copy the boot.vhdx file from the golden VM to the same location with the below script. In my example I used C:\VMs\boot-gold.vhdx

Note: before moving further with the script create the password files. As we don’t want to have passwords in clear text in our scripts load the following function in PS

Then execute it for the Intune Create-SecurePass for both local admin and Intune password as shown below. In my example I put the password files in the same location with the script C:\VMs\

When your done you should have 2 password files in c:\VMS

On the Hyper-V host, you will do create a PowerShell script that will do the following:

  • Import required modules
  • Create credentials for local admin on the VM clone
  • Create credentials for Intune
  • Create a new VM and copy the golden image disk to the new VM. Start the new VM
  • Keep trying to create a PS session with the new VM. Basically, the script keeps trying till the machine is fully booted and able to accept winrm PSSessions
  • When the PSSession is created the script runs the get-WindowsAutopilotInformation command and load the value in a variable ($d)
  • Add the device information to Intune using Add-AutoPilotImportedDevice cmd-let. Note that we pass order value set to “VMs”. You can use this filed for identification. Let’s say you create the clone for someone. You can put that person’s name in order  
  • intune Autopilot cmd-lets work asynchronously. This means we need to wait for the information to propagate. The script sleeps till the data is there
  • Wait for device information to get into Intune
  • Wait for the profile assignment
  • Finally, trigger the remote MDM wipe

Use the below script

Now let’s see the demo in action 😊

As seen below I ran the PS script to create a VM name Win10-APClient.

Then, the machine performs a wipe

After 20-40 minutes depending on your host power you will have the machine ready for Autopilot demo