Skip to content

PatchBee vs packaging Intune apps by hand

The manual route is free, needs no new vendor, and every Intune administrator knows it: find the installer, work out the silent switches, run IntuneWinAppUtil, fill in the Win32 app wizard, write a detection rule, assign, and repeat for every update. It is also where the hours go. The step-by-step guide walks the whole route; this page puts it next to the automated one.

Manual packaging figures checked 11 October 2026 against the sources listed below.

At a glance

Swipe sideways to see both columns.

TopicPatchBeeManual packaging
CostFree under 50 devices; $3 per device per year on ProNo licence; 45 to 90 minutes of an administrator per app, per version (the common community estimate)
Finding the installer6,300+ apps with the publisher's download URL and SHA-256 from winget and HomebrewVendor download pages, enterprise installers found by hand
Silent switchesKnown per installer technology and per manifest; wrapped for zip and portable appsLooked up, guessed, tested on a VM
Detection rulesWritten from the installer, version-aware, shown before publishingWritten by hand; the most common cause of false failures
Building the packageAutomatic (.intunewin, native MSIX, macOS PKG or DMG)IntuneWinAppUtil per version; macOS files uploaded as they are
Publishing and assigningOne action: app, assignments to Entra groups, supersedenceThe Win32 app wizard, page by page
UpdatesDetected nightly, rolled out through rings with auto-approve, supersedence and rollbackEvery step again, for every release, then move the assignments
macOSSame catalog, same console, bundle identity read from the packageA separate manual process with its own tooling
Installer integrityDownloaded from the publisher, SHA-256 verified before packagingManual hash check, or none
Security dataCVE and CVSS on every update, exploited flag from CISA KEVVendor advisories read by hand
Audit trailActivity log, version history per deployed appWhatever Intune's audit log captured

When packaging by hand is the right call

  • You have a handful of apps that rarely change, and a quiet month to do them in.
  • The apps are your own line-of-business installers, which no public catalog carries.
  • Policy forbids a third party publishing into the tenant, even one your administrator consents to with scoped permissions.

When a packaging tool pays for itself

  • You run more than a dozen third-party apps. At one update a month each, the manual route is a day or two of skilled work every month, before anything goes wrong.
  • You manage Macs too, and the Windows process does not carry over.
  • Patch timing matters: a tool that detects the new version at night and starts it through a pilot ring in the morning beats a ticket in a backlog.
  • You want to know what an update fixes and what your devices are exposed to without reading forty advisories.

What does not change

Intune still delivers the app, Intune still evaluates the detection rule, and your tenant is still the source of truth. PatchBee writes the same kind of Win32 app a careful administrator would, shows it in full before publishing, and leaves every field editable. If you stopped using it tomorrow, every app it published would keep working exactly as it is.

Sources

Manual packaging figures are quoted from these public pages as read on 11 October 2026. Vendors change prices and features; if something here is out of date, tell us at contact@patchbee.io and we will correct it.

Try it on your own tenant.

The honest comparison is a real app on a real device. Sign in, connect Intune, package one app. Free forever under 50 devices, no card.