This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi all, hoping someone has tried this and may have some answers... reading the docs, I should be able to assign a CSP Windows 10 Enterprise license to a user that currently has Win 10 Pro (for example to enable them to run Direct Access or machine based Always On VPN). However my initial tests I have been unable to see the OS change from Pro to Ent. I found this from 2017:
The suggested fix was very convoluted (aka unacceptable!) but I thought I would give it a try on my Win 10 Pro 1909 setup. Even after leaving the on prem domain, logging in as local admin (which seems to be the only way to get the option to 'join Azure AD' during setting up work or school account), then joining Azure AD and logging in with a user assigned the Win 10 Ent E3 license, it still remained Win 10 Pro. It seems that this is supposed to work, even automatically without these steps if the machine is 'Hybrid Azure AD joined' which this clients machines are. Really frustrating to read about these things and discuss them with clients, only for them not to work. Even if the above process worked, how you gonna do that for 200 workstations across the globe? Stink bro!
Keen to hear if anyone has used this method successfully on latest OS versions, thanks!
Simon
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(188.79999999999998, 25%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EST%3C/text%3E%3C/svg%3E)
This is down to how your users (even test) are signing in.
If you have setup hybrid domain joined for autopilot, then your users aren't signing into 365 when they log in to the laptop, they are instead logging in to the domain (AD not AAD)
As a result, the user isn't creating the 'Access Work or School' account for your 365 environment, only for Domain.
As a result of not creating that link to AAD specifically, you won't get the Enterprise licence associated with your M365 E3 (or similar) until that is configured.
This is a huge oversight by MS (surprised?) and it is a total pain.
On your autopilot device that's ready and signed in, have you tried starting say MS Teams, then selecting the 'allow my company to manage my device' when prompted on initial launch?
That should fix the problem after a period of time for a sync up. Failing that, the user will need to go to Access Work or School and add the account/connection.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(304, 19%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECS%3C/text%3E%3C/svg%3E)
Well the two lines in the bottom doesn't work, atleast not in our org, since you can't sign in to a Work or School account, since the pc is already inside a Hybrid join, and therefor in a domain join.
(tried both options since we are running our heads into a brick wall trying to make it work)
Hello @Simon Burbery ,
Here are the notes for upgrading Windows 10 Pro to Enterprise for your setup
Devices must be running Windows 10 Pro, version 1703, and be Azure Active Directory joined, or hybrid domain joined with Azure AD Connect. Customers who are federated with Azure Active Directory are also eligible.
There are many methods available to assign license. I haven one of them
Sign in to portal.office.com and open the user properties as shown below and assign the license:
Now that your Windows 10 Enterprise E3 or E5 licenses have been assigned to users, the users are ready to upgrade their devices running Windows 10 Pro
To join a device to Azure AD when the device already has Windows 10 Pro, version 1703 installed and set up
Please mark as "Accept the answer" if the above steps helps you. Others with similar issues can also follow the solution as per your suggestion
Regards,
Manu
Hi Manu, I hope you are a bot as you don't seem to have read my post at all. I've read all of that, it just simply does not work.
Hi,
For Microsoft customers with Enterprise Agreements (EA) or Microsoft Products & Services Agreements (MPSA), you must have the following:
Windows 10 (Pro or Enterprise) version 1703 or later installed on the devices to be upgraded.
Azure Active Directory (Azure AD) available for identity management.
Devices must be Azure AD-joined or Hybrid Azure AD joined. Workgroup-joined or Azure AD registered devices are not supported.
More information please refer to the following article:
https://learn.microsoft.com/en-us/windows/deployment/windows-10-subscription-activation
Hope above information can help you.
Hi Jenny, I hope you are a bot too... once again I know how it is supposed to work, my devices are Hybrid Azure AD Joined all the requirements are met. It just does not change to Enterprise at all. If I delete the device completely then leave the domain, then join Azure AD as local admin, it might work.
Today I am trying to change someone that has a MS Business Premium (so they are activated with Windows Business digital license (included with that subscription) on a Azure AD Hybrid device. I have changed their license to MS Business Standard (which does not include the license), then assigned a Windows 10 Enterprise E3 license. No matter what I do (and believe me I have tried everything!) it still activates with a Windows Business license and will not change to Windows Enterprise. Very disappointing and frustrating when these things do not work!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(99.2, 64%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
Not sure if the below note applies. I haven't set enterprise up, but I'm looking into it at the moment and found this note:
An issue has been identified where devices can lose activation status or be blocked from upgrading to Windows Enterprise if the device is not able to connect to Windows Update. A workaround is to ensure that devices do not have the REG_DWORD present HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\DoNotConnectToWindowsUpdateInternetLocations and set to 1. If this REG_DWORD is present, it must be set to 0.
Also ensure that the Group Policy setting: Computer Configuration > Administrative Templates > Windows Components > Windows Update > "Do not connect to any Windows Update Internet locations" is set to "Disabled".
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(73.60000000000001, 85%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECV%3C/text%3E%3C/svg%3E)
Hi,
I think there is a known bug:
An issue has been identified with Hybrid Azure AD joined devices that have enabled multi-factor authentication (MFA). If a user signs into a device using their Active Directory account and MFA is enabled, the device will not successfully upgrade to their Windows Enterprise subscription. Or it drops off when getting renewed after 30 days.
https://learn.microsoft.com/en-us/windows/deployment/windows-10-subscription-activation
I have had a ticket open with Premier support for about 6 weeks as this is not good.
Cheers
@Craig Vibert did you ever get a resolution with Premier support on this issue? The docs do say it is a known issue as you indicated, but was wondering if they gave you a workaround. I'm also dealing with Microsoft support on this, but it isn't Premier support and I don't expect much.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(291.2, 55.00000000000001%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMC%3C/text%3E%3C/svg%3E)
Did this issue ever get resolved? If so how? I think I have the same issue.
I did not. My ticket was open for a month and they just kept repeating the requirements which I met on the devices. I gave up and did a fresh start on the devices and Autopilot. They all upgraded fine from Pro to Enterprise at that point.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(115.19999999999999, 65%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETZ%3C/text%3E%3C/svg%3E)
Apologies for responding to old post.
Still no solution/update? Going through exact same problem.
You also stated that you did a fresh start and then an autopilot (as in Autopilot reset?). After that it installed Enterprise after logging in with the user assigned and Enterprise license?
Is that correct?
No, Microsoft Support nor I could figure out why some devices were not getting the Enterprise license. I surmised it was something to do with how the previous Help Desk person imaged them. In the end I just decide it wasn't worth spending time on and all new devices are Azure AD joined via Intune Autopilot and it works fine.