Merge pull request #113228 from MicrosoftDocs/release-preview-wvd-arm

Release preview wvd arm

Author: huypub

articles/firewall/protect-windows-virtual-desktop.md

@@ -22,7 +22,7 @@ Follow the guidelines in this article to provide additional protection for your
 
  - A deployed WVD environment and host pool.
 
-   For more information, see [Tutorial: Create a host pool by using the Azure Marketplace](../virtual-desktop/create-host-pools-azure-marketplace.md) and [Create a host pool with an Azure Resource Manager template](../virtual-desktop/create-host-pools-arm-template.md).
+   For more information, see [Tutorial: Create a host pool by using the Azure Marketplace](../virtual-desktop/create-host-pools-azure-marketplace.md) and [Create a host pool with an Azure Resource Manager template](../virtual-desktop/virtual-desktop-fall-2019/create-host-pools-arm-template.md).
 
 To learn more about WVD environments see [Windows Virtual Desktop environment](../virtual-desktop/environment-setup.md).
 

articles/virtual-desktop/TOC.yml

@@ -1,22 +1,18 @@
-- name: Windows Virtual Desktop
+- name: Windows Virtual Desktop Spring 2020 Release
   href: index.yml
 - name: Overview
   items:
   - name: What is Windows Virtual Desktop?
     href: overview.md
 - name: Tutorials
   items:
-  - name: 1. Create a tenant in Windows Virtual Desktop
-    href: tenant-setup-azure-active-directory.md
-  - name: 2. Create service principals and role assignments by using PowerShell
-    href: create-service-principal-role-powershell.md
-  - name: 3. Create a host pool by using the Azure Marketplace
+  - name: 1. Create a host pool with the Azure portal
     href: create-host-pools-azure-marketplace.md
-  - name: 4. Manage app groups
+  - name: 2. Manage app groups
     href: manage-app-groups.md
-  - name: 5. Create a host pool to validate service updates
+  - name: 3. Create a host pool to validate service updates
     href: create-validation-host-pool.md
-  - name: 6. Set up service alerts
+  - name: 4. Set up service alerts
     href: set-up-service-alerts.md
 - name: How-to
   items:
@@ -32,18 +28,18 @@
         href: connect-macos.md
       - name: Connect with the iOS client
         href: connect-ios.md
+  - name: Set up the PowerShell module
+    href: powershell-module.md
   - name: Create a host pool and session hosts
     items:
-      - name: Azure Resource Manager template
-        href: create-host-pools-arm-template.md
       - name: PowerShell
         href: create-host-pools-powershell.md
-      - name: Deploy a Windows 7 virtual machine
-        href: deploy-windows-7-virtual-machine.md
       - name: Deploy a GPU-based session host
         href: configure-vm-gpu.md
       - name: Expand an existing host pool
         href: expand-existing-host-pool.md
+      - name: Manage app groups with PowerShell
+        href: manage-app-groups-powershell.md
   - name: Create a profile container
     items:
       - name: Use a VM-based file share
@@ -68,20 +64,10 @@
         href: set-up-customize-master-image.md
       - name: Install Office on a master VHD image
         href: install-office-on-wvd-master-image.md
-  - name: Scale session hosts automatically
-    href: set-up-scaling-script.md
   - name: Customize feed
     href: customize-feed-for-virtual-desktop-users.md
-  - name: Deploy the management tool
-    items:
-      - name: Azure Resource Manager template
-        href: manage-resources-using-ui.md
-      - name: PowerShell
-        href: manage-resources-using-ui-powershell.md
   - name: Use service diagnostics
     items:
-        - name: Deploy the diagnostics tool
-          href: deploy-diagnostics.md
         - name: Use diagnostics with Log Analytics
           href: diagnostics-log-analytics.md
   - name: Publish built-in apps
@@ -124,10 +110,6 @@
     href: troubleshoot-set-up-issues.md
   - name: Session host virtual machine configuration
     href: troubleshoot-vm-configuration.md
