Merge pull request #293195 from dknappettmsft/avd-freshness-january-2025

AVD freshness January 2025

Author: v-dirichards

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

@@ -5,7 +5,7 @@ ms.topic: conceptual
 zone_pivot_groups: azure-virtual-desktop-app-attach
 author: dknappettmsft
 ms.author: daknappe
-ms.date: 12/08/2023
+ms.date: 01/17/2025
 ---
 
 # App attach and MSIX app attach in Azure Virtual Desktop
@@ -16,12 +16,12 @@ The following table compares MSIX app attach with app attach:
 
 | MSIX app attach | App attach |
 |--|--|
-| Applications are delivered using RemoteApp or as part of a desktop session. Permissions are controlled by assignment to application groups, however all desktop users see all MSIX app attach applications in the desktop application group. | Applications are delivered using RemoteApp or as part of a desktop session. Permissions are applied per application per user, giving you greater control over which applications your users can access in a remote session. Desktop users only see the app attach applications assigned to them. |
+| Applications are delivered using RemoteApp or as part of a desktop session. Assignment to application groups controls access, however all desktop users see all MSIX app attach applications in the desktop application group. | Applications are delivered using RemoteApp or as part of a desktop session. Permissions are applied per application per user, giving you greater control over which applications your users can access in a remote session. Desktop users only see the app attach applications assigned to them. |
 | Applications might only run on one host pool. If you want it to run on another host pool, you must create another package. | The same application package can be used across multiple host pools. |
 | Applications can only run on the host pool in which they're added. | Applications can run on any session host running a Windows client operating system in the same Azure region as the application package. |
 | To update the application, you must delete and recreate the application with another version of the package. You should update the application in a maintenance window. | Applications can be upgraded to a new application version with a new disk image without the need for a maintenance window. |
 | Users can't run two versions of the same application on the same session host. | Users can run two versions of the same application concurrently on the same session host. |
-| Telemetry for usage and health is not available through Azure Log Analytics. | Telemetry for usage and health is available through Azure Log Analytics. |
+| Telemetry for usage and health isn't available through Azure Log Analytics. | Telemetry for usage and health is available through Azure Log Analytics. |
 
 You can use the following application package types and file formats:
 
@@ -38,14 +38,14 @@ MSIX and Appx are Windows application package formats that provide a modern pack
 > [!TIP]
 > Select a button at the top of this article to choose between *app attach* and *MSIX app attach* to see the relevant documentation.
 
-You can get MSIX packages from software vendors, or you can [create an MSIX package from an existing installer](/windows/msix/packaging-tool/create-an-msix-overview). To learn more about MSIX, see [What is MSIX?](/windows/msix/overview)
+You can get MSIX packages from software vendors or you can [create an MSIX package from an existing installer](/windows/msix/packaging-tool/create-an-msix-overview). To learn more about MSIX, see [What is MSIX?](/windows/msix/overview)
 
 ::: zone pivot="app-attach"
 ## How a user gets an application 
 
 You can assign different applications to different users in the same host pool or on the same session host. During sign-in, all three of the following requirements must be met for the user to get the right application at the right time: 
 
-- The application must be assigned to the host pool. Assigning the application to the host pool enables you to be selective about which host pools the application is available on to ensure that the right hardware resources are available for use by the application. For example, if an application is graphics-intensive, you can ensure it only runs on a host pool with GPU-optimized session hosts. 
+- The application must be assigned to the host pool. Assigning the application to the host pool enables you to be selective about which host pools the application is available on to ensure that the right hardware resources are available for use by the application. For example if an application is graphics-intensive, you can ensure it only runs on a host pool with GPU-optimized session hosts. 
 
 - The user must be able to sign-in to session hosts in the host pool, so they must be in a Desktop or RemoteApp application group. For a RemoteApp application group, the app attach application must be added to the application group, but you don't need to add the application to a desktop application group.
 
@@ -78,7 +78,7 @@ Before you can use MSIX application packages with Azure Virtual Desktop, you nee
 
 ### Disk image types
 
