Category filter

Configuration profile to enable/disable AirDrop on macOS devices

Using AirDrop on a macOS device allows users to share files wirelessly with nearby Macs, iPhones, and iPads via Bluetooth and Wi-Fi connectivity. It enables easy transfer of files like photos, videos, documents, websites, etc. However, this convenience raises significant security concerns about potential data leakage. Disabling AirDrop tentatively or permanently can act as a proactive measure to prevent inadvertent sharing of sensitive data and ensure compliance with regulations. If you want to disable AirDrop to address security concerns, you can utilize the configuration profile described below. The custom configuration profile can be executed using Hexnode’s Deploy Custom Configuration feature.


The sample configuration profiles provided below are created using various profile creator applications.

Disable AirDrop

In the provided configuration profile, the key DisableAirDrop is set to true, which instructs macOS to disable the AirDrop feature, thereby preventing users from using it to share files wirelessly between devices.

Re-enable AirDrop

In the provided configuration profile, the key DisableAirDrop is set to false, which instructs macOS to re-enable the AirDrop feature if it has been disabled or blocked.

What happens at the device end?

After deploying the “Disable AirDrop” configuration profile to the macOS devices, the AirDrop option in the Control Center becomes completely greyed out and toggled off, preventing users from accessing it.

Executing the configuration profile disables AirDrop on Mac and the option greys out

The feature can be re-enabled by deploying the “Re-enable AirDrop” configuration profile. This will restore the feature to its normal state, allowing users to access it again.

Use a configuration profile to enable AirDrop on Mac


  • To create and customize configuration profiles, you can use tools like Apple Configurator, Profile Manager or manually create them using text editors.
  • Use non-encrypted .mobileconfig, .xml, or plist files to deploy profiles across devices.
  • Ensure that you do not associate conflicting configurations with the devices.
  • It is recommended to manually validate the configuration profile on a system before executing it in bulk.
  • Hexnode will not be responsible for any damage/loss to the system on the behavior of the configuration profile.

  • Configuration Profile Repository