-  - name: Troubleshoot Windows 7 virtual machines in Windows Virtual Desktop
-    href: troubleshoot-windows-7-vm.md
-  - name: Troubleshoot the Windows Virtual Desktop management tool
-    href: troubleshoot-management-tool.md
   - name: Remote Desktop service connections
     href: troubleshoot-service-connection.md
   - name: Remote Desktop client issues
@@ -141,9 +123,9 @@
   - name: Linux support
     href: linux-overview.md
   - name: PowerShell
-    href: /powershell/windows-virtual-desktop/overview
+    href: /powershell/module/az.desktopvirtualization
   - name: REST API
-    href: /rest/api/virtual-desktop/
+    href: /rest/api/desktopvirtualization/
   - name: Supported RDP file settings
     href: https://docs.microsoft.com/windows-server/remote/remote-desktop-services/clients/rdp-files?context=/azure/virtual-desktop/context/context
   - name: Network guidance

articles/virtual-desktop/app-attach.md

@@ -14,7 +14,7 @@ manager: lizross
 
 > [!IMPORTANT]
 > MSIX app attach is currently in public preview.
-> This preview version is provided without a service level agreement, and it's not recommended for production workloads. Certain features might not be supported or might have constrained capabilities. 
+> This preview version is provided without a service level agreement, and we don't recommend using it for production workloads. Certain features might not be supported or might have constrained capabilities. 
 > For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
 
 This topic will walk you through how to set up MSIX app attach in a Windows Virtual Desktop environment.
@@ -24,7 +24,7 @@ This topic will walk you through how to set up MSIX app attach in a Windows Virt
 Before you get started, here's what you need to configure MSIX app attach:
 
 - Access to the Windows Insider portal to obtain the version of Windows 10 with support for the MSIX app attach APIs.
-- A functioning Windows Virtual Desktop deployment. For information, see [Create a tenant in Windows Virtual Desktop](tenant-setup-azure-active-directory.md).
+- A functioning Windows Virtual Desktop deployment. For information, see [Create a tenant in Windows Virtual Desktop](./virtual-desktop-fall-2019/tenant-setup-azure-active-directory.md).
 - The MSIX packaging tool
 - A network share in your Windows Virtual Desktop deployment where the MSIX package will be stored
 

articles/virtual-desktop/apply-windows-license.md

@@ -18,7 +18,7 @@ Windows Virtual Desktop licensing allows you to apply a license to any Windows o
 
 There are a few ways to use the Windows Virtual Desktop license:
 - You can create a host pool and its session host virtual machines using the [Azure Marketplace offering](./create-host-pools-azure-marketplace.md). Virtual machines created this way automatically have the license applied.
-- You can create a host pool and its session host virtual machines using the [GitHub Azure Resource Manager template](./create-host-pools-arm-template.md). Virtual machines created this way automatically have the license applied.
+- You can create a host pool and its session host virtual machines using the [GitHub Azure Resource Manager template](./virtual-desktop-fall-2019/create-host-pools-arm-template.md). Virtual machines created this way automatically have the license applied.
 - You can apply a license to an existing session host virtual machine. To do this, first follow the instructions in [Create a host pool with PowerShell](./create-host-pools-powershell.md) to create a host pool and associated VMs, then return to this article to learn how to apply the license.
 
 ## Apply a Windows license to a session host VM

articles/virtual-desktop/configure-host-pool-load-balancing.md

@@ -17,34 +17,65 @@ Configuring the load-balancing method for a host pool allows you to adjust the W
 >[!NOTE]
 > This does not apply to a persistent desktop host pool because users always have a 1:1 mapping to a session host within the host pool.
 
+## Prerequisites
+
+This article assumes you've followed the instructions in [Set up the Windows Virtual Desktop PowerShell module](powershell-module.md) to download and install the PowerShell module and sign in to your Azure account.
+
 ## Configure breadth-first load balancing
 
 Breadth-first load balancing is the default configuration for new non-persistent host pools. Breadth-first load balancing distributes new user sessions across all available session hosts in the host pool. When configuring breadth-first load balancing, you may set a maximum session limit per session host in the host pool.
 
