How to Use Bundle IDs in Jamf Pro — Complete MDM Guide
If you manage company-owned iPhones and iPads with Jamf Pro, you already know that controlling which apps users can install is a core part of mobile device management. Allowlists and blocklists in Jamf are built around one critical piece of data: the app’s bundle ID. Without the correct bundle identifier, your policies won’t match the right apps, and you can end up blocking the wrong thing or failing to allow a required app.
This guide walks you through what Jamf Pro is, how to create app allowlists and blocklists using bundle IDs, where to find bundle IDs (including with the iOS Bundle ID Finder tool), and how to avoid common mistakes.
What Is Jamf Pro?
Jamf Pro is a leading Mobile Device Management (MDM) platform for Apple devices. IT teams use it to enroll iPhones, iPads, and Macs; push configuration profiles; manage apps (including VPP and App Store apps); and enforce security and compliance policies. For iOS and iPadOS, Jamf lets you define which apps are allowed or blocked on managed devices. Those decisions are made using each app’s bundle ID — the unique identifier Apple assigns to every app (e.g. com.spotify.client for Spotify). Jamf uses bundle IDs because they are stable and unique; app names can change or be duplicated, but the bundle ID does not.
Why Bundle IDs Matter in Jamf
Jamf Pro identifies apps by bundle ID, not by display name. When you create an app restriction or allowlist, you enter the bundle identifier. If you enter the wrong one — or a typo — the policy will not apply to the app you have in mind. For example, blocking com.spotify.client blocks Spotify; blocking com.spotify.lite would block a different app if it existed. Using the iOS Bundle ID Finder ensures you get the exact identifier for the app you want to allow or block.
How to Create an App Allowlist in Jamf Pro Using Bundle IDs
An allowlist (whitelist) limits users to only the apps you approve. Here’s how to build one using bundle IDs.
Step 1: Gather the Bundle IDs You Want to Allow
Decide which apps are required or permitted (e.g. Mail, Slack, your company app). For each app, look up its bundle ID. You can use the iOS Bundle ID Finder: search for the app name, select the correct country if needed, and copy the bundle ID from the results. Write down or paste each ID into a list (e.g. in a spreadsheet or text file).
Step 2: Create a Smart Group or Use Restrictions
In Jamf Pro, go to Devices → Configuration Profiles (or Policies depending on your workflow). To restrict which apps can be installed, you typically use an App Restrictions or Allowed Apps payload. Open the payload that lets you specify allowed app bundle IDs.
Step 3: Add Allowed Bundle IDs
In the allowed-apps list, add each bundle ID one per line (or as required by your Jamf version). Example:
com.apple.mobilemailcom.tinyspeck.chatlyio(Slack)com.spotify.client(Spotify, if you allow it)
Save the profile and scope it to the right devices or groups. Once deployed, only apps whose bundle IDs are in this list can be installed (or remain) on managed devices, depending on how your restriction is configured.
Step 4: Test on a Device
Enroll a test device (or use a test group), assign the profile, and verify that only allowed apps can be installed and that blocked or unlisted apps are restricted as intended.
How to Create an App Blocklist in Jamf Pro
A blocklist (blacklist) forbids specific apps. The process is similar: you identify the bundle IDs of the apps you want to block, then add them to the blocklist in Jamf.
- Identify apps to block — e.g. social media, games, or other non-business apps.
- Look up each app’s bundle ID — Use iOS Bundle ID Finder and copy the exact identifier (e.g.
com.burbn.instagramfor Instagram). - Add bundle IDs to the blocklist — In Jamf Pro, open the appropriate restriction profile and add these bundle IDs to the “blocked” or “disallowed” apps list.
- Deploy and test — Scope the profile and confirm that the blocked apps cannot be installed or are removed as expected.
Common Mistakes When Using Bundle IDs in Jamf
- Using the wrong bundle ID — Always verify the ID with a lookup tool or Apple’s App Store / developer resources. A single wrong character means the policy won’t match.
- Blocking or allowing the wrong variant — Some products have multiple apps (e.g. “Facebook” vs “Facebook Lite”). Each has its own bundle ID; make sure you’re targeting the right one.
- Not testing after changes — After updating allowlists or blocklists, test on a device to ensure the intended apps are allowed or blocked.
- Forgetting regional differences — Bundle IDs are usually the same worldwide, but app availability can vary by country. If you manage devices in multiple regions, confirm the app (and its bundle ID) in the correct store.
How to Look Up the Bundle ID for Use in Jamf
You need a reliable source for bundle IDs. The iOS Bundle ID Finder is built for this: enter the app name, choose the country if relevant, and copy the bundle ID from the results. Use it when building or updating Jamf allowlists and blocklists so your MDM policies always reference the correct identifiers.
Summary
In Jamf Pro, app allowlists and blocklists depend on bundle IDs. Use the iOS Bundle ID Finder to get the exact ID for each app, add those IDs to your Jamf restriction profiles, and test on devices to ensure your policies behave as intended. Getting bundle IDs right is the foundation of reliable app control in Jamf.