PatchBee docs
Migrating existing apps
Already have apps in your tenant that PatchBee did not publish? Bring them under management so you get update tracking and rings. Open Migrate; it has two tabs.
Managed apps
Shows every app in your Intune tenant, Windows and macOS alike, each with a badge for its type. Where PatchBee can match an app to its catalog, you can adopt it; from then on it behaves like an app you published: it appears in Deployed Apps and gets update tracking.
Discovered apps
Shows software installed on your devices that is not deployed through Intune at all (from device inventory), with how many devices have it. When PatchBee recognises the app, select Package & deploy to package it and take over its management; this opens the publish flow pre-targeted at your tenant.
Example: standardising an inherited fleet
You take over a tenant with years of history. Under Managed apps, 7-Zip and Chrome were hand-packaged long ago: adopt both, and their versions immediately show against the catalog (both are behind; they appear in Update Candidates). Under Discovered apps, VLC is installed on 60 devices but managed by nobody: Package & deploy takes it over, so the next VLC release is one Approve click instead of a manual repackage. Finish by pointing the adopted apps at a rollout profile, and the inherited mess now patches itself.