Category filter

Configuration profile to disable Siri on macOS devices

Siri is Apple’s voice-activated virtual assistant that simplifies and enhances various tasks on Apple devices through natural language voice commands. However, in a work environment consisting of Macs, privacy and security concerns related to Siri can be significant. Siri, if used in noisy environments or, when permitted interactions with third-party applications that require access to sensitive data sources on your Mac, can pose security risks. This may lead IT administrators to consider disabling or restricting its use.

Disabling Siri individually on a fleet of devices can be cumbersome. That’s where Hexnode’s Deploy Custom Configuration feature comes in. Learn how to disable Siri efficiently using a configuration profile through Hexnode.


The configuration profile provided below is adapted from third-party open-source sites.


This configuration profile is supported on devices running macOS 14 and above.

Configuration profile to disable Siri on Macs

In the above configuration profile, the “allowAssistant” key should be set to false to disable Siri. Once the configuration profile is successfully deployed to the device, the settings related to Siri will be greyed out under System Settings, accompanied by a warning message stating, “Use of Siri is restricted”.

Deploying a configuration profile to disable Siri on Mac shows the message

Configuration profile to enable Siri on Macs

In the provided configuration profile, the “Assistant Enabled” key should be set to true to enable Siri. Once the configuration profile is successfully deployed to the device, the “Ask Siri” option under System Settings > Siri & Spotlight will be enabled, and users will not be able to disable it.


  • 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 macOS devices.
  • Ensure that you do not associate conflicting configurations with the devices.
  • Use wildcards to fetch key values from the portal.
  • It is recommended to manually validate the configuration profile execution on a system before executing the action in bulk.
  • Hexnode will not be responsible for any damage/loss to the system on the behavior of the configuration profile.

  • Configuration Profile Repository