Issues with App Package Creation and App Attach in AVD

Question

Issues with App Package Creation and App Attach in AVD

Tariq Ghouri 25

Trying to create a host pool for remote apps in Azure Virtual Desktop (AVD). During the process of adding an application and moving to the app attach section, three options appear: Start Menu, App Attach, and File Path. When proceeding with app attach, a message regarding app packaging is displayed. The MSIX app packager has been installed to facilitate this, but packaging the app also results in the software being installed on the desktop, which is not the desired outcome. How can the app package be created without it being installed on my local desktop, and how will the package attach with app attach?

Mounika Reddy Anumandla 6,850 Reputation points Microsoft External Staff Moderator

2025-05-06T16:38:20.1433333+00:00

Hi Tariq Ghouri,

I understand that you want to create an MSIX app package without it being installed locally on your desktop. you can try App Attach from Visual Studio. It allows you to create MSIX packages specifically tailored for app attach without installing them on your local machine. This article explains how to create App Attach ready packages using Visual Studio 2022 and publish it to Azure Virtual Desktop. If your app is WinUI 3, this is the best approach. For other app types, use the MSIX Packaging Tool and MSIXMGR for manual packaging and image creation.

Don't package on your local machine. Instead, follow Microsoft’s best practice:

Use a virtual machine (VM) with a clean snapshot to package apps. You can use a clean machine for conversion during the installation step of the MSIX Packaging Tool. https://learn.microsoft.com/en-us/windows/msix/packaging-tool/prepare-your-environment
Then you can Convert MSIX to VHDX and Store VHDX on a File Share. Use Azure Portal to Attach the App.https://learn.microsoft.com/en-us/azure/virtual-desktop/app-attach-create-msix-image?tabs=cim

Hope this helps!

Let me know if you have any further queries!

If the comment is helpful, please click "upvote" to let us know!
Tariq Ghouri 25 Reputation points

2025-05-07T07:58:06.98+00:00
Hi Mounika,

Thanks a lot for your detailed answer. But I still have confusions. First of all below is the list of some of the softwares I want to package.

Postman

Redis Insight

Docker Desktop

Github Desktop

VSCode etc

Chrome

Firefox

Below are my some concerns.

Do I need to create the package for each app separately ?

After creating the package/packages, I need to upload them on storage account ?

And then in Azure in App Attach section I need to attach each package separately in case the package are created separately for each software.

If the package for each software is created separately do i need to revert my azure vm to the fresh installation everytime to package the other software.

I will be creating the VM on Azure for packaging so It can be a separate vm or should be the part of hostpool ?

I will highly appreciate your response for this.
Tariq Ghouri 25 Reputation points

2025-05-08T08:59:14.3566667+00:00

Hi @Mounika Reddy Anumandla

Thanks a lot for your response, unfortunately the above stated solution also didn't work and it's a very long and tiering procedure too. I hope there might be some simple solution for this too. However, I went through the app attach feature of Azure but through that I am getting permission issues on the storage, below is the screenshot of the error when i tried to resolve.
Mounika Reddy Anumandla 6,850 Reputation points Microsoft External Staff Moderator

2025-05-08T09:34:35.4533333+00:00

Hi Tariq Ghouri,

You're absolutely right, the MSIX app attach process can feel complex and tiring, especially when you're starting out. While Microsoft is improving the experience, today’s solution still involves a few moving parts. Focus only on 1 or 2 apps like Chrome or VSCode. Follow the prerequisites and documentation https://learn.microsoft.com/en-us/azure/virtual-desktop/app-attach-overview?pivots=app-attach throughly. Please provide me the screenshot of the error message so that I can assist you further!
Tariq Ghouri 25 Reputation points

2025-05-08T13:07:10.7066667+00:00

Hi @Mounika Reddy Anumandla

Thank you for your prompt response, here you go with the screenshot.
Mounika Reddy Anumandla 6,850 Reputation points Microsoft External Staff Moderator

2025-05-08T15:29:52.0966667+00:00

Hi Tariq Ghouri,

