Forum Discussion
Microsoft 365 - upgrade windows 7 to Windows 10
- Jan 28, 2019
Please add the UPN (your office 365 custom domain) in your AD and attach this to your users in AD as their UPN! This change should now sync!
If they are hybrid joined they should be able to login with their UPN now
Also: make sure that the GPO for "Do not connect to any Windows Update Internet locations" is TURNED OFF!
Just to make sure: Do your licenses include Windows 10??
Adam
The on-prem AD has Azure AD connect setup and the machines are hybrid joined using that. The AD users and computers appear in the Azure AD and I've assigned the AD users an A3 licence in Office 365. The AD has an internal domain name so the users appear in Azure AD as an onmicrosoft.com domain. I'm just missing the probably obvious last step of how these users then activate the Windows 10 subscription so that the Windows 10 pro computer becomes enterprise.
I can't logon to the Windows 10 computer using the Azure AD username (user@<mydomain>.onmicrosoft.com) so I'm not sure what "sign in to the Azure AD" means in the earlier part of the thread to enable the activation. Or exactly what documentation is this from as I've followed all I could find?
Thanks,
Nigel
Please add the UPN (your office 365 custom domain) in your AD and attach this to your users in AD as their UPN! This change should now sync!
If they are hybrid joined they should be able to login with their UPN now
Also: make sure that the GPO for "Do not connect to any Windows Update Internet locations" is TURNED OFF!
Just to make sure: Do your licenses include Windows 10??
Adam
- ennis66ieMar 23, 2020Copper ContributorYes, you rite!!!
- Jan 29, 2019
Great to hear!!
/ Adam
- Nigel ArcherJan 29, 2019Brass Contributor
Thanks both. I've got it working now as I was missing the part about non-routable domains and the UPN.
Nigel
- Jan 28, 2019Yeah, thanks! Missed that part :)
- Jono GreenJan 28, 2019Former Employee
He mentioned M365 A3 in an earlier comment so yes there should be the license.
Updating the UPN suffix when using AD Connect is quite important and if you're using EMS down the line to manage the devices you might strike trouble here as well with an internal domain suffix as UPN. Having a .local suffix is called a non-routable domain suffix. Can find guidance on adding a vanity domain suffix as a UPN within AD here.
Then you can just select multiple users and batch-update their UPN within AD, run a delta sync in Azure AD Connect then try sign into a device using Azure AD account.