Microsoft Autopilot and Prowise OPS

This document describes the setup needed for Microsoft Autopilot to automatically deploy Prowise OPS modules to Intune.

Following the Microsoft guide on: https://docs.microsoft.com/en-us/microsoft-365/admin/devices/add-autopilot-devices-and-profile?view=o365-worldwide

and 

https://docs.microsoft.com/en-us/windows/deployment/windows-autopilot/demonstrate-deployment-on-vm

Prepare autopilot by creating a Windows Autopilot deployment profile in endpoint.microsoft.com.

2021-10-25_08_16_32-Windows_Autopilot_deployment_profiles_-_Microsoft_Endpoint_Manager_admin_center.jpg

Assign the deployment profile to a group:

2021-10-25_08_17_40-Edit_profile_-_Microsoft_Endpoint_Manager_admin_center.jpg

From the OPS modules that are going to be used for Autopilot and Intune, the following powershell scripts need to be executed: 

  • Install-Script -Name Get-WindowsAutoPilotInfo
  • mkdir “c:\temp”
  • Get-WindowsAutoPilotInfo -OutputFile “c:\temp\output.csv”

(The output for multiple OPS modules can be combined into 1 CSV file.)

import devices in autopilot with the generated csv file.

2021-10-25_08_24_12-Add_Autopilot_devices_-_Microsoft_Endpoint_Manager_admin_center.jpg

Add the imported PC to the autopilot deployment group

2021-10-25_08_21_50-autopilot_-_Microsoft_Endpoint_Manager_admin_center.jpg

Wait until the autopilot profile has been updated to Assigned for the autopilot device

2021-10-25_08_22_58-Windows_Autopilot_devices_-_Microsoft_Endpoint_Manager_admin_center.jpg

When resetting a pc, autopilot will now be active. 

After login to Azure on the pc, the pc will get registered in Azure and Intune (if the deployment policy is set to Azure AD)

2021-10-25_08_23_50-Windows_-_Microsoft_Endpoint_Manager_admin_center.jpg

Remark: user needs to have an intune license in admin.microsoft.com to be able to use autopilot and Intune.