Merge pull request #228418 from Heidilohr/work-apps-change3

Turning "app groups" into "application groups," "remote app groups" into "RemoteApp application groups."

Author: AnnaMHuff

articles/virtual-desktop/app-attach-azure-portal.md

@@ -93,22 +93,22 @@ To publish the apps:
 2. Select the application group you want to publish the apps to.
 
    >[!NOTE]
-   >MSIX applications can be delivered with MSIX app attach to both remote app and desktop app groups. When a MSIX package is assigned to a remote app group and desktop app group from the same host pool the desktop app group will be displayed in the feed.
+   >MSIX applications can be delivered with MSIX app attach to both remote app and desktop application groups. When a MSIX package is assigned to a RemoteApp application group and Desktop application group from the same host pool the Desktop application group will be displayed in the feed.
 
-3. Once you're in the app group, select the **Applications** tab. The **Applications** grid will display all existing apps within the app group.
+3. Once you're in the application group, select the **Applications** tab. The **Applications** grid will display all existing apps within the application group.
 
 4. Select **+ Add** to open the **Add application** tab.
 
       > [!div class="mx-imgBorder"]
       > ![A screenshot of the user selecting + Add to open the add application tab](media/select-add.png)
 
 5. For **Application source**, choose the source for your application.
-    - If you're using a Desktop app group, choose **MSIX package**.
+    - If you're using a Desktop application group, choose **MSIX package**.
 
       > [!div class="mx-imgBorder"]
       > ![A screenshot of a customer selecting MSIX package from the application source drop-down menu. MSIX package is highlighted in red.](media/select-source.png)
     
-    - If you're using a remote app group, choose one of the following options:
+    - If you're using a RemoteApp application group, choose one of the following options:
 
         - Start menu
         - App path
@@ -122,16 +122,16 @@ To publish the apps:
 
     - For **Description**, enter a short description of the app package.
 
-    - If you're using a remote app group, you can also configure these options:
+    - If you're using a RemoteApp application group, you can also configure these options:
 
         - **Icon path**
         - **Icon index**
 
 6. When you're done, select **Save**.
 
-## Assign a user to an app group
+## Assign a user to an application group
 
-After assigning MSIX apps to an app group, you'll need to grant users access to them. You can assign access by adding users or user groups to an app group with published MSIX applications. Follow the instructions in [Manage app groups with the Azure portal](manage-app-groups.md) to assign your users to an app group.
+After assigning MSIX apps to an application group, you'll need to grant users access to them. You can assign access by adding users or user groups to an application group with published MSIX applications. Follow the instructions in [Manage application groups with the Azure portal](manage-app-groups.md) to assign your users to an application group.
 
 ## Change MSIX package state
 

articles/virtual-desktop/app-attach-powershell.md

@@ -18,7 +18,7 @@ Here's what you need to configure MSIX app attach:
 
 - A functioning Azure Virtual Desktop deployment. To learn how to deploy Azure Virtual Desktop (classic), see [Create a tenant in Azure Virtual Desktop](./virtual-desktop-fall-2019/tenant-setup-azure-active-directory.md). To learn how to deploy Azure Virtual Desktop with Azure Resource Manager integration, see [Create a host pool with the Azure portal](./create-host-pools-azure-marketplace.md).
 - A Azure Virtual Desktop host pool with at least one active session host.
-- A Desktop remote app group.
+- A Desktop or RemoteApp application group.
 - The MSIX packaging tool.
 - An MSIX-packaged application expanded into an MSIX image that's uploaded into a file share.
 - A file share in your Azure Virtual Desktop deployment where the MSIX package will be stored.