Thank you for your patience and understanding! Truly appreciate your time and effort in reviewing the technical document.
Before you enable identity-based authentication on your storage account, you need to know what identity source you're going to use. It's likely that you already have one, as most companies and organizations have some type of domain environment configured. Consult your Active Directory (AD) or IT admin to be sure. If you don't already have an identity source, you'll need to configure one before you can enable identity-based authentication.

This article explains how you can use identity-based authentication, either on-premises or in Azure, to enable identity-based access to Azure file shares over SMB.
https://learn.microsoft.com/en-us/azure/storage/files/storage-files-active-directory-overview
Also, please go through https://learn.microsoft.com/en-us/azure/virtual-desktop/app-attach-overview?pivots=app-attach#permissions

Hope it helps!

Please tag for any queries!

If the comment is helpful, please click "upvote" to let us know!
Tariq Ghouri 25 Reputation points

2025-05-09T07:28:48.9833333+00:00

Hi @Mounika Reddy Anumandla

Thank you so much for your prompt response. I went through the document but unfortunately we don't have any directory services for now so most probably we have to go through the Golden Image strategy with pre-installed softwares and settings.
Mounika Reddy Anumandla 6,850 Reputation points Microsoft External Staff Moderator

2025-05-09T08:44:32.8966667+00:00

Hi Tariq Ghouri,

Thank you for replying back!

That would be a very practical and smart decision given your current environment. Without directory services (like Entra ID or AD DS), MSIX App Attach becomes more complex to manage, especially around permissions and app lifecycle.

If the information provided is helpful, please Accept answer as a token of appreciation.
Accepted answer will help other community members navigate to the appropriate solutions.

Accepted answer

0 additional answers

Your answer

Mounika Reddy Anumandla 6,850 Reputation points Microsoft External Staff Moderator

2025-05-06T16:38:20.1433333+00:00

Hi Tariq Ghouri,

I understand that you want to create an MSIX app package without it being installed locally on your desktop. you can try App Attach from Visual Studio. It allows you to create MSIX packages specifically tailored for app attach without installing them on your local machine. This article explains how to create App Attach ready packages using Visual Studio 2022 and publish it to Azure Virtual Desktop. If your app is WinUI 3, this is the best approach. For other app types, use the MSIX Packaging Tool and MSIXMGR for manual packaging and image creation.

Don't package on your local machine. Instead, follow Microsoft’s best practice:

Use a virtual machine (VM) with a clean snapshot to package apps. You can use a clean machine for conversion during the installation step of the MSIX Packaging Tool. https://learn.microsoft.com/en-us/windows/msix/packaging-tool/prepare-your-environment
Then you can Convert MSIX to VHDX and Store VHDX on a File Share. Use Azure Portal to Attach the App.https://learn.microsoft.com/en-us/azure/virtual-desktop/app-attach-create-msix-image?tabs=cim

Hope this helps!

Let me know if you have any further queries!

If the comment is helpful, please click "upvote" to let us know!
Tariq Ghouri 25 Reputation points

2025-05-07T07:58:06.98+00:00

Hi Mounika,

Thanks a lot for your detailed answer. But I still have confusions. First of all below is the list of some of the softwares I want to package.

Postman

Redis Insight

Docker Desktop

Github Desktop

VSCode etc

Chrome

Firefox

Below are my some concerns.

Do I need to create the package for each app separately ?

After creating the package/packages, I need to upload them on storage account ?

And then in Azure in App Attach section I need to attach each package separately in case the package are created separately for each software.

If the package for each software is created separately do i need to revert my azure vm to the fresh installation everytime to package the other software.

I will be creating the VM on Azure for packaging so It can be a separate vm or should be the part of hostpool ?

I will highly appreciate your response for this.
Tariq Ghouri 25 Reputation points

2025-05-08T08:59:14.3566667+00:00

Hi @Mounika Reddy Anumandla

Thanks a lot for your response, unfortunately the above stated solution also didn't work and it's a very long and tiering procedure too. I hope there might be some simple solution for this too. However, I went through the app attach feature of Azure but through that I am getting permission issues on the storage, below is the screenshot of the error when i tried to resolve.
Mounika Reddy Anumandla 6,850 Reputation points Microsoft External Staff Moderator

