The Problem: Manual App Packaging for Intune
Every IT professional managing Windows endpoints through Microsoft Intune knows the pain: packaging applications manually for deployment. Download the installer, convert it to IntuneWin format, configure detection rules, set up dependencies, upload to Intune — and repeat for every single application. Each app takes 30 to 60 minutes. Multiply that by dozens of applications across your environment, and you are looking at entire days spent on repetitive, low-value work.
For MSPs managing multiple tenants, the problem multiplies further. The same packaging workflow, repeated across every client environment.
What Is IntuneGet?
IntuneGet is a free, open-source tool built by Ugur Koc (UgurLabs) that automates the entire Winget-to-Intune deployment pipeline. It connects the Windows Package Manager repository — over 10,000 applications — directly to Microsoft Intune, turning a 30-minute manual process into a 5-minute automated workflow.
The tool is available as a hosted service at intuneget.com or can be self-hosted via Docker with unlimited users and no seat restrictions.
How It Works
IntuneGet follows a three-step workflow:
- Select Applications (~30 seconds) — Search and choose apps from Winget's 10,000+ package repository. An AI-powered search using OpenAI integration helps find the right Winget ID even with partial or ambiguous queries.
- Package with Winget (2-3 minutes) — The tool automatically downloads and packages selected applications into .intunewin format. No manual conversion required.
- Upload to Intune (1-2 minutes) — Packages are uploaded directly to Microsoft Intune with auto-generated detection rules and pre-verified permissions.
Key Features
Beyond basic deployment, IntuneGet includes several features that make it production-ready for enterprise and MSP environments:
- Automated Update Management — Configurable update policies with four modes: auto_update, notify, ignore, or pin_version. Includes circuit breakers and rate limiting to prevent deployment storms.
- Multi-Channel Notifications — Email and webhook notifications for Slack, Microsoft Teams, Discord, and custom endpoints. Stay informed of deployment status without checking dashboards.
- SCCM Migration — Import existing SCCM application data, match it to Winget packages, and migrate to Intune. A critical feature for organizations transitioning from ConfigMgr to Intune.
- MSP Multi-Tenant Support — Manage multiple Intune tenants from a single instance with batch deployment capabilities.
- Unmanaged Apps Detection — Discover applications in your environment that are not managed through Intune and bring them under management.
- PSADT v4 Support — Integration with PowerShell App Deployment Toolkit version 4 for complex deployment scenarios.
Architecture
IntuneGet runs as a Docker container with an embedded SQLite database. The architecture consists of two components:
- A Next.js web application handling the UI, API, and Intune integration via Microsoft Graph
- A Packager Service running on a Windows machine that handles the actual .intunewin file creation
Authentication is handled through Microsoft Entra ID (formerly Azure AD), and all Intune permissions are verified before any upload begins.
The Broader Ecosystem
IntuneGet is part of a growing suite of Intune automation tools from the same creator:
- IntuneAutomation — Free PowerShell scripts for Intune automation tasks
- IntuneBrew (intunebrew.com) — macOS app deployment via Homebrew integration for Intune
- TenuVault (tenuvault.com) — Intune backup and restore solution
Getting Started
IntuneGet can be used immediately via the hosted version at intuneget.com, or self-hosted using Docker. Self-hosting requires a Microsoft Azure account for Entra ID app registration and a Windows machine for the Packager Service.
Full documentation is available at intuneget.com/docs, and the source code is on GitHub.