-For MSIX and Appx disk images, you can use *Composite Image File System (CimFS)*, *VHDX* or *VHD*, but we don't recommend using VHD. Mounting and unmounting CimFS images is faster than VHD and VHDX files and also consumes less CPU and memory. We only recommend using CimFS for your application images if your session hosts are running Windows 11.
+For MSIX and Appx disk images, you can use *Composite Image File System (CimFS)*, *VHDX*, or *VHD*, but we don't recommend using VHD. Mounting and unmounting CimFS images is faster than VHD and VHDX files and also consumes less CPU and memory. We only recommend using CimFS for your application images if your session hosts are running Windows 11.
 
 A CimFS image is a combination of several files: one file has the `.cim` file extension and contains metadata, together with at least two other files, one starting with `objectid_` and the other starting with `region_` that contain the actual application data. The files accompanying the `.cim` file don't have a file extension. The following table is a list of example files you'd find for a CimFS image:
 
@@ -134,11 +134,11 @@ MSIX app attach doesn't limit the number of applications users can use. You shou
 ## Application state
 
 ::: zone pivot="app-attach"
-Application packages are set as **active** or **inactive**. Packages set to active makes the application available to users. Packages set to inactive are ignored by Azure Virtual Desktop and not added when a user signs-in.
+Application packages are set as **active** or **inactive**. Packages set to active makes the application available to users. Azure Virtual Desktop ignores packages set to **inactive** and aren't added when a user signs in.
 ::: zone-end
 
 ::: zone pivot="msix-app-attach"
-An MSIX package is set as **active** or **inactive**. MSIX packages set to active makes the application available to users. MSIX packages set to inactive are ignored by Azure Virtual Desktop and not added when a user signs in.
+An MSIX package is set as **active** or **inactive**. MSIX packages set to active makes the application available to users. Azure Virtual Desktop ignores packages set to **inactive** and aren't added when a user signs in.
 ::: zone-end
 
 ::: zone pivot="app-attach"
@@ -262,9 +262,9 @@ All MSIX and Appx packages require a valid code signing certificate. To use thes
 
 - A tool such as the PowerShell cmdlet [New-SelfSignedCertificate](/powershell/module/pki/new-selfsignedcertificate) that generates a self-signed certificate. You should only use self-signed certificates in a test environment. For more information on creating a self-signed certificate for MSIX and Appx packages, see [Create a certificate for package signing](/windows/msix/package/create-certificate-package-signing).
 
-Once you've obtained a certificate, you need to digitally sign your MSIX or Appx packages with the certificate. You can use the [MSIX Packaging Tool](/windows/msix/packaging-tool/tool-overview) to sign your packages when you create an MSIX package. For more information, see [Create an MSIX package from any desktop installer](/windows/msix/packaging-tool/create-app-package).
+Once you obtain a certificate, you need to digitally sign your MSIX or Appx packages with the certificate. You can use the [MSIX Packaging Tool](/windows/msix/packaging-tool/tool-overview) to sign your packages when you create an MSIX package. For more information, see [Create an MSIX package from any desktop installer](/windows/msix/packaging-tool/create-app-package).
 
-To ensure the certificate is trusted on your session hosts, you need your session hosts to trust the whole certificate chain. How you do this depends on where you got the certificate from and how you manage your session hosts and the identity provider you use. The following table provides some guidance on how to ensure the certificate is trusted on your session hosts:
+To ensure the certificate is trusted on your session hosts, you need your session hosts to trust the whole certificate chain. How your session hosts trust the certificate chain depends on where you got the certificate from and how you manage your session hosts and the identity provider you use. The following table provides some guidance on how to ensure the certificate is trusted on your session hosts:
 
 - **Public CA**: certificates from a public CA are trusted by default in Windows and Windows Server.
 
@@ -279,7 +279,7 @@ To ensure the certificate is trusted on your session hosts, you need your sessio
 - **Self-signed**: install the trusted root to the **Trusted Root Certification Authorities** store on each session host. We don't recommend distributing this certificate using Group Policy or Intune as it should only be used for testing.
 
 > [!IMPORTANT]
-> You should timestamp your package so that its validity can outlast your certificate's expiration date. Otherwise, once the certificate has expired, you need to update the package with a new valid certificate and once again ensure it's trusted on your session hosts.
+> You should timestamp your package so that its validity can outlast your certificate's expiration date. Otherwise, once the certificate expires, you need to update the package with a new valid certificate and once again ensure session hosts trust the certificate chain.
 
 ## Next steps
 

articles/virtual-desktop/fslogix-profile-containers.md

@@ -3,7 +3,7 @@ title: User profile management for Azure Virtual Desktop with FSLogix profile co
 description: Learn about using User profile management for Azure Virtual Desktop with FSLogix profile containers to manage user profiles and personalization.
 author: dknappettmsft
 ms.topic: conceptual
