AVD August 2026 Update: App Attach Now Supports Multiple User Configuration Files for App-V Packages

Azure Virtual Desktop’s August 2026 updates continue to roll in, and the latest addition is a significant one for organizations navigating the App-V to AVD migration path. Microsoft has added App Attach support for App-V packages that use multiple user configuration files, closing a critical feature gap that has been a migration blocker for many enterprises.

What’s New: Multiple User Configuration File Support for App-V Packages

Azure Virtual Desktop App Attach now natively supports App-V packages that ship with multiple user configuration files. Previously, App Attach only supported a single user configuration file per App-V package, which created a meaningful gap between what App-V Server could do and what App Attach in AVD could handle.

Why This Matters

Many organizations have invested years in building sophisticated App-V package deployments with per-department, per-role, or per-user-group configuration files. A single App-V application might have different user configuration files for:

• Finance users — with specific registry settings and file associations
• Engineering users — with different add-ins and configuration parameters
• Standard users — with a locked-down, minimal configuration
• Power users — with elevated permissions and additional features

Until now, migrating these multi-config App-V packages to AVD App Attach required either repackaging the application to consolidate into a single config file or maintaining separate App Attach packages for each user configuration — both of which added cost, complexity, and risk to migration projects.

The Migration Context

This update lands at a critical time in the App-V lifecycle:

With App-V Server already end-of-support and AVD Classic end-of-support coming in September 2026, organizations are under increasing pressure to migrate. This new feature removes one of the last remaining technical barriers to a straightforward migration.

How App Attach Works with App-V

For those new to App Attach, here’s a quick primer on how it delivers virtualized applications in AVD:

1. Packaging: Applications are packaged as App-V (.appv), MSIX, or AppX packages and stored as disk images (VHD/VHDX/CimFS) on an SMB file share
2. Assignment: Administrators assign packages to host pools and to specific users or groups through the Azure portal
3. Mounting at sign-in: When a user signs in, the package is mounted from the file share — no installation required on the session host
4. Per-user registration: The application registers for the specific user session, respecting their assigned configuration

Key Advantages Over Traditional App-V Server

• No separate App-V Server infrastructure to maintain
• Cloud-native management through the Azure portal
• Per-user, per-app assignment without requiring application groups (for modern App Attach)
• Support for both Entra ID-joined and AD DS-joined session hosts
• Works across Windows 11 multi-session and Windows Server 2025/2022 session hosts

Practical Migration Scenario

Consider a common enterprise scenario: An organization has a line-of-business application virtualized with App-V that serves three departments with different configurations:

Before this update:

• Three separate App Attach packages needed (one per department config)
• Or: repackage to merge configs (potentially breaking functionality)
• Result: Increased management overhead, storage costs, and migration risk

After this update:

• Single App Attach package with all three user configuration files
• App Attach respects the appropriate config file based on user assignment
• Result: Direct migration from App-V Server with minimal repackaging

Best Practices for App Attach with App-V

If you’re planning to migrate App-V packages to App Attach, keep these recommendations in mind:

1. File share placement: Keep the App Attach image file share in the same Azure region as your session hosts for optimal mount performance
2. Antivirus exclusions: Exclude the read-only application disk images from antivirus scanning (including Microsoft Defender) to prevent performance degradation
3. Separate from FSLogix: Use a dedicated file share for App Attach images — don’t combine with FSLogix profile container storage
4. Azure Files considerations: On multi-session hosts, App Attach limits are counted per device, not per user session
5. Health check monitoring: Configure the AppAttachHealthCheck status to catch staging failures early

What This Means for Your AVD Strategy

This update is part of Microsoft’s broader strategy to make App Attach the definitive application delivery mechanism for Azure Virtual Desktop. The trajectory is clear:

• MSIX App Attach (classic) is gone
• App-V Server is end-of-support
• App Attach now supports App-V with multiple configs, Windows Server, and Entra ID-joined hosts
• The migration path from App-V Server to AVD App Attach is now nearly frictionless

For organizations still running App-V Server or procrastinating on AVD migration, the technical barriers are rapidly disappearing. With AVD Classic end-of-support looming in September 2026, now is the time to plan and execute your migration.

Get Started

To start using App Attach with App-V packages in your AVD environment:

1. Navigate to Azure Virtual Desktop in the Azure portal
2. Select App Attach, then + Create
3. Choose your App-V package from an Azure Files storage account or UNC path
4. Assign to host pools and users/groups as needed
5. Configure health check status for monitoring

For detailed setup instructions, see the official App Attach documentation on Microsoft Learn.

Have questions about migrating your App-V workloads to Azure Virtual Desktop? Big Hat Group specializes in Microsoft cloud and AI technologies with 20+ years of Microsoft partnership experience. Reach out to discuss your migration strategy.

Follow Kevin Kaminski on X (Twitter) at https://x.com/kkaminsk for daily Azure and AVD insights.