Deploy MSIX as Intune LOB app

%3CLINGO-SUB%20id%3D%22lingo-sub-2946813%22%20slang%3D%22en-US%22%3EDeploy%20MSIX%20as%20Intune%20LOB%20app%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2946813%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20you%20install%20MSIX%20via%20PowerShell%20Add-AppxPackage%20command%2C%20there%20are%20bunch%20of%20useful%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fappx%2Fadd-appxpackage%3Fview%3Dwindowsserver2019-ps%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Eoptions%3C%2FA%3E%3C%2FP%3E%3CP%3EFor%20example%26nbsp%3B%3CEM%3E-DeferRegistrationWhenPackagesAreInUse%26nbsp%3B%3C%2FEM%3Eis%20really%20nice%20from%20end%20user%20experience%20point%20of%20view.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20you%20put%20your%20MSIX%20package%20to%20Intune%20as%20a%20Line%20of%20Business%20app%2C%20there%20are%20no%20options%20to%20configure%20whatsoever%20and%20you%20cannot%20change%20any%20behavior%20-%20at%20least%20I%20cannot%20find%20any%20options%20to%20for%20example%20include%20the%26nbsp%3B%3CEM%3E-DeferRegistrationWhenPackagesAreInUse.%26nbsp%3B%3C%2FEM%3EWhen%20I%20test%20to%20deploy%20update%20to%20MSIX%20app%20that%20is%20in%20use%20on%20client%2C%20the%20installation%20will%20reboot%20the%20computer%20to%20apply%20the%20update%2C%20which%20I%20cannot%20use%20in%20real%20world.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECurrent%20workaround%20for%20me%20is%20to%20convert%20my%20MSIX%20into%20Win32%20app%20and%20add%20Powershell%20script%20in%20which%20I%20call%20the%20Add-AppxPackage%20command%20with%20desired%20options.%20It%20works%20but%20feels%20like%20an%20overkill.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAm%20I%20doing%20this%20wrong%3F%20Are%20there%20better%20options%20within%20Intune%20so%20I%20don't%20have%20to%20convert%20and%20add%20scripts%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3020713%22%20slang%3D%22en-US%22%3ERe%3A%20Deploy%20MSIX%20as%20Intune%20LOB%20app%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3020713%22%20slang%3D%22en-US%22%3EHi%2C%20%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%20for%20reaching%20out.%20I%20am%20not%20an%20expert%20on%20Intune%20so%20I've%20reached%20out%20to%20the%20product%20team%20there%20and%20am%20working%20to%20get%20an%20answer%20for%20you.%20%3CBR%20%2F%3E%3CBR%20%2F%3EBest%2C%3CBR%20%2F%3ESharla%3C%2FLINGO-BODY%3E
Occasional Contributor

When you install MSIX via PowerShell Add-AppxPackage command, there are bunch of useful options

For example -DeferRegistrationWhenPackagesAreInUse is really nice from end user experience point of view.

 

When you put your MSIX package to Intune as a Line of Business app, there are no options to configure whatsoever and you cannot change any behavior - at least I cannot find any options to for example include the -DeferRegistrationWhenPackagesAreInUse. When I test to deploy update to MSIX app that is in use on client, the installation will reboot the computer to apply the update, which I cannot use in real world.

 

Current workaround for me is to convert my MSIX into Win32 app and add Powershell script in which I call the Add-AppxPackage command with desired options. It works but feels like an overkill.

 

Am I doing this wrong? Are there better options within Intune so I don't have to convert and add scripts?

1 Reply
Hi,

Thanks for reaching out. I am not an expert on Intune so I've reached out to the product team there and am working to get an answer for you.

Best,
Sharla