-First, [download and import the Windows Virtual Desktop PowerShell module](/powershell/windows-virtual-desktop/overview/) to use in your PowerShell session if you haven't already. After that, run the following cmdlet to sign in to your account:
+To configure a host pool to perform breadth-first load balancing without adjusting the maximum session limit, run the following PowerShell cmdlet:
 
 ```powershell
-Add-RdsAccount -DeploymentUrl "https://rdbroker.wvd.microsoft.com"
+Update-AzWvdHostPool -ResourceGroupName <resourcegroupname> -Name <hostpoolname> -LoadBalancerType 'BreadthFirst' 
 ```
 
-To configure a host pool to perform breadth-first load balancing without adjusting the maximum session limit, run the following PowerShell cmdlet:
+After that, to make sure you've set the breadth-first load balancing method, run the following cmdlet: 
 
 ```powershell
-Set-RdsHostPool <tenantname> <hostpoolname> -BreadthFirstLoadBalancer
+Get-AzWvdHostPool -ResourceGroupName <resourcegroupname> -Name <hostpoolname> | format-list Name, LoadBalancerType 
+
+Name             : hostpoolname 
+LoadBalancerType : BreadthFirst
 ```
 
 To configure a host pool to perform breadth-first load balancing and to use a new maximum session limit, run the following PowerShell cmdlet:
 
 ```powershell
-Set-RdsHostPool <tenantname> <hostpoolname> -BreadthFirstLoadBalancer -MaxSessionLimit ###
+Update-AzWvdHostPool -ResourceGroupName <resourcegroupname> -Name <hostpoolname> -LoadBalancerType 'BreadthFirst' -MaxSessionLimit ###
 ```
 
 ## Configure depth-first load balancing
 
-Depth-first load balancing distributes new user sessions to an available session host with the highest number of connections but has not reached its maximum session limit threshold. When configuring depth-first load balancing, you **must** set a maximum session limit per session host in the host pool.
+Depth-first load balancing distributes new user sessions to an available session host with the highest number of connections but has not reached its maximum session limit threshold. When configuring depth-first load balancing, you must set a maximum session limit per session host in the host pool.
 
 To configure a host pool to perform depth-first load balancing, run the following PowerShell cmdlet:
 
 ```powershell
-Set-RdsHostPool <tenantname> <hostpoolname> -DepthFirstLoadBalancer -MaxSessionLimit ###
+Update-AzWvdHostPool -ResourceGroupName <resourcegroupname> -Name <hostpoolname> -LoadBalancerType 'DepthFirst' -MaxSessionLimit ### 
+```
+
+To make sure the setting has updated, run this cmdlet:
+
+```powershell
+Get-AzWvdHostPool -ResourceGroupName <resourcegroupname> -Name <hostpoolname> | format-list Name, LoadBalancerType, MaxSessionLimit 
+
+Name             : hostpoolname
+LoadBalancerType : DepthFirst
+MaxSessionLimit  : 6
 ```
+
+## Configure load balancing with the Azure portal
+
+You can also configure load balancing with the Azure portal.
+
+To configure load balancing:
+
+1. Sign into the Azure portal at https://portal.azure.com. 
+2. Search for and select **Windows Virtual Desktop** under Services. 
+3. In the Windows Virtual Desktop page, select **Host pools**.
+4. Select the name of the host pool you want to edit.
+5. Select **Properties**.
+6. Enter the **Max session limit** into the field and select the **load balancing algorithm** you want for this host pool in the drop-down menu.
+7. Select **Save**. This applies the new load balancing settings.

articles/virtual-desktop/configure-host-pool-personal-desktop-assignment-type.md

@@ -6,44 +6,43 @@ author: HeidiLohr
 
 ms.service: virtual-desktop
 ms.topic: conceptual