2025-05-08T09:34:35.4533333+00:00

Hi Tariq Ghouri,

You're absolutely right, the MSIX app attach process can feel complex and tiring, especially when you're starting out. While Microsoft is improving the experience, today’s solution still involves a few moving parts. Focus only on 1 or 2 apps like Chrome or VSCode. Follow the prerequisites and documentation https://learn.microsoft.com/en-us/azure/virtual-desktop/app-attach-overview?pivots=app-attach throughly. Please provide me the screenshot of the error message so that I can assist you further!
Tariq Ghouri 25 Reputation points

2025-05-08T13:07:10.7066667+00:00

Hi @Mounika Reddy Anumandla

Thank you for your prompt response, here you go with the screenshot.
Mounika Reddy Anumandla 6,850 Reputation points Microsoft External Staff Moderator

2025-05-08T15:29:52.0966667+00:00

Hi Tariq Ghouri,

Thank you for your patience and understanding! Truly appreciate your time and effort in reviewing the technical document.
Before you enable identity-based authentication on your storage account, you need to know what identity source you're going to use. It's likely that you already have one, as most companies and organizations have some type of domain environment configured. Consult your Active Directory (AD) or IT admin to be sure. If you don't already have an identity source, you'll need to configure one before you can enable identity-based authentication.

This article explains how you can use identity-based authentication, either on-premises or in Azure, to enable identity-based access to Azure file shares over SMB.
https://learn.microsoft.com/en-us/azure/storage/files/storage-files-active-directory-overview
Also, please go through https://learn.microsoft.com/en-us/azure/virtual-desktop/app-attach-overview?pivots=app-attach#permissions

Hope it helps!

Please tag for any queries!

If the comment is helpful, please click "upvote" to let us know!
Tariq Ghouri 25 Reputation points

2025-05-09T07:28:48.9833333+00:00

Hi @Mounika Reddy Anumandla

Thank you so much for your prompt response. I went through the document but unfortunately we don't have any directory services for now so most probably we have to go through the Golden Image strategy with pre-installed softwares and settings.
Mounika Reddy Anumandla 6,850 Reputation points Microsoft External Staff Moderator

2025-05-09T08:44:32.8966667+00:00

Hi Tariq Ghouri,

Thank you for replying back!

That would be a very practical and smart decision given your current environment. Without directory services (like Entra ID or AD DS), MSIX App Attach becomes more complex to manage, especially around permissions and app lifecycle.

If the information provided is helpful, please Accept answer as a token of appreciation.
Accepted answer will help other community members navigate to the appropriate solutions.

Answer 1

Hi Tariq Ghouri,

Thank you for replying back to us again!

App Attach works by mounting a virtual disk (VHD/VHDX/CIM) that contains a single MSIX package, which includes: The app binaries,Dependencies (if included), App manifest and entry points. Each package is treated as a separate application in AVD and must be independently mounted and published.https://learn.microsoft.com/en-us/azure/virtual-desktop/app-attach-create-msix-image?tabs=vhdx Yes, each application must have its own MSIX + VHDX package. Each app will be published individually in AVD under the RemoteApp group.
After you've created the MSIX package, you need to store it on a file share and add the MSIX package to Azure Virtual Desktop.
Yes, that's absolutely correct. In Azure Virtual Desktop (AVD), each MSIX App Attach package must be attached separately even if you created multiple packages for different software.
Follow the best practices recommendations for setting up the MSIX Packaging Tool (or tool of your choice), then create a checkpoint for the VM. This way you can use the VM to convert, revert to your previous checkpoint, and it will be a clean, configured machine ready for conversion again or for verifying your MSIX package converted successfully.

https://learn.microsoft.com/en-us/windows/msix/packaging-tool/prepare-your-environment

App Attach packages should be created before deployment to session hosts. Packaging tools and app installers may modify system state something you want to avoid on production/session hosts. Host pool VMs should remain clean and consistent for users.

Hope it helps!

If you have any further queries, please let me know.

If the information is helpful, please click "upvote" to let us know.

Share via

Issues with App Package Creation and App Attach in AVD

0 additional answers

Your answer