@@ -190,42 +190,42 @@ To remove the package, run this cmdlet:
 Remove-AzWvdMsixPackage -FullName $obj.PackageFullName -HostPoolName $hp -ResourceGroupName $rg
 ```
 
-## Publish MSIX apps to an app group
+## Publish MSIX apps to an application group
 
-You can only follow the instructions in this section if you've finished following the instructions in the previous sections. If you have a host pool with an active session host, at least one Desktop app group, and have added an MSIX package to the host pool, you're ready to go.
+You can only follow the instructions in this section if you've finished following the instructions in the previous sections. If you have a host pool with an active session host, at least one Desktop application group, and have added an MSIX package to the host pool, you're ready to go.
 
-To publish an app from the MSIX package to an app group, you'll need to find its name, then use that name in the publishing cmdlet.
+To publish an app from the MSIX package to an application group, you'll need to find its name, then use that name in the publishing cmdlet.
 
 To publish an app:
 
-Run this cmdlet to list all available app groups:
+Run this cmdlet to list all available application groups:
 
 ```powershell
 Get-AzWvdApplicationGroup -ResourceGroupName $rg -SubscriptionId $subId
 ```
 
-When you've found the name of the app group you want to publish apps to, use its name in this cmdlet:
+When you've found the name of the application group you want to publish apps to, use its name in this cmdlet:
 
 ```powershell
 $grName = "<AppGroupName>"
 ```
 
 Finally, you'll need to publish the app.
 
-- To publish MSIX application to a desktop app group, run this cmdlet:
+- To publish MSIX application to a desktop application group, run this cmdlet:
 
    ```powershell
    New-AzWvdApplication -ResourceGroupName $rg -SubscriptionId $subId -Name PowerBi -ApplicationType MsixApplication -ApplicationGroupName $grName -MsixPackageFamilyName $obj.PackageFamilyName -CommandLineSetting 0
    ```
 
-- To publish the app to a remote app group, run this cmdlet instead:
+- To publish the app to a RemoteApp application group, run this cmdlet instead:
 
    ```powershell
    New-AzWvdApplication -ResourceGroupName $rg -SubscriptionId $subId -Name PowerBi -ApplicationType MsixApplication -ApplicationGroupName $grName -MsixPackageFamilyName $obj.PackageFamilyName -CommandLineSetting 0 -MsixPackageApplicationId $obj.PackageApplication.AppId
    ```
 
 >[!NOTE]
->If a user is assigned to both a remote app group and a desktop app group in the same host pool, when the user connects to their remote desktop, they will see MSIX apps from both groups.
+>If a user is assigned to both a RemoteApp application group and a desktop application group in the same host pool, when the user connects to their remote desktop, they will see MSIX apps from both groups.
 
 ## Next steps
 

articles/virtual-desktop/automatic-migration.md

@@ -34,7 +34,7 @@ Before you use the migration module, make sure you have the following things rea
 - PowerShell or PowerShell ISE to run the scripts you'll see in this article. The Microsoft.RdInfra.RDPowershell module doesn't work in PowerShell Core.
 
 >[!IMPORTANT]
->Migration only creates service objects in the US geography. If you try to migrate your service objects to another geography, it won't work. Also, if you have more than 500 app groups in your Azure Virtual Desktop (classic) deployment, you won't be able to migrate. You'll only be able to migrate if you rebuild your environment to reduce the number of app groups within your Azure Active Directory (Azure AD) tenant.
+>Migration only creates service objects in the US geography. If you try to migrate your service objects to another geography, it won't work. Also, if you have more than 500 application groups in your Azure Virtual Desktop (classic) deployment, you won't be able to migrate. You'll only be able to migrate if you rebuild your environment to reduce the number of application groups within your Azure Active Directory (Azure AD) tenant.
 
 ## Prepare your PowerShell environment
 
@@ -164,8 +164,8 @@ To migrate your Azure virtual Desktop (classic) resources to Azure Resource Mana
 
    You'll also need to specify a user assignment mode for the existing user assignments:
 
-      - Use **Copy** to copy all user assignments from your old app groups to Azure Resource Manager application groups. Users will be able to see feeds for both versions of their clients.
-      - Use **None** if you don't want to change the user assignments. Later, you can assign users or user groups to app groups with the Azure portal, PowerShell, or API. Users will only be able to see feeds using the Azure Virtual Desktop (classic) clients.
+      - Use **Copy** to copy all user assignments from your old application groups to Azure Resource Manager application groups. Users will be able to see feeds for both versions of their clients.
+      - Use **None** if you don't want to change the user assignments. Later, you can assign users or user groups to application groups with the Azure portal, PowerShell, or API. Users will only be able to see feeds using the Azure Virtual Desktop (classic) clients.
 
    You can only copy 2,000 user assignments per subscription, so your limit will depend on how many assignments are already in your subscription. The module calculates the limit based on how many assignments you already have. If you don't have enough assignments to copy, you'll get an error message that says "Insufficient role assignment quota to copy user assignments. Rerun command without the -CopyUserAssignments switch to migrate."
 
@@ -179,20 +179,20 @@ To migrate your Azure virtual Desktop (classic) resources to Azure Resource Mana
 
          - A resource group called "Tenantname," which contains your workspace.
 
-         - A resource group called "Tenantname_originalHostPoolName," which contains the host pool and desktop app groups.
+         - A resource group called "Tenantname_originalHostPoolName," which contains the host pool and desktop application groups.
 
-      - Any users you published to the newly created app groups.
+      - Any users you published to the newly created application groups.
 
       - Virtual machines will be available in both existing and new host pools to avoid user downtime during the migration process. This lets users connect to the same user session.
 
    Since these new Azure service objects are Azure Resource Manager objects, the module can't set Role-based Access Control (RBAC) permissions or diagnostic settings on them. Therefore, you'll need to update the RBAC permissions and settings for these objects manually.
 
-   Once the module validates the initial user connections, you can also publish the app group to more users or user groups, if you'd like.
+   Once the module validates the initial user connections, you can also publish the application group to more users or user groups, if you'd like.
 
    >[!NOTE]
-   >After migration, if you move app groups to a different resource group after assigning permissions to users, it will remove all RBAC roles. You'll need to reassign users RBAC permissions all over again.
+   >After migration, if you move application groups to a different resource group after assigning permissions to users, it will remove all RBAC roles. You'll need to reassign users RBAC permissions all over again.
 
-4. If you want to delete all Azure Virtual Desktop (classic) service objects, run **Complete-RdsHostPoolMigration** to finish the migration process. This cmdlet will delete all Azure Virtual Desktop (classic) objects, leaving only the new Azure objects. Users will only be able to see the feed for the newly created app groups on their clients. Once this command is done, you can safely delete the Azure Virtual Desktop (classic) tenant to finish the process.
+4. If you want to delete all Azure Virtual Desktop (classic) service objects, run **Complete-RdsHostPoolMigration** to finish the migration process. This cmdlet will delete all Azure Virtual Desktop (classic) objects, leaving only the new Azure objects. Users will only be able to see the feed for the newly created application groups on their clients. Once this command is done, you can safely delete the Azure Virtual Desktop (classic) tenant to finish the process.
 
    For example:
 
@@ -206,7 +206,7 @@ To migrate your Azure virtual Desktop (classic) resources to Azure Resource Mana
     Complete-RdsHostPoolMigration -Tenant Contoso -HostPool Office -Location EastUS
     ```
 