-ms.date: 12/10/2019
+ms.date: 04/30/2020
 ms.author: helohr
 manager: lizross
 ---
 # Configure the personal desktop host pool assignment type
 
+>[!IMPORTANT]
+>This content applies to the Spring 2020 update with Azure Resource Manager Windows Virtual Desktop objects. If you're using the Windows Virtual Desktop Fall 2019 release without Azure Resource Manager objects, see [this article](./virtual-desktop-fall-2019/configure-host-pool-personal-desktop-assignment-type-2019.md).
+>
+> The Windows Virtual Desktop Spring 2020 update is currently in public preview. This preview version is provided without a service level agreement, and we don't recommend using it for production workloads. Certain features might not be supported or might have constrained capabilities. 
+> For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
+
 You can configure the assignment type of your personal desktop host pool to adjust your Windows Virtual Desktop environment to better suit your needs. In this topic, we'll show you how to configure automatic or direct assignment for your users.
 
 >[!NOTE]
 > The instructions in this article only apply to personal desktop host pools, not pooled host pools, since users in pooled host pools aren't assigned to specific session hosts.
 
+## Prerequisites
+
+This article assumes you've already downloaded and installed the Windows Virtual Desktop PowerShell module. If you haven't, follow the instructions in [Set up the PowerShell module](powershell-module.md).
+
 ## Configure automatic assignment
 
 Automatic assignment is the default assignment type for new personal desktop host pools created in your Windows Virtual Desktop environment. Automatically assigning users doesn't require a specific session host.
 
 To automatically assign users, first assign them to the personal desktop host pool so that they can see the desktop in their feed. When an assigned user launches the desktop in their feed, they will claim an available session host if they have not already connected to the host pool, which completes the assignment process.
 
-Before you start, [download and import the Windows Virtual Desktop PowerShell module](/powershell/windows-virtual-desktop/overview/) if you haven't already. 
-
-> [!NOTE]
-> Make sure you've installed Windows Virtual Desktop PowerShell module version 1.0.1534.2001 or later before following these instructions.
-
-After that, run the following cmdlet to sign in to your account:
-
-```powershell
-Add-RdsAccount -DeploymentUrl "https://rdbroker.wvd.microsoft.com"
-```
-
 To configure a host pool to automatically assign users to VMs, run the following PowerShell cmdlet:
 
 ```powershell
-Set-RdsHostPool <tenantname> <hostpoolname> -AssignmentType Automatic
+Update-AzWvdHostPool -ResourceGroupName <resourcegroupname> -Name <hostpoolname> -PersonalDesktopAssignmentType Automatic
 ```
 
 To assign a user to the personal desktop host pool, run the following PowerShell cmdlet:
 
 ```powershell
-Add-RdsAppGroupUser <tenantname> <hostpoolname> "Desktop Application Group" -UserPrincipalName <userupn>
+New-AzRoleAssignment -SignInName <userupn> -RoleDefinitionName "Desktop Virtualization User" -ResourceName <appgroupname> -ResourceGroupName <resourcegroupname> -ResourceType 'Microsoft.DesktopVirtualization/applicationGroups'
 ```
 
 ## Configure direct assignment
@@ -53,19 +52,19 @@ Unlike automatic assignment, when you use direct assignment, you must assign the
 To configure a host pool to require direct assignment of users to session hosts, run the following PowerShell cmdlet:
 
 ```powershell
-Set-RdsHostPool <tenantname> <hostpoolname> -AssignmentType Direct
+Update-AzWvdHostPool -ResourceGroupName <resourcegroupname> -Name <hostpoolname> -PersonalDesktopAssignmentType Direct
 ```
 
 To assign a user to the personal desktop host pool, run the following PowerShell cmdlet:
 
 ```powershell
-Add-RdsAppGroupUser <tenantname> <hostpoolname> "Desktop Application Group" -UserPrincipalName <userupn>
+New-AzRoleAssignment -SignInName <userupn> -RoleDefinitionName "Desktop Virtualization User" -ResourceName <appgroupname> -ResourceGroupName <resourcegroupname> -ResourceType 'Microsoft.DesktopVirtualization/applicationGroups'
 ```
 
 To assign a user to a specific session host, run the following PowerShell cmdlet:
 
 ```powershell
-Set-RdsSessionHost <tenantname> <hostpoolname> -Name <sessionhostname> -AssignedUser <userupn>
+Update-AzWvdSessionHost -HostPoolName <hostpoolname> -Name <sessionhostname> -ResourceGroupName <resourcegroupname> -AssignedUser <userupn>
 ```
 
 ## Next steps
