Anyone want to share best practice for this? Blueutil doesn’t work as great/possibly at all in our environment after updating to macos 26.
As a workaround I’ve been using the api to send the MDM command in a policy/script to those macs that turn it off. We have an outset login script that manages to lock out bluetooth changing in the control center and system settings, but there’s a short window of 5 seconds or so where students can turn it off before it is locked.
+6Hi,
For keeping Bluetooth enabled on macOS 26, the recommended approach is to use a Configuration Profile to restrict Bluetooth modification — this is officially supported by Apple.
Deploy a Restrictions Profile with allowBluetoothModification set to false:
Requirement: macOS 14 or later (Supervision is not required)
Reference: Device management restrictions for Mac computers - Apple Support
+6Can you post a screenshot of what this looks like? I have only been able to ever accomplish this on iPads.
+6Can you post a screenshot of what this looks like? I have only been able to ever accomplish this on iPads.
You're right — the "Allow Bluetooth modification" option exists in Mobile Device Configuration Profiles, but not in macOS Computer Profiles.
For macOS, you'll need to deploy a Custom Configuration Profile with the allowBluetoothModification key manually.
Here's a ready-made signed profile shared by GabePPS: https://community.jamf.com/general-discussions-2/enable-bluetooth-for-bluetooth-headset-pairing-and-block-rest-29123
(Requires macOS 14+ and the profile must be signed before uploading to Jamf Pro)
+22https://github.com/usnistgov/macos_security/blob/main/rules/system_settings/system_settings_bluetooth_disable.yaml
You can also create a configuration profile to straight force disable or enable Bluetooth.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.