App Attach not working in AVD: Application not appearing on session host

Varthana Chandrasekaran 0 Reputation points
2025-11-18T05:43:27.7266667+00:00

Hello Everyone,

I am currently working on setting up App Attach in Azure Virtual Desktop (AVD) using a Bicep template, but the attached application is not appearing on the session host.

Steps Completed So Far:

  1. Self-Signed Certificate:
  • Created a self-signed certificate using MSIX Hero for the MSIX package.
  1. MSIX Package Creation:
  • Built the MSIX package using the MSIX Packaging Tool.

Converted the package to VHD/VHDX format using MSIX Hero.

  1. Certificate Trust:
  • Trusted the certificate.
  1. VHD Upload and Permissions:
  • Uploaded the VHD to a file share in an Azure Storage Account.
  • The storage account has Identity Access and Storage Key for access.
  • Assigned SMB Reader access to the session hosts for the file share and Reader and Data Access roles to the AVD.

5.App Attach Configuration:

  • Imported the certificate onto the required session hosts.
  • Created the App Attach package from the VHD.
  • Linked the App Attach package to the host pool and added the required assignments.
  • Verified the package shows as Created and Active in the portal.
  • Registration status is Registered.
  • Session Host Health:
    Session host is healthy and shows as available in the host pool.

Issue:

Despite following these steps, the application is still not appearing on the session host when users log in.

Questions:

  1. Are there any additional configuration steps that I may have missed?
  2. Are there known issues with MSIX conversion, storage account access, or App Attach registration that could cause the application not to appear?
  3. Is there a way to better diagnose why the App Attach package is not appearing on the session hosts?

I would appreciate any insights or advice on resolving this issue.

Azure Virtual Desktop
Azure Virtual Desktop

A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.


2 answers

Sort by: Most helpful
  1. Darrell Dortch 1 Reputation point
    2026-06-22T19:45:02.5066667+00:00

    Install the Windows App SDK https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/downloads, reboot and see if that fixes your issue.

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2025-11-18T05:43:49.91+00:00

    It seems like you've followed a comprehensive set of steps to set up App Attach in Azure Virtual Desktop (AVD). Here are some additional considerations and troubleshooting steps that may help resolve the issue with the application not appearing on the session host:

    1. Certificate Trust: Ensure that the self-signed certificate is properly trusted on all session hosts. This includes verifying that the certificate is installed in the Trusted Root Certification Authorities store on each session host. If the certificate is not trusted, the application will not launch.
    2. Application State: Check the application state in the App Attach configuration. Ensure that the application is marked as active. If the application is set to inactive, it will not be available to users.
    3. Session Host Health: Verify the health of the session hosts. If the session hosts are not healthy, it could prevent applications from being mounted properly. You can check the health status using the Azure portal or PowerShell commands.
    4. Log on Blocking vs. On-Demand Registration: If you are using log on blocking registration, consider switching to on-demand registration, which is the recommended method. This can help reduce sign-in time and may resolve issues with application visibility.
    5. Permissions: Double-check the permissions on the file share where the VHD is stored. Ensure that the session hosts have the necessary permissions to access the VHD file. This includes verifying that the SMB Reader access is correctly assigned.
    6. Diagnostics: To diagnose the issue further, you can enable logging for App Attach to gather more information about what might be going wrong during the application registration process. Look for any error messages or warnings in the logs that could indicate the source of the problem.
    7. Known Issues: Review any known issues with MSIX conversion or App Attach registration that might be documented in Azure's resources. Sometimes, specific configurations or updates can lead to unexpected behavior.

    By checking these areas, you may be able to identify the root cause of the issue and resolve it effectively.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.