Autopilot OOBE Wi-Fi Profiles

Hi Siti,

You can't reliably pre-stage a corporate Wi-Fi profile into a standard Windows Autopilot deployment before the device has enrolled, because the device must first obtain internet connectivity in OOBE in order to receive Intune policies, including Wi-Fi profiles. Microsoft's supported process is for the user to connect to Wi-Fi during the initial out-of-box experience, after which Autopilot can download its configuration and Intune can deploy the corporate wireless profile.

If these are Microsoft Entra-joined Autopilot devices, the recommended approach is to provide users with the corporate SSID and credentials (or certificate onboarding process) so they can connect during OOBE. Once enrollment completes, the managed Wi-Fi profile will be automatically installed and maintained by Intune.

If you need a true zero-touch experience, consider having the OEM or staging partner perform Autopilot pre-provisioning while connected to a network beforehand, or use a provisioning package (PPKG) that contains the Wi-Fi profile. A PPKG can inject wireless settings before enrollment, but it adds operational overhead and is generally used for specific deployment scenarios rather than standard cloud-native Autopilot deployments.

For a brand-new office with only Wi-Fi available, the most practical and fully supported solution is usually to have users join the corporate wireless network during OOBE. Windows Autopilot fully supports starting deployment over Wi-Fi, although the user must select region, keyboard, and connect to the wireless network before provisioning can begin.

This article includes the above information, you might want to go thru it: https://learn.microsoft.com/en-us/autopilot/pre-provision

Harry.