Deploy DevPod to Microsoft Intune
loftWindowsversion 0.6.15, 10 March 2025
DevPod is in the PatchBee catalog as a Windows app from loft, synced from the Windows Package Manager community repository (winget). Pick it in the App Library and PatchBee writes the deployment plan below, builds the package, publishes it to your Intune tenant and assigns it to the Entra groups you choose. New versions then follow through your update rings.
The plan PatchBee writes
DevPod as an Intune app
The standard form for a MSI (WiX) (x64, per machine). The real plan is generated from the installer when you package, and shown in full before anything is published; every field can be changed.
- Intune app type
- Windows app (Win32), .intunewin
- Install
- msiexec /i "DevPod.msi" /qn /norestart
- Uninstall
- msiexec /x {8D08BD5F-A8B8-4145-8885-70BD20F14383} /qn /norestart
- Detection
- MSI product code. Product code {8D08BD5F-A8B8-4145-8885-70BD20F14383}, version 0.6.15 or newer.
- Requirements
- x64 · per user or per machine
Installers in version 0.6.15
| Architecture | Type | Scope | Hash |
|---|---|---|---|
| x64 | NSIS | per user | SHA-256 published |
| x64 | MSI (WiX) | per machine | SHA-256 published |
PatchBee downloads the installer from the publisher's own URL and verifies its SHA-256 against the catalog before packaging. "None published" means the source carries no hash for this download, so that check has nothing to compare against; packaging still works.
Silent install switches
Recorded for DevPod in its winget manifest. PatchBee uses them as the installer's unattended switches, so the package installs without a click.
- Install location
- INSTALLDIR="<INSTALLPATH>"
About DevPod
DevPod is a client-only tool to create reproducible developer environments based on a devcontainer.json on any backend. Each developer environment runs in a container and is specified through a devcontainer.json. Through DevPod providers, these environments can be created on any backend, such as the local computer, a Kubernetes cluster, any reachable remote machine, or in a VM in the cloud.
You can think of DevPod as the glue that connects your local IDE to a machine where you want to develop. So depending on the requirements of your project, you can either create a workspace locally on the computer, on a beefy cloud machine with many GPUs, or a spare remote computer. Within DevPod, every workspace is managed the same way, which also makes it easy to switch between workspaces that might be hosted somewhere else.
- Publisher
- loft
- Homepage
- devpod.sh/
- License
- MPL-2.0
- Source
- winget · LoftLabs.DevPod
- Versions in catalog
- 22
How this becomes an app in your tenant
Sign in with your Microsoft work account and connect your Intune tenant once. Find DevPod in the App Library, open its plan (the commands, detection rule and requirements above, editable) and publish: PatchBee downloads and verifies the installer, builds the package, creates the Intune app and assigns your groups. When loft ships a new version, PatchBee detects it and rolls it out through your rings, with supersedence and rollback.
Read the step-by-step guideMore Windows apps
Catalog data as of 11 October 2026, from the Windows Package Manager community repository (winget). The product re-reads the source every night and plans against the live catalog, so the version here may already be one behind. Nothing is published to a tenant without an administrator approving the plan.