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?