Forum Discussion
windows autopilot - hybrid join
Hello folks,
I have setup a hybrid Autopilot deployment profile to test on my OOBE laptop, an issue with my test laptop is that it doesn't connect to Autopilot service and so doesn't give me the Hi username! Welcome to Microsoft Services. It goes straight to sign in to microsoft account as a standard Windows 10 setup.
If i do Azure join profile, laptop connects to Autopilot service after joining the home wifi and starts the deployment.
For Hybrid setup, I have followed the below
https://docs.microsoft.com/en-us/mem/intune/enrollment/windows-autopilot-hybrid
My active directory domain controller is a Azure VM. The Intune connector, AD connect all is setup correctly and shows green as healthy connection.
Any help will be much appreciated.
thanks
v
PeterRising Hi , yes. I have created the dynamic group for Device in Azure. The imported hardware id show up as a member in the group and I have assigned the test user that I am using.
So if you switch to just Azure AD join, it works OK right?
It's only Hybrid Azure AD join where the autopilot deployment doesn't work? Do I have that correct?
With Hybrid Azure AD join and Autopilot, TPM can cause issues as per this doc - https://docs.microsoft.com/en-us/windows/deployment/windows-autopilot/self-deploying
vishal1502 your DC is running in the cloud (Azure) and your client is local, that will never work without the VPN option which is not yet available. As your client needs to be able to contact the DC.
I suggest yo have a look at Michal Niehaus his article https://oofhours.com/2020/05/23/digging-into-hybrid-azure-ad-join/
