Skip to main content

Disabling and Restricting Enablement of Bluetooth with Jamf Pro

Disabling and restricting enablement of Bluetooth with Jamf Pro

Description

This article provides steps to disable Bluetooth or prevent it from being enabled on mobile devices and computers.

Disabling and Restricting Bluetooth Access on iOS

  1. In Jamf Pro navigate to the inventory record of an impacted iOS device and select the Management tab. Click Disable Bluetooth.

  2. Once Bluetooth is disabled, utilize the Modifying Bluetooth settings in a configuration profile or Jamf Pro blueprint to prevent users from modifying their Bluetooth settings.

Disabling/Restricting Bluetooth Access on macOS

There are a few different approaches when restricting Bluetooth on computers. The table below previews the options and nuances to each method.

Option

Locks Settings

Locks Control Center

Locks Menu Bar

Bluetooth Accessories still work?

Requires signing?

Yes

No

No

Yes

No

Yes

Yes

Yes

No

No

Yes

Yes

Yes

No

Yes

Option 1: Jamf Pro Configuration Profile

What this is: Computers > Configuration Profiles > Restrictions: Disable selected items > Bluetooth

What it sets: DisabledPreferencePanes containing com.apple.preferences.Bluetooth, inside a com.apple.systempreferences payload.

Note: This only hides the Settings pane. It does not restrict Bluetooth itself. A user can still turn Bluetooth on or off at any time via Control Center, and Bluetooth accessories continue to pair and work normally.

Configuration steps:

  1. In Jamf Pro, go to a computer configuration profile's Restrictions payload.

  2. Under Preferences > Restrict items in System Preferences, enable Disable selected items.

  3. Check Bluetooth.

  4. Scope to your target computers and Deploy.

Option 2: Jamf Pro Blueprint

What this is: A toggle in the blueprint Restrictions component that sets allowBluetoothModification key.

Requirements: You must meet the hosting, authentication and privilege sets to create blueprints.

Important Note: This sets allowBluetoothModification, which doesn't just lock the toggle but prevents new Bluetooth accessories (headphones, keyboards, drawing tablets) from pairing, since pairing counts as a "modification." Devices paired previously can still connect.

Configuration steps:

  1. In Jamf Pro, create a new Blueprint (or open an existing one you want to apply this to).

  2. Go to the Restrictions component.

  3. Search for Allow modifying Bluetooth settings and set it to False.

  4. Scope the Blueprint to your target computers and Deploy.

Option 3: Signed Custom Configuration Profile

What this is: A manually built .mobileconfig setting the same allowBluetoothModification key. This method would be for customers without Jamf Pro blueprints access (e.g., on-premise Jamf Pro).

Important Note: This sets allowBluetoothModification, which doesn't just lock the toggle but prevents new Bluetooth accessories (headphones, keyboards, drawing tablets) from pairing, since pairing counts as a "modification." Devices paired previously can still connect.

Configuration Steps:

  1. Create a .mobileconfig file containing an allowBluetoothModification key set to false, for the com.apple.applicationaccess payload.

  2. Sign the file and upload to Jamf Pro.

  3. Scope it to a test device and test bluetooth functionality before scoping to production devices.

Expand for an example

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>PayloadContent</key>
<array>
<dict>
<key>PayloadDescription</key>
<string></string>
<key>PayloadDisplayName</key>
<string>Restrictions</string>
<key>PayloadEnabled</key>
<true/>
<key>PayloadIdentifier</key>
<string>GENERATE-A-FRESH-UUID-HERE</string>
<key>PayloadOrganization</key>
<string>Jamf Software, Inc.</string>
<key>PayloadType</key>
<string>com.apple.applicationaccess</string>
<key>PayloadUUID</key>
<string>GENERATE-A-FRESH-UUID-HERE</string>
<key>PayloadVersion</key>
<integer>1</integer>
<key>allowBluetoothModification</key>
<false/>
</dict>
</array>
<key>PayloadDescription</key>
<string></string>
<key>PayloadDisplayName</key>
<string>Restrict Bluetooth Modification System Settings</string>
<key>PayloadEnabled</key>
<true/>
<key>PayloadIdentifier</key>
<string>GENERATE-A-FRESH-UUID-HERE</string>
<key>PayloadOrganization</key>
<string>Jamf Software, Inc.</string>
<key>PayloadRemovalDisallowed</key>
<true/>
<key>PayloadScope</key>
<string>System</string>
<key>PayloadType</key>
<string>Configuration</string>
<key>PayloadUUID</key>
<string>GENERATE-A-FRESH-UUID-HERE</string>
<key>PayloadVersion</key>
<integer>1</integer>
</dict>
</plist>

Note you need to generate PayloadUUID and PayloadIdentifier values for the plist above and sign the profile before upload (example workflow here) in order to enforce the setting.

Did this answer your question?