AutoPilot Vs Hybrid Vs ???

[CyBeRkId2002]

Am I right in thinking there is a big difference in a way users authenticate on to a laptop in an AutoPilot (pure Azure) device Vs Hybrid joined device (enrolling via SCCM co-management if that makes a difference).

 

My understanding is the hybrid device authenticates against our AD and it would not be possible to log-on as a cloud user off-site on the device (although should get most of the benefits of a hybrid device that we are looking for once they have logged on in school for the first time)

 

I have seen it is possible to do the opposite and essentially domain join an Azure AD device. Would this give domain security groups to the user logging on? Looking into hybrid solutions for a small number of staff devices and trying to weigh up pros and cons to each approach

[DalekSec]

Autopilot is just a method of enrolling windows into Intune and Azure AD. You can also set it to domain join the device and have it Hybrid.

 

IIRC Microsoft recommend Hybrid currently as cloud only has its draw backs still and onsite AD only has lots of drawbacks.

 

Last place we used Autopilot to enroll the device into local and azure AD you can then login with either a AD account or an azure AD account.

 

Cloud only which i have at new gaffe i have had draw backs and ideally i'd do hybrid only but we have 0 onsite server infrastructure!

 

TLDR: Hybrid is the way to go

[CyBeRkId2002]

Ok. Our devices are enrolled in AD first, then SCCM adds them as hybrid. Not sure if this makes them different.

 

Will try signing in on one of our devices on Monday, outside of the school environment, and see if it lets me. From memory it doesn't and needs a domain login first (although cached off-site obviously works fine from that point on).