Jump to content

Windows Licensing, key vs Entra ID ... any prodcedural changes?

Recommended Posts


For a long time when I've been making and deploying Win10/11 images, I have been pre-populating the license field with the generic KMS key, which the machines have no trouble using (though we've switched from KMS to on-prem AD activation, fwiw).

At the same time, once the machines are placed in their destination OU, they get hybrid-joined to Entra ID (formerly Azure AD) which introduces user-based licensing from the cloud ... which I presume supersedes/overrides the previous license/activation config.

I was pondering - do I need to make any changes in image creation or deployment config as a result of the new Azure-licensing method? Are there any new best practices in light of this? (eg, what if we ditched on-prem AD and went Azure-native?)


Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...