Find Application Bundle IDs for Apple Profiles
What an application bundle ID does
An application bundle identifier uniquely identifies an Apple app to a configuration profile. FileWave can populate the identifier from an App Store search, or you can enter a verified identifier manually. Profile payloads that commonly require bundle IDs include:
- Notifications
- Home Screen Layout
When you need one
Use the bundle ID when a profile must target one specific app—for example, to preset notification behavior or place an app in a managed Home Screen Layout.
Add the app to a profile payload
Search for an App Store app
Taking Notifications as an example, choosing to create a Notifications Payload, a Search box pops up:
| FileWave Central | FileWave Anywhere |
![]() |
The following captured example uses Microsoft Teams. Search results and identifiers may differ for current app releases and distribution channels:
![]() |
On selecting the Store App for Microsoft Teams from the list, the following is shown:
However, in the background FileWave has lifted the Bundle ID from the App Store query and inserted this into the underlying profile:
NotificationSettings = Array {
Dict {
BadgesEnabled = false
ShowInCarPlay = false
ShowInLockScreen = true
AlertType = 1
GroupingType = 0
CriticalAlertEnabled = false
SoundsEnabled = true
BundleIdentifier = com.microsoft.skype.teams
PreviewType = 0
NotificationsEnabled = true
ShowInNotificationCenter = true
}
}
Treat the identifiers in this example as captured values, not permanent Microsoft Teams identifiers. Bundle IDs can differ by platform, app generation, release channel, and distribution method. Verify the identifier for the exact app installed in your environment before deploying the profile.
If the required macOS or iOS/iPadOS app does not appear in the App Store search, enter its verified bundle ID manually.
| FileWave Central | FileWave Anywhere |
Upon entering the Bundle ID into the search box, select the one listed as the Bundle Identifier and accept this.
Re-opening the Payload in the future may show the Bundle ID instead of the App name, where App Store items were previously accepted.
Home Screen Layout is another Payload example which requires a Bundle ID and the search should behave in the same manner, where if found, the App Store version may be selected, otherwise the Application Bundle ID must be added manually into the search box to be selected:
![]() |
Find the bundle identifier in inventory
If the application is installed on a managed device, create an Inventory Report that includes the application name, version, platform, and bundle ID. The illustrated report uses Application > Product ID: its field help identifies the value as the bundle ID on Apple platforms and a UUID on Windows. Do not use a Windows Product ID for an Apple profile. Use a device running the exact app build you intend to target; similar app names do not prove that the identifier is the same.
Read a macOS app’s bundle ID locally
If the Mac app is not yet available in inventory, read CFBundleIdentifier from the app’s own Contents/Info.plist. This is a macOS lookup, not a way to determine an iPhone or iPad app’s identifier from its Mac counterpart. Use the exact app build you intend to manage.
In Terminal on the Mac, this read-only example prints Calculator’s bundle ID without launching the app or changing its files:
/usr/libexec/PlistBuddy -c 'Print :CFBundleIdentifier' "/System/Applications/Calculator.app/Contents/Info.plist"
For that example, the expected value is com.apple.calculator. Replace the quoted path with the full path to your target app’s Contents/Info.plist; keep the quotation marks if the app name contains spaces. Do not copy Calculator’s identifier into a profile for another app. If the file or key is missing, check that you selected the intended application bundle rather than guessing an identifier or modifying the app. A readable identifier proves only the app’s identity, not that a profile setting is supported or applied.
Verify before deployment
- Confirm the bundle ID against inventory from the target platform and app build, or the local macOS app lookup above.
- Deploy the profile to a small pilot group.
- Verify that the intended app receives the setting and that unrelated apps are unchanged.












No comments to display
No comments to display