deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 13:27:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Merge pull request #8062 from MicrosoftDocs/frankroj-patch-1

Browse Source 
Clarify where VM can be hosted
This commit is contained in:
Angela Fleischmann 2023-03-20 14:21:45 -06:00 committed by GitHub
commit 155a745c06
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
windows/deployment/vda-subscription-activation.md
View File

@ -1,6 +1,7 @@
--- ---
title: Configure VDA for Windows subscription activation title: Configure VDA for Windows subscription activation
description: Learn how to configure virtual machines (VMs) to enable Windows 10 Subscription Activation in a Windows Virtual Desktop Access (VDA) scenario. description: Learn how to configure virtual machines (VMs) to enable Windows 10 Subscription Activation in a Windows Virtual Desktop Access (VDA) scenario.
ms.reviewer: nganguly
manager: aaroncz manager: aaroncz
ms.author: frankroj ms.author: frankroj
author: frankroj author: frankroj
@ -37,7 +38,7 @@ Deployment instructions are provided for the following scenarios:
### Scenario 1 ### Scenario 1
- The VM is running a supported version of Windows. - The VM is running a supported version of Windows.
- The VM is hosted in Azure or another Qualified Multitenant Hoster (QMTH). - The VM is hosted in Azure, an authorized outsourcer, or another Qualified Multitenant Hoster (QMTH).
When a user with VDA rights signs in to the VM using their Azure AD credentials, the VM is automatically stepped-up to Enterprise and activated. There's no need to do Windows Pro activation. This functionality eliminates the need to maintain KMS or MAK in the qualifying cloud infrastructure. When a user with VDA rights signs in to the VM using their Azure AD credentials, the VM is automatically stepped-up to Enterprise and activated. There's no need to do Windows Pro activation. This functionality eliminates the need to maintain KMS or MAK in the qualifying cloud infrastructure.