Windows 10 AAD enrollment with current versions of SCCM/Intune

We started testing Windows 10 with AAD join couple weeks ago. In our first testing environment (no Intune or SCCM) we can join Windows 10 boxes to Azure AD. No problem there.

But when we are trying to join computers to AAD tenant that has active Intune + SCCM subscription, it fails only saying "Something went wrong". All the settings in Azure AD are the same.

Just wondering, is this even suppose to work yet?

May 26th, 2015 1:35am

I had a similar experience in my lab, but the scenario was not 100% the same (Mine was Intune Standalone).

Are you by any change using a custom domain or are you using user@alias.onmicrosoft.com when you try to join?

I solved my problem by using the "alias.onmicrosoft.com" address, when adding the device.

Free Windows Admin Tool Kit Click here and download it now
May 26th, 2015 6:39am

I'm in the same boat on this one, ConfigMgr 2012 R2 SP1/Intune Hybrid with domain joined Win 10 (10130).

Trying to connect to workplace just results in "Something went wrong".

I've had a very brief look, but can't find any relevant logs client side to check, anyone know a place to start checking?

Thanks,
Steve

June 12th, 2015 9:53am

Hi,

I had the same issue with Intune standalone (trial subscription) and the problem was that I had not set the Mobile Device Management Authority in Intune. After I did, the enrollment worked like a charm.

W10 build 10162.

Regards
Olof

Free Windows Admin Tool Kit Click here and download it now
July 10th, 2015 2:29am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics