Category filter

Configuration profile to disable iCloud sync for Desktop & Documents folders on Mac

This document explains how to deploy a configuration profile to disable iCloud sync on Mac’s Desktop and Documents folders.

With iCloud Drive, a macOS user can sync files stored in their Desktop and Documents folders with all their Apple devices or access them at iCloud.com from a web browser. While it is a helpful feature, concerns may arise about the corporate data being accessed outside of a company device or the folders taking up excessive iCloud storage space. In such instances, IT admins can utilize a custom configuration profile to disable iCloud sync on Mac for the Desktop and Documents folders. IT admins who wish to remotely deploy the configuration profile to multiple macOS devices enrolled in their organizations can use Hexnode’s Deploy Custom Configuration feature.

Disclaimer:


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

Note:


This configuration profile is supported on macOS 10.12.4 and later devices enrolled in Hexnode.

Disable iCloud sync for Desktop & Documents folders

The device management profile configures the allowCloudDesktopAndDocuments key, which accepts the boolean values, true or false. To disable the iCloud sync for Desktop & Documents folders, the key value has to be set to false.

What happens at the device end?

Upon associating the policy and custom configuration to disable iCloud sync for the Desktop & Documents folders on Mac, the ‘Desktop & Documents Folders’ option (in System Settings > iCloud > iCloud Drive) becomes disabled, preventing users from manually enabling or disabling the sync for these folders.

The configuration profile disabled iCloud sync on Mac's Desktop & Documents folders option

Notes:

  • 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