Activation

Scenario 1

When a user with VDA rights signs in to the VM using their AAD credentials, the VM is automatically stepped-up to Enterprise and activated. There is no need to perform Windows 10 Pro activation. This eliminates the need to maintain KMS or MAK in the qualifying cloud infrastructure.

Scenario 2

The Hyper-V host and the VM are both running Windows 10, version 1803 or later.

Inherited Activation is enabled. All VMs created by a user with a Windows 10 E3 or E5 license are automatically activated independent of whether a user signs in iwth a local account or using an Azure Active Directory account.

Scenario 3

The VM is running Windows 10, version 1703 or 1709, or the hoster is not an authorized QMTH partner.

In this scenario, the underlying Windows 10 Pro license must be activated prior to Subscription Activation of Windows 10 Enterprise. Activation is accomplished using a Windows 10 Pro Generic Volume License Key (GVLK) and a Volume License KMS activation server provided by the hoster. Alternatively, a KMS activation server on your corporate network can be used if you have configured a private connection, such as ExpressRoute or VPN Gateway.

Azure Active Directory-joined VMs

Important

Azure Active Directory (Azure AD) provisioning packages have a 180 day limit on bulk token usage. You will need to update the provisioning package and re-inject it into the image after 180 days. Existing virtual machines that are Azure AD-joined and deployed will not need to be recreated.

In step 9, during setup with Windows Configuration Designer, under Name, type a name for the project that indicates it is not for Active Directory joined VMs, such as Desktop Bulk Enrollment Token Pro GVLK.

In step 11, during setup with Windows Configuration Designer, on the Account Management page, instead of enrolling in Active Directory, choose Enroll in Azure AD, click Get Bulk Token, sign in and add the bulk token using your organization's credentials.

In step 15, sub-step 2, when entering the PackagePath, use the project name you entered in step 9 (ex: Desktop Bulk Enrollment Token Pro GVLK.ppkg)