Event banner
Event details
Ever since the Return of key functionality for Windows Autopilot sign-in and deployment experience was announced on July 27, 2022, we are still not able to have the UPN pre-populate on the Azure sign in page. I opened a case three weeks ago to address this and no progress is being made. Please provide clarification on this functionality. I am not sure why this is based on the OEM. We are assigning users ourselves.
Also, is there a way to know if a device was automatically re-enrolled after replacing hardware components?
- Please believe me 🙂 as mvp guy… its based on the hardwAre suppliers (oem) … as a recommended advice… please advise them to get in contact with microsoft
- In our last monthly sync with Lenovo, they basically said they are still trying to understand what they need to do on their end. I understand the OEM dependence on the re-enrollment process after hardware change, but what does OEM have to do with pre-populating UPN on Azure sign-in page during Autopilot setup? OEM is only uploading hashes for our devices. We manually assign to user when we deploy the laptop.
- Cristina_Osorio
Microsoft
Hi Michael, other than the Windows version requirement listed here: https://techcommunity.microsoft.com/t5/intune-customer-success/return-of-key-functionality-for-windows-autopilot-sign-in-and/ba-p/3583130, you will need to check with your OEM to get confirmation they support the automatic re-enroll of pre-provision or self-deployed devices as well as the UPN pre-prepolation.
