Event banner
Event details
For reference, https://learn.microsoft.com/en-us/mem/configmgr/comanage/how-to-prepare-win10#windows-autopilot. (see the Note) and it explains that the limitation is due to the identity change of the device during hybrid AAD-join.
I'd love to see a solution (we already have a workaround) to this. Hybrid AAD join isn't going away anytime soon.
Herman_Arnedo_Byrne
Microsoft
MicrosoftHi Adam / Chad,
We strongly discourage any customer from building their modern provisioning plan on Hybrid Azure AD Join. At best you’re deferring a problem you’ll still have to solve and won’t necessarily get any easier with time. At worst you’ll end up investing lots of time and effort to try and solve a complex problem and gain very little benefit over the current solution you have today that work well and reliably.
1. The HAADJ flow during Autopilot is one we’re seeing customers see issues and lots of unnecessary complexity.
2. HAADJ is really intended to uplift a customer’s existing domain join devices.
3. AAD is the Microsoft recommended path for most new or repurposed devices, especially when using modern deployment tools like Windows Autopilot
I would like to know more about your blockers. Please, feel free to reach out to me via private message