Bluetooth enforcement in MDM

Currently, the MDM capability is to lock modification of bluetooth. This prevents the user from toggling bluetooth on and off and prevents them from pairing new devices. Our use case is to enforce bluetooth on so that Apple Classroom always works properly, but we do not want to restrict the users from pairing new devices. Our hope is that there will be a way to control bluetooth through the MDM in a similar way to wifi is currently handled. This being an option to force it on(rather than prevent toggling if it is already off), and still allow the user to connect to new networks(in this case pair new devices).


Is this something that is being considered to better support schools using Apple Classroom?

Thanks!

2 years ago, and still now answer on it.

I am also interested in this feature. It should be possible to force bluetooth on, to prevent students from not accessing a classroom class. And keep them the ability to pair their devices.

Actually it is a educational measure, to individualy set the restriction on some devices, if they use this technic often. So they are foreced with bluetooth on, and the loss of new pairing with bluetooth devices.

I came across another problem with Bluetooth. While I can use a Settings command to enable Bluetooth, turning it off via command seems to be an issue. A possible solution for keeping Bluetooth on is to keep sending the enable command repeatedly.

Command is here

Bluetooth no working

In educational environments, we manage iPads using MDM and have a specific requirement regarding Bluetooth that current MDM capabilities do not fully support.

Use Case: We want to enforce that Bluetooth remains enabled at all times, while still allowing users to pair and manage their own Bluetooth accessories (e.g., keyboards, headphones, classroom devices).

Current Limitation: Disabling the MDM setting "Allow modifying Bluetooth settings" prevents users from turning Bluetooth off but also blocks them from pairing new devices or managing their connections.

Leaving the setting enabled allows full user control, including the ability to turn off Bluetooth, which disrupts essential workflows in the classroom.

Expected Behavior (Analogy with Wi-Fi): We are looking for Bluetooth behavior equivalent to Wi-Fi management via MDM:

Wi-Fi can be forced ON via MDM while still allowing the user to connect to any network.

We need the same for Bluetooth: forced ON, but with user flexibility to connect to any accessory.

Why This Matters: In schools, students often turn off Bluetooth unintentionally, leading to unnecessary support overhead.

Preventing all access to Bluetooth settings blocks the use of critical accessories.

A granular setting here would strike the right balance between control and usability.

Feature Request: Please consider adding an MDM restriction that:

Ensures Bluetooth stays enabled (cannot be turned off).

Still allows the user to pair/unpair and manage Bluetooth devices.

This would align perfectly with how Wi-Fi management is currently handled and would be incredibly valuable in supervised/shared device deployments.

Is this something currently under consideration for future iOS releases?

Bluetooth enforcement in MDM
 
 
Q