Autopilot onboarding experience for new users

[@danpowell7421]

The main point with I have had with Autopilot is when the devices take ages to become compliant, I've had some windows devices take a few hours. I normally resolve this by exempting the device ID in conditional access. I've also seen the Dell network optimizer get in the way. Dunno if there is a better way to go about making this smoother for the end user?

[@alexk7837]

Good stuff. Do you disable hello or keep it?

[@getrubix]

Either way works

[@upinsmoke-tv]

Ty bro for the vid , can I ask what app you used to share your android screen , I use air server but it bit flakey

[@getrubix]

Sure thing: github.com/Genymobile/scrcpy

[@BetaLyte]

But where did Clark get the phone and how did he enroll it?

[@getrubix]

The first sign in screen after I entered the password instructed the user to download authenticator app

[@BetaLyte]

​@@getrubix Sure, but that implies the user already has an enrolled device (can't really rely on a personal device for MFA, right?).

[@FiniSim0]

Same experience with Autopilot v2? Thanks in advance!

[@getrubix]

More or less, once user signs in.