Forum Discussion
Deploying new PCs through Autopilot (Hybrid joined)
Hi,
I have seen an article from Microsoft that they don't recommend deploying new PCs through autopilot as it may not get some of the latest features. So they asked to do and local AD join first and then register in Azure / intune etc...
Can someone list exactly the features that we will lose if we deploy new PCs through Autopilot (Windows 11 ) devices.
We deployed new PCs and works well so far but wanting to know the features that we will lose.
2 Replies
Hy,
The Hybrid Joined it should be used more like a transition, but i have managed a lot of customers that are still using this as a stable environment with a Higher complexity volume due to dual environment.
So, Microsoft recommends deploying new devices as cloud-native Entra ID joined devices rather than Hybrid Join, especially when using Autopilot because you do have some benefits regarding management, troubleshooting and user experience.
- Better user experience with seamless internet-based authentication
- Reduced infrastructure dependencies and complexity
- Access to evolving cloud security and deployment features
I am not aware of loosing any features with Entra Hybrid Join Devices.
Good luck!
I am taking you meant that the recommendation from MS is not to deploy new devices as Entra Hybrid using Autopilot. If that is what you meant, then the recommendation is correct. The recommendation also goes on to say that, new devices should be provisioned as Entra ID only. I honestly don’t know if you miss out any features if you do hybrid join using Autopilot, but this shouldn’t be a desired configuration any way.
