You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As an Enterprise Administrator I want to be able to select and deploy WinGet packages directly from Intune like I can with the Microsoft Store for Business. An auto update mechanism exists which helps me to stay current with 3rd party software on my devices.
This is something that would greatly benefit our company as we attempt to manage multiple applications being pushed out via Intune. Having to automate a whole workflow of checking the package version, pulling the new version, if it's MSI then push directly via Intune, else if it's EXE then use the Win32 Content Prep Tool and then pushing via Intune is proving to be quite an endeavor. Looking at Chocolatey, they recommend the internalization of packages (totally understandable), but still, it doesn't fully integrate with Intune. I highly support a WinGet-Intune integration of even the most basic proportion.
Please implement this, packaging is such a time consuming task with all the different types of installers, having access to winget would be a big plus.
Looking forward to having a more first party experience for adding winget entries to the Company Portal similar to the MSStore integration added.
Also would like to see Intune expose a winget REST source that mirrored Company Portal so users can use the cli to pull in things they want. May have some limits based on scoping etc, but have them work better together with fewer registries.
We've provided the full capabilities for Intune to leverage WinGet. We will continue adding new capabilities via the COM APIs as we develop new functionality in Windows Package Manager.
Demitrius Nelon (@denelon) are you aware of a public Issue tracker on the Intune side where we can keep an eye on their progress? Not a winget thing, but I know our biggest issue has been elevating the user context for apps that need it. Moving to machine via SYSTEM context can be done with PATH work, but normal Logs etc I find break in the client.
Yup I think we all use some sort of variant of that today, but it's definitely not a first party option.
Expectation is that it acts more like the experience with Store apps.
I am also trying to figure out if there is a method to use it via the existing COM interface implementation as well. Will still need some scripting, but maybe simplify some of the integration in scripts.
As we migrate more and more customers across to intune from SCCM the need for an easier way to keep applications up to date is getting bigger by the day. Winget is such a great utility for individuals, if it was extended to enterprise administrators it would be a game changer.
Reacted by Matthew Steeples, Justin Rackliffe, Matt Day, Zaintzeko, Andrew Webster, marlana80 and Leon van Ginneken
The funny thing is that the Intune Store integration is done by winget so all the bones are there. What is missing is the ability to input a custom source and ID in Intune then have AgentExecutor do all the rest. There are definitely some other sharp edges like managing updates over time that might need something similar to what Store does, but the basics are all there.
I have had some success with making a factory pattern with posh, but it's much higher cost than it should be. individual intunewin files since there isn't metadata available at ex time, custom update notifications, etc.
Activity
JoshPhillips59 commentedon May 19, 2020
Seconded
pl4nty commentedon May 20, 2020
Related to #151, Intune integration would need DO support (and Microsoft Connected Cache too?)
denelon commentedon May 22, 2020
This looks like it might be similar to #118 and #213. I'm fine keeping this open to look at specific needs for Intune.
nach1man commentedon Oct 1, 2020
This is something that would greatly benefit our company as we attempt to manage multiple applications being pushed out via Intune. Having to automate a whole workflow of checking the package version, pulling the new version, if it's MSI then push directly via Intune, else if it's EXE then use the Win32 Content Prep Tool and then pushing via Intune is proving to be quite an endeavor. Looking at Chocolatey, they recommend the internalization of packages (totally understandable), but still, it doesn't fully integrate with Intune. I highly support a WinGet-Intune integration of even the most basic proportion.
sjansen1 commentedon Aug 4, 2021
Please implement this, packaging is such a time consuming task with all the different types of installers, having access to winget would be a big plus.
denelon commentedon Aug 4, 2021
https://techcommunity.microsoft.com/t5/windows-it-pro-blog/evolving-the-microsoft-store-for-business-and-education/ba-p/2569423
Simpuhl commentedon Jan 25, 2022
2022, any updates on this ?
denelon commentedon Jan 26, 2022
According to the blog post, first half of 2022. It's likely to be closer to the middle of the year.
roconnor04 commentedon Jan 31, 2022
Really hope this comes sooner rather than later.
denelon commentedon Feb 9, 2022
Work is in progress.
Related to:
Romanitho commentedon Apr 19, 2022
To wait for official support, we have this
https://github.com/Romanitho/Winget-Install
larsuhartmann commentedon Jun 8, 2022
Really hoping on this - are there any updates regarding the timeframe we can expect it?
janne-tech commentedon Jul 1, 2022
is there any update intune preview H1 ?
9 remaining items
byjrack commentedon Apr 12, 2023
Looking forward to having a more first party experience for adding winget entries to the Company Portal similar to the MSStore integration added.
Also would like to see Intune expose a winget REST source that mirrored Company Portal so users can use the cli to pull in things they want. May have some limits based on scoping etc, but have them work better together with fewer registries.
denelon commentedon Jun 8, 2023
We've provided the full capabilities for Intune to leverage WinGet. We will continue adding new capabilities via the COM APIs as we develop new functionality in Windows Package Manager.
byjrack commentedon Jun 12, 2023
Demitrius Nelon (@denelon) are you aware of a public Issue tracker on the Intune side where we can keep an eye on their progress? Not a winget thing, but I know our biggest issue has been elevating the user context for apps that need it. Moving to machine via SYSTEM context can be done with PATH work, but normal Logs etc I find break in the client.
denelon commentedon Jun 12, 2023
Justin Rackliffe (@byjrack), I'm not aware of a public issue tracker for them. I'll forward your request and see what we can do here.
SorenLundt commentedon Oct 30, 2023
Would this allow us to install any WIn32App from winget-pkgs repo ?
So far I have been using this to integrate with InTune:
https://github.com/SorenLundt/WinGet-Wrapper
byjrack commentedon Oct 30, 2023
Yup I think we all use some sort of variant of that today, but it's definitely not a first party option.
Expectation is that it acts more like the experience with Store apps.
I am also trying to figure out if there is a method to use it via the existing COM interface implementation as well. Will still need some scripting, but maybe simplify some of the integration in scripts.
Squashed 'src/SfsClient/sfs-client/' changes from be733af9..44d81dc8
Squashed 'src/SfsClient/sfs-client/' changes from be733af9..c639a506
Squashed 'src/SfsClient/sfs-client/' changes from be733af9..0e27525d
b00walk commentedon Mar 11, 2025
As we migrate more and more customers across to intune from SCCM the need for an easier way to keep applications up to date is getting bigger by the day. Winget is such a great utility for individuals, if it was extended to enterprise administrators it would be a game changer.
webstean commentedon Apr 11, 2025
Really long overdue - winget has no future until it is enterprise enabled.
byjrack commentedon Apr 11, 2025
The funny thing is that the Intune Store integration is done by winget so all the bones are there. What is missing is the ability to input a custom source and ID in Intune then have AgentExecutor do all the rest. There are definitely some other sharp edges like managing updates over time that might need something similar to what Store does, but the basics are all there.
I have had some success with making a factory pattern with posh, but it's much higher cost than it should be. individual intunewin files since there isn't metadata available at ex time, custom update notifications, etc.