Sep 25 2018 08:12 PM - edited Jul 26 2020 07:02 PM
Sep 28 2018 06:05 AM
Oct 07 2018 05:32 AM
Oct 15 2018 06:26 PM
Oct 15 2018 10:34 PM
how about if you are upgrading items below?
- Windows 10 home to Windows 10 pro?
- Windows 10 pro to Windows 10 Enterprise?
Oct 15 2018 11:00 PM
Oct 15 2018 11:47 PM
Kindly take help fro the below video
Oct 16 2018 12:04 AM - edited Oct 16 2018 12:04 AM
Microsoft 365 offering includes a windows 10 enterprise upgrade license
Office 365 alone does not
Oct 23 2018 01:22 PM
Windows 10 home to Windows 10 pro?
You need either Windows 10 Pro, or Windows 7/8.1 Pro to upgrade.
Windows 10 pro to Windows 10 Enterprise?
This is supported. For both M365 Business and M365 Enterprise paths, simply add the licensing to each user, then sign that user into Azure Active Directory. When each user with a valid M365 Windows entitlement signs in, their Operating System will slipstream upgrade to either Windows 10 Business or Windows 10 Enterprise from Windows 10 Pro. If that user removes their Azure Active Directory sign-in, their Operating System will revert back to Windows 10 Pro.
Oct 29 2018 07:42 AM
Oct 29 2018 07:42 AM
Use your system management tool to upgrade Win7 to Win 10 and then assign and then assign the M365 E3/E5 license to the user but make sure you selecting Windows 10 Enterprise license in M365 E3/E5.
Refer to Windows 10 Subscription Activation.
Jan 24 2019 08:59 AM
I'm trying to setup Windows 10 subscription activation using M365. When you say "sign that user into Azure Active Directory". Do you mean add the AAD user as an account in settings on the Windows 10 computer? I've tried that and it hasn't worked?
This user has an M365 A3 licence in Office 365 and is running on a Windows 10 Pro machine.
Jan 24 2019 09:16 AM
Jan 28 2019 02:04 AM
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?
Jan 28 2019 02:13 AMSolution
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??
Jan 28 2019 10:49 AM
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.
Jan 29 2019 03:48 AM
Thanks both. I've got it working now as I was missing the part about non-routable domains and the UPN.