@@ -74,3 +73,6 @@ Now that you've configured the personal desktop assignment type, you can sign in
 
 - [Connect with the Windows Desktop client](connect-windows-7-and-10.md)
 - [Connect with the web client](connect-web.md)
+- [Connect with the Android client](connect-android.md)
+- [Connect with the iOS client](connect-ios.md)
+- [Connect with the macOS client](connect-macos.md)

articles/virtual-desktop/configure-vm-gpu.md

@@ -12,6 +12,12 @@ ms.author: denisgun
 
 # Configure graphics processing unit (GPU) acceleration for Windows Virtual Desktop
 
+>[!IMPORTANT]
+>This content applies to the Spring 2020 update with Azure Resource Manager Windows Virtual Desktop objects. If you're using the Windows Virtual Desktop Fall 2019 release without Azure Resource Manager objects, see [this article](./virtual-desktop-fall-2019/configure-vm-gpu-2019.md).
+>
+> The Windows Virtual Desktop Spring 2020 update is currently in public preview. This preview version is provided without a service level agreement, and we don't recommend using it for production workloads. Certain features might not be supported or might have constrained capabilities. 
+> For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
+
 Windows Virtual Desktop supports GPU-accelerated rendering and encoding for improved app performance and scalability. GPU acceleration is particularly crucial for graphics-intensive apps.
 
 Follow the instructions in this article to create a GPU optimized Azure virtual machine, add it to your host pool, and configure it to use GPU acceleration for rendering and encoding. This article assumes you already have a Windows Virtual Desktop tenant configured.
@@ -22,7 +28,7 @@ Azure offers a number of [GPU optimized virtual machine sizes](/azure/virtual-ma
 
 ## Create a host pool, provision your virtual machine, and configure an app group
 
-Create a new host pool using a VM of the size you selected. For instructions, see [Tutorial: Create a host pool with Azure Marketplace](/azure/virtual-desktop/create-host-pools-azure-marketplace).
+Create a new host pool using a VM of the size you selected. For instructions, see [Tutorial: Create a host pool with the Azure portal](/azure/virtual-desktop/create-host-pools-azure-marketplace).
 
 Windows Virtual Desktop supports GPU-accelerated rendering and encoding in the following operating systems:
 
@@ -35,7 +41,7 @@ You must also configure an app group, or use the default desktop app group (name
 
 To take advantage of the GPU capabilities of Azure N-series VMs in Windows Virtual Desktop, you must install the appropriate graphics drivers. Follow the instructions at [Supported operating systems and drivers](/azure/virtual-machines/windows/sizes-gpu#supported-operating-systems-and-drivers) to install drivers from the appropriate graphics vendor, either manually or using an Azure VM extension.
 
-Only drivers distributed by Azure are supported for Windows Virtual Desktop. Additionaly, for Azure VMs with NVIDIA GPUs, only [NVIDIA GRID drivers](/azure/virtual-machines/windows/n-series-driver-setup#nvidia-grid-drivers) are supported for Windows Virtual Desktop.
+Only drivers distributed by Azure are supported for Windows Virtual Desktop. Additionally, for Azure VMs with NVIDIA GPUs, only [NVIDIA GRID drivers](/azure/virtual-machines/windows/n-series-driver-setup#nvidia-grid-drivers) are supported for Windows Virtual Desktop.
 
 After driver installation, a VM restart is required. Use the verification steps in the above instructions to confirm that graphics drivers were successfully installed.