Timezone not honored from OOBE after Intune Wipe
When on-boarding a device with Windows Autopilot, the region selected (e.g New Zealand) in the OOBE is honored as the time zone for the device. If the device is then wiped in Intune, the region selected in the OOBE on the subsequent Autopilot on-boarding is ignored and the time zone is set to the default for Windows, Pacific Standard Time. A work around such as a PowerShell script to set the timezone or using a CSP can be used, but become complex in a multi time zone environment and can cause problems with the Autopilot Enrollment Status Page timing out in the device setup stage if the PowerShell script/CSP is not implemented in the user context.
Mark Szili commented
I really think autopilot needs to take all the best bits from the Config Manager build and capture task sequences to square away all these things in a hurry.
We don't need to reinvent the wheel here just put some racing slicks on the Autopilot car for the drag race that Config Manager is still winning every race for OSD championship cup.