Skip to content
Atlas AVD+Infrastructure

MSIX App Attach

Upload App Attach packages, assign them to host pools and groups, and publish them to Azure.

MSIX App Attach delivers applications to session hosts as package images instead of installing them into your golden image. Upload an MSIX, CIM, VHD or VHDX package and Atlas stores it in your own Azure Storage account, or point Atlas at an image you already host by its https URL. Assign each package to host pools and Entra groups, and Atlas publishes the package, the host pool references and the user access to Azure for you. Track each package's type, version and state, and remove the ones you no longer need.

Atlas AVD screenshot. All names, metrics and values are demo data.

The problem MSIX App Attach solves

Every application installed into a golden image makes the image bigger, slower to build and more likely to break at the next update. It also puts the application on every host in the pool, when only one department may be licensed to use it. So teams end up with a host pool per department, or an image rebuild every time one vendor ships a patch.

MSIX App Attach is Microsoft's answer: the application lives in a package image on storage and is attached to the user's session at sign-in. Setting it up by hand means creating package resources in Azure, linking them to host pools, granting each group access and keeping all of it in step, across several portal blades.

Key capabilities

Upload an MSIX, APPX, CIM, VHD or VHDX package, stored in your tenant's own Azure Storage account
Or register an image you already host by its https URL
Registry of every package with its type, version, image path and state, with search
Assign packages per host pool and per Entra group from the host pool's settings
Atlas publishes packages, host pool references and user access grants to Azure
Totals for active, in-progress, failed and inactive packages
Remove a package and its assignments in one step, from Azure as well as Atlas
Every registry change recorded in the audit log

How MSIX App Attach works

  1. 1Open App Attach under Administration, or find it from search
  2. 2Upload a package or reference its https URL
  3. 3Assign it to host pools and Entra groups in the host pool's Apps & Automation settings
  4. 4Atlas publishes it to Azure, and session hosts mount the package image when assigned users sign in

The App Attach registry

Atlas keeps one registry of App Attach packages per tenant, on a page titled MSIX App Attach. Open it from search or from the App Attach registry link in a host pool's settings. Register a package in one of two ways. Upload a file, an .msix, .appx, .cim, .vhd or .vhdx of up to 1 GB, and Atlas stores it as a private blob in a storage account in your own subscription, writing with its own identity and Azure role-based access instead of an account key. Or reference an image you already host by its https address.

The registry lists each package with its image path, type, version and state. Tiles above the list count the packages that are active, in progress, failed and inactive, and clicking a tile filters the list to that state. Removing a package removes its assignments and deletes it from Azure as well as from Atlas, so nothing is left behind.

Assigning packages to pools and groups

Registering a package delivers it to nobody. Assignment happens from the host pool: under Settings → Apps & Automation, the MSIX App Attach panel lets you pick a package and choose who gets it, either everyone who signs in to the pool or specific Entra groups. That is what makes one shared pool work for several departments, since the finance application is attached only for the finance group.

When you click Assign, Atlas publishes the package to Azure, links it to the host pool and grants the groups access. Users get the application the next time they sign in to a session host in the pool, with nothing installed on the host and nothing to rebuild. App Attach works alongside the Winget apps Atlas installs at provisioning: keep what everyone needs, and anything that installs drivers or services, on the Winget path, and use App Attach for line-of-business applications, applications that change often and applications only some users should see.

How to set up MSIX App Attach

  1. 1Set up the upload storage account for your tenant, or host the package image on storage your session hosts can already read.
  2. 2Open the MSIX App Attach registry from search and choose Upload a file or Reference a URL.
  3. 3Enter the display name, resource group and location, then register the package.
  4. 4Open the host pool's Settings → Apps & Automation and, in the MSIX App Attach panel, choose the package and who gets it.
  5. 5Click Assign. Users have the application at their next sign-in.

MSIX App Attach: frequently asked questions

What is MSIX App Attach?

A way to deliver applications to Azure Virtual Desktop without installing them on session hosts. The application sits in a package image on Azure storage and is attached to a user's session at sign-in, so re-imaging a host never loses it and updating it means replacing one image.

Which package formats can I register?

You can upload .msix, .appx, .cim, .vhd and .vhdx files of up to 1 GB, or reference a CIM, VHD or VHDX image by its https address. CIM is the format Microsoft recommends. A traditional .msi installer is not an App Attach package; deploy those with Winget or a script.

Can I assign a package to some users in a pool and not others?

Yes. When you assign a package to a host pool you choose everyone who signs in, or one or more Entra groups. Only members of those groups get the application.

Where are uploaded packages stored?

As private blobs in a storage account in your own Azure subscription. Atlas writes to it with its own identity and Azure role-based access, never an account key, and your session hosts read from it the same way.

Can I register a package from a file share path?

No. A package referenced by address must use an https URL; UNC file-share paths are not accepted. If the package only exists on a file share, upload the file instead.

Does Atlas publish App Attach applications as RemoteApps?

Not yet. Atlas publishes the package and grants the pool and the groups access to it. In a RemoteApp host pool, adding the package's applications to the application group is still done in Azure.

Available on

Atlas AVD plan and above

MSIX App Attach is included in every Atlas AVD subscription.