windows autopilot - hybrid join

[vishal1502]

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

[#2]

@vishal1502 

Hi, do you have a device security group associated with your deployment profile?

[#3]

@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. 

[#4]

@vishal1502 

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

[#5]

@PeterRising 

yes, Azure AD works perfectly. No issues at all. 

I am not getting the 'Hi username! Welcome to Microsoft Services! after I select the language, keyboard and connect to home wifi. Straight it goes in 'sign to microsoft account'

please note I am trying the Hybrid join from my home, my Domain controller is a in Azure VM. I can understand if the process fails at domain join step, but I am not able to figure why I don't get Welcome to Microsoft Services page.

[#6]

@vishal1502 

Hi, I would suggest opening a ticket with Microsoft is the next best step to resolve this.

[#7]

@PeterRising cheers Peter. Seems that is the best option right now.

[#8]

@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/