-ms.date: 01/04/2021
+ms.date: 08/22/2024
 ms.author: daknappe
 ms.custom: docs_inherited
 ---
@@ -12,7 +12,7 @@ ms.custom: docs_inherited
 
 A user profile contains data elements about an individual, including configuration information like desktop settings, persistent network connections, and application settings. By default, Windows creates a local user profile that is tightly integrated with the operating system.
 
-A remote user profile provides a partition between user data and the operating system. It allows the operating system to be replaced or changed without affecting the user data. With a VDI solution, such as Azure Virtual Desktop, the operating system may be replaced for the following reasons:
+If you configure a user profile to be remote, it provides a partition between user data and the operating system. You can change or replace the operating system without affecting the user data. With a virtual desktop infrastructure (VDI) solution, such as Azure Virtual Desktop, the operating system might be replaced for the following reasons:
 
 - An upgrade of the operating system.
 - A replacement of an existing session host.
@@ -23,19 +23,17 @@ We recommend using [FSLogix profile containers](/fslogix/concepts-container-type
 > [!NOTE]
 > If you're looking for comparison material about the different FSLogix Profile Container storage options on Azure, see [Storage options for FSLogix profile containers](store-fslogix-profile.md).
 
-
 ## FSLogix profile containers
 
 Existing and legacy Microsoft solutions for user profiles came with various challenges. No previous solution handled all the user profile needs of a VDI environment.
 
 FSLogix profile containers address many user profile challenges. Key among them are:
 
-- **Performance:** The [FSLogix profile containers](/fslogix/configure-profile-container-tutorial/) are high performance and resolve performance issues that have historically blocked cached exchange mode.
-
-- **OneDrive:** Without FSLogix profile containers, OneDrive is not supported in non-persistent VDI environments.
+- **Performance:** [FSLogix profile containers](/fslogix/configure-profile-container-tutorial/) are high performance and can resolve performance issues that historically blocked cached Exchange mode in Microsoft Outlook.
 
-- **Additional folders:** FSLogix profile containers provides the ability to extend user profiles to include additional folders.
+- **OneDrive:** Without FSLogix profile containers, OneDrive isn't supported in non-persistent VDI environments.
 
+- **Additional folders:** you can extend user profiles to include other folders.
 
 ## Best practices for Azure Virtual Desktop
 
@@ -51,17 +49,17 @@ To ensure your Azure Virtual Desktop environment follows best practices:
 
    - Azure Files has limits on the number of open handles per root directory, directory, and file. For more information on the limits and sizing guidance, see [Azure Files scalability and performance targets](../storage/files/storage-files-scale-targets.md#file-scale-targets) and [Azure Files sizing guidance for Azure Virtual Desktop](../storage/files/storage-files-scale-targets.md#azure-files-sizing-guidance-for-azure-virtual-desktop).
 
-- Each host pool VM must be built of the same type and size VM based on the same master image.
+- Each host pool VM must be built of the same type and size VM based on the same VM image.
 
 - Each host pool VM must be in the same resource group to aid management, scaling and updating.
 
 - For optimal performance, the storage solution and the FSLogix profile container should be in the same data center location.
 
-- The storage account containing the master image must be in the same region and subscription where the VMs are being provisioned.
+- The storage account containing the VM image must be in the same region and subscription where the VMs are being provisioned.
 
 ## Next steps
 
-- Learn more about storage options for FSLogix profile containers, see [Storage options for FSLogix profile containers in Azure Virtual Desktop](store-fslogix-profile.md).
+- To learn more about storage options for FSLogix profile containers, see [Storage options for FSLogix profile containers in Azure Virtual Desktop](store-fslogix-profile.md).
 - [Set up FSLogix Profile Container with Azure Files and Active Directory](fslogix-profile-container-configure-azure-files-active-directory.md)
 - [Set up FSLogix Profile Container with Azure Files and Microsoft Entra ID](create-profile-container-azure-ad.yml)
 - [Set up FSLogix Profile Container with Azure NetApp Files](create-fslogix-profile-container.md)

articles/virtual-desktop/index.yml

@@ -9,7 +9,7 @@ metadata:
   ms.topic: landing-page
   author: dknappettmsft
   ms.author: daknappe
-  ms.date: 02/28/2022
+  ms.date: 01/17/2025
 
 # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | sample | tutorial | video | whats-new