A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize request, please see:
The ability to pair Patch My PC with local infrastructure to create and update MSIX packages would allow for a single point of reference for application deployment and virtualization with Windows Virtual Desktop.
This suggestion could be interpreted in different ways, as evidenced by the comments so far.
1 - PMPC to enable support for MSIX packages that comes direct from the vendors (like Teams) for publishing into ConfigMgr/Intune. This is being actively worked on.
2 - PMPC to convert EXE/MSI apps to MSIX and offer these in the catalog.
3 - PMPC to support publishing MSIX AppAttach to Azure Virtual Desktop / Citrix / VMware as an alternative publishing destination instead of ConfigMgr / Intune.
4 - PMPC to have the ability to trigger local infrastructure to start an internal automated process of converting an app to MSIX. This would only be achievable by integrating with existing 3rd party platforms designed for this task (of which there are several).
#4 seems the closest to the original request, but I feel many of these votes may be directed to #1. I propose this idea be split up into more specific requests so that we can properly assess customer demand for each feature.
Let's go PMPC...
I see that competitors are getting ahead of you on this front.
+ 999 for PMPC to support publishing MSIX App Attach to Azure Virtual Desktop
This suggestion could be interpreted in different ways, as evidenced by the comments so far.
1 - PMPC to enable support for MSIX packages that comes direct from the vendors (like Teams) for publishing into ConfigMgr/Intune. This is being actively worked on.
2 - PMPC to convert EXE/MSI apps to MSIX and offer these in the catalog.
3 - PMPC to support publishing MSIX AppAttach to Azure Virtual Desktop / Citrix / VMware as an alternative publishing destination instead of ConfigMgr / Intune.
4 - PMPC to have the ability to trigger local infrastructure to start an internal automated process of converting an app to MSIX. This would only be achievable by integrating with existing 3rd party platforms designed for this task (of which there are several).
#4 seems the closest to the original request, but I feel many of these votes may be directed to #1. I propose this idea be split up into more specific requests so that we can properly assess customer demand for each feature.
+999 teams v2 msix
other msix app requests from the UserVoice:
Apple Devices
Microsoft Teams
Upvoting for like requirements with other requested catalog apps as well. (i.e. Keeper Password Manager (x64)).