Skip to content

Deploy Cisco Jabber to Microsoft Intune

webex.commacOSversion 20260917083054

Cisco Jabber is in the PatchBee catalog as a macOS app from webex.com, synced from Homebrew casks. 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

Cisco Jabber as an Intune app

The standard form for a PKG installer (any architecture, scope decided at plan time). 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
macOS app (PKG)
Install
No command: Intune runs the installer package on the Mac.
Uninstall
Removed through the app's bundle identifier.
Detection
Bundle identifier. com.cisco.Jabber, version 20260917083054 or newer.
Requirements
any architecture

Installers in version 20260917083054

ArchitectureTypeScopeHash
any architecturePKG installerscope decided at plan timeSHA-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.

About Cisco Jabber

Jabber client from Cisco

Publisher
webex.com
Source
Homebrew · cisco-jabber
Versions in catalog
3

How this becomes an app in your tenant

Sign in with your Microsoft work account and connect your Intune tenant once. Find Cisco Jabber 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 webex.com ships a new version, PatchBee detects it and rolls it out through your rings, with supersedence and rollback.

Read the step-by-step guide

More macOS apps

Catalog data as of 11 October 2026, from Homebrew casks. 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.