-    This will delete all service objects created by Azure Virtual Desktop (classic). You will be left with just the new Azure objects and users will only be able to see the feed for the newly created app groups on their clients. Once you are done finalizing your migration, you need to explicitly delete the tenant in Azure Virtual Desktop (classic).
+    This will delete all service objects created by Azure Virtual Desktop (classic). You will be left with just the new Azure objects and users will only be able to see the feed for the newly created application groups on their clients. Once you are done finalizing your migration, you need to explicitly delete the tenant in Azure Virtual Desktop (classic).
 
 5. If you've changed your mind about migrating and want to revert the process, run the **Revert-RdsHostPoolMigration** cmdlet.
     

articles/virtual-desktop/azure-ad-joined-session-hosts.md

@@ -45,14 +45,14 @@ You can deploy Azure AD-joined VMs directly from the Azure portal when you [crea
 
 ### Assign user access to host pools
 
-After you've created your host pool, you must assign users access to their resources. To grant access to resources, add each user to the app group. Follow the instructions in [Manage app groups](manage-app-groups.md) to assign user access to apps and desktops. We recommend that you use user groups instead of individual users wherever possible.
+After you've created your host pool, you must assign users access to their resources. To grant access to resources, add each user to the application group. Follow the instructions in [Manage application groups](manage-app-groups.md) to assign user access to apps and desktops. We recommend that you use user groups instead of individual users wherever possible.
 
 For Azure AD-joined VMs, you'll need to do two extra things on top of the requirements for Active Directory or Azure Active Directory Domain Services-based deployments:  
 
 - Assign your users the **Virtual Machine User Login** role so they can sign in to the VMs.
 - Assign administrators who need local administrative privileges the **Virtual Machine Administrator Login** role.
 
-To grant users access to Azure AD-joined VMs, you must [configure role assignments for the VM](../active-directory/devices/howto-vm-sign-in-azure-ad-windows.md#configure-role-assignments-for-the-vm). You can assign the **Virtual Machine User Login** or **Virtual Machine Administrator Login** role either on the VMs, the resource group containing the VMs, or the subscription. We recommend assigning the Virtual Machine User Login role to the same user group you used for the app group at the resource group level to make it apply to all the VMs in the host pool.
+To grant users access to Azure AD-joined VMs, you must [configure role assignments for the VM](../active-directory/devices/howto-vm-sign-in-azure-ad-windows.md#configure-role-assignments-for-the-vm). You can assign the **Virtual Machine User Login** or **Virtual Machine Administrator Login** role either on the VMs, the resource group containing the VMs, or the subscription. We recommend assigning the Virtual Machine User Login role to the same user group you used for the application group at the resource group level to make it apply to all the VMs in the host pool.
 
 ## Access Azure AD-joined VMs
 

articles/virtual-desktop/cli-powershell.md

@@ -135,4 +135,4 @@ Some PowerShell cmdlets require you to provide the object ID of Azure Virtual De
 Now that you know how to use Azure CLI and Azure PowerShell with Azure Virtual Desktop, here are some articles that use them:
 
 - [Create an Azure Virtual Desktop host pool with PowerShell or the Azure CLI](create-host-pools-powershell.md)
-- [Manage app groups using PowerShell or the Azure CLI](manage-app-groups-powershell.md)
+- [Manage application groups using PowerShell or the Azure CLI](manage-app-groups-powershell.md)

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

@@ -88,8 +88,8 @@ To directly assign a user to a session host in the Azure portal:
 4. At the Azure Virtual Desktop page, go the menu on the left side of the window and select **Host pools**.
 5. Select the host pool you want to assign users to.
 6. Next, go to the menu on the left side of the window and select **Application groups**.
-7. Select the name of the app group you want to assign users to, then select **Assignments** in the menu on the left side of the window.
-8. Select **+ Add**, then select the users or user groups you want to assign to this app group.
+7. Select the name of the application group you want to assign users to, then select **Assignments** in the menu on the left side of the window.
+8. Select **+ Add**, then select the users or user groups you want to assign to this application group.
 9. Select **Assign VM** in the Information bar to assign a session host to a user.
 10. Select the session host you want to assign to the user, then select **Assign**. You can also select **Assignment** > **Assign user**.
 11. Select the user you want to assign the session host to from the list of available users.