Skip to content

Commit 75f9357

Browse files
authored
Update windows-desktop-multitenant-hosting-deployment.md
1 parent 53d4bfc commit 75f9357

File tree

1 file changed

+8
-7
lines changed

1 file changed

+8
-7
lines changed

articles/virtual-machines/windows/windows-desktop-multitenant-hosting-deployment.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -67,10 +67,10 @@ win11-22h2-pron Windows-11 MicrosoftWindowsDesktop westus
6767
6868
```
6969

70-
For more information on available images see [Find and use Azure Marketplace VM images with Azure PowerShell](./cli-ps-findimage.md)
70+
For more information on available images, see [Find and use Azure Marketplace VM images with Azure PowerShell](./cli-ps-findimage.md)
7171

7272
## Uploading Windows 11 VHD to Azure
73-
If you are uploading a generalized Windows 11 VHD, note Windows 11 does not have built-in administrator account enabled by default. To enable the built-in administrator account, include the following command as part of the Custom Script extension.
73+
If you're uploading a generalized Windows 11 VHD, note Windows 11 doesn't have built-in administrator account enabled by default. To enable the built-in administrator account, include the following command as part of the Custom Script extension.
7474

7575
```powershell
7676
Net user <username> /active:yes
@@ -91,7 +91,7 @@ For more information:
9191

9292

9393
## Deploying Windows 11 with Multitenant Hosting Rights
94-
Make sure you have [installed and configured the latest Azure PowerShell](/powershell/azure/). Once you have prepared your VHD, upload the VHD to your Azure Storage account using the `Add-AzVhd` cmdlet as follows:
94+
Make sure you've [installed and configured the latest Azure PowerShell](/powershell/azure/). Once you've prepared your VHD, upload the VHD to your Azure Storage account using the `Add-AzVhd` cmdlet as follows:
9595

9696
```powershell
9797
Add-AzVhd -ResourceGroupName "myResourceGroup" -LocalFilePath "C:\Path\To\myvhd.vhd" `
@@ -100,7 +100,7 @@ Add-AzVhd -ResourceGroupName "myResourceGroup" -LocalFilePath "C:\Path\To\myvhd.
100100

101101

102102
**Deploy using Azure Resource Manager Template Deployment**
103-
Within your Resource Manager templates, an additional parameter for `licenseType` can be specified. You can read more about [authoring Azure Resource Manager templates](../../azure-resource-manager/templates/syntax.md). Once you have your VHD uploaded to Azure, edit you Resource Manager template to include the license type as part of the compute provider and deploy your template as normal:
103+
Within your Resource Manager templates, an additional parameter for `licenseType` can be specified. You can read more about [authoring Azure Resource Manager templates](../../azure-resource-manager/templates/syntax.md). Once you've your VHD uploaded to Azure, edit your Resource Manager template to include the license type as part of the compute provider and deploy your template as normal:
104104
```json
105105
"properties": {
106106
"licenseType": "Windows_Client",
@@ -110,13 +110,14 @@ Within your Resource Manager templates, an additional parameter for `licenseType
110110
```
111111

112112
**Deploy via PowerShell**
113-
When deploying your Windows Server VM via PowerShell, you have an additional parameter for `-LicenseType`. Once you have your VHD uploaded to Azure, you create a VM using `New-AzVM` and specify the licensing type as follows:
113+
When deploying your Windows Server VM via PowerShell, you've an another parameter for `-LicenseType`. Once you've your VHD uploaded to Azure, you create a VM using `New-AzVM` and specify the licensing type as follows:
114+
114115
```powershell
115116
New-AzVM -ResourceGroupName "myResourceGroup" -Location "West US" -VM $vm -LicenseType "Windows_Client"
116117
```
117118

118119
## Verify your VM is utilizing the licensing benefit
119-
Once you have deployed your VM through either the PowerShell or Resource Manager deployment method, verify the license type with `Get-AzVM` as follows:
120+
Once you've deployed your VM through either the PowerShell or Resource Manager deployment method, verify the license type with `Get-AzVM` as follows:
120121
```powershell
121122
Get-AzVM -ResourceGroup "myResourceGroup" -Name "myVM"
122123
```
@@ -138,7 +139,7 @@ LicenseType :
138139
```
139140

140141
## Additional Information about joining Azure Active Directory
141-
Azure provisions all Windows VMs with built-in administrator account, which cannot be used to join Azure Active Directory. For example, *Settings > Account > Access Work or School > +Connect* will not work. You must create and log on as a second administrator account to join Azure AD manually. You can also configure Azure AD using a provisioning package, use the link in the *Next Steps* section to learn more.
142+
Azure provisions all Windows VMs with built-in administrator account, which can't be used to join Azure Active Directory. For example, *Settings > Account > Access Work or School > + Connect* won't work. You must create and log on as a second administrator account to join Azure AD manually. You can also configure Azure AD using a provisioning package, use the link in the *Next Steps* section to learn more.
142143

143144
## Next Steps
144145
- Learn more about [Configuring VDA for Windows 11](/windows/deployment/vda-subscription-activation)

0 commit comments

Comments
 (0)