Installing and enforcing software updates for Apple devices
Using declarative device management, organizations can configure different aspects of the software update process. This includes managing software update availability, enforcing software updates, enrolling devices into beta programs, and more.
Requiring a minimum version during enrollment
Starting in iOS 17, iPadOS 17, and macOS 14, MDM solutions can enforce a minimum operating system version during Automated Device Enrollment. If the device doesn’t meet the minimum version expected by the mobile device management (MDM) solution, the user is guided through an update before they can complete Setup Assistant. The same process happens automatically when used with Auto Advance. This helps ensure that devices owned by an organization are on the necessary operating system version before being put into production.
Managing the availability of software updates
Organizations may want to control which versions their users can update their devices to. For example, this control can be used to perform verification of an update with a test group before allowing all users to install it in production, or deploy different deferrals to different groups to phase the rollout of recent updates.
Time-based deferrals
Supervised devices can be prevented from offering OTA software updates to users until a specified period of time has passed since they were made publicly available by Apple. For example, say that an iPhone fleet is using iOS 17.3, and a deferred software update configuration of 30 days is applied. In this scenario, users have iOS 17.4 offered to them on their managed devices 30 days after the iOS 17.4 release date.
As part of the configuration, organizations can specify a custom deferral period from 1 to 90 days. For devices with iOS and iPadOS, this delay applies to both operating system updates and upgrades. For Mac computers, they can also specify different deferral periods for operating system updates, upgrades, and non-operating system updates. Non-operating system updates include updates for Safari, XProtect, printer drivers, and Xcode command-line tools. For example, a custom deferral can be used on macOS to defer a software upgrade for longer than a software update.
Note: OTA software updates are typically available for up to 180 days after their initial release date to ensure that an update is always available for managed devices with the maximum deferral value.
Recommended cadence on iOS and iPadOS
In addition to defining time-based deferrals, organizations can define whether users on supervised iPhone and iPad devices have the option to upgrade to a newer, major version or continue on the current one and still receive minor updates, even after an upgrade is available.
For example, on an iPhone using iOS 17.6, one of three options can be used:
Offer users only additional updates to iOS 17.
Offer users only the upgrade to iOS 18.
Allow users the choice: additional updates to iOS 17 (for example, iOS 17.7) or upgrade to iOS 18.
The first option is available for only a limited period of time and allows users to benefit from any important security updates while testing is completed to approve the major upgrade for a production environment.
In conjunction with deferrals, a recommended cadence can be used. In the example above, it could be used to keep devices on iOS 17 while deferring software updates only (like iOS 17.7) for the defined period of time.
Installing software updates automatically
For devices with iOS 18, iPadOS 18, macOS 14, or later, organizations can manage the automatic software update behavior on supervised devices.
Automatic software updates (not upgrades)
For downloading and preparing automatic software updates, the following configuration choices are available:
Let the user choose whether to turn on automatic downloads.
Automatic update downloads are turned off.
Automatic update downloads are turned on.
For installing automatic software updates and upgrades, the following configuration choices are available:
Let the user choose whether to turn on automatic update installation.
Automatic update installations are turned off.
Automatic update installations are turned on.
Note: This option requires automatic downloads to be turned on.
These choices provide granular controls for an organization to define the most suitable automatic software update approach.
For Mac computers, there’s an additional setting with the same three configuration options for security updates, which include updates for XProtect, Gatekeeper, and system data files. For more information, see the Apple Support article About background updates in macOS.
Automatic Rapid Security Responses
Rapid Security Responses don’t adhere to the managed software update deferral. Because they apply only to the latest minor operating system version, if that update is deferred, the Rapid Security Response is also effectively deferred.
Organizations can define whether Rapid Security Responses are automatically applied and specify whether users are allowed to remove them after they’ve been applied.
Requiring authorization by an administrator on macOS
Organizations can change the default behavior to require authorization by a local administrator to install a software update. For example, this can be used in deployments where a device is shared with multiple users to restrict who can perform an update.
Enforcing software updates
Organizations can enforce specific software updates at a chosen time regardless of configured deferrals or if the automatic installation of Rapid Security Responses is turned off. This helps ensure managed devices run a specified version by a certain date and time while allowing users to install the update at a time convenient for them (prior to the enforcement date).
The enforcement date and time are relative to the local time zone of the device. This allows the same configuration to be applied across different regions. For example, if the enforcement date is set to 6 p.m., devices attempt to perform the update at 6 p.m. on the specified date in their local time zone.
When a software update is declared, users are informed about its deadline:
In Settings (iOS and iPadOS) and in System Settings (macOS)
In a notification
Depending on the time left until the enforcement deadline, the notification provides different options (as described below). To allow for increased transparency to users and to keep them informed about the process, additional information about the update can be provided using the “More information” link.
If the user doesn’t immediately begin the installation, the notifications and options shown depend on the remaining time get more frequent leading up to the enforcement date and are meant to encourage the user to install the update at a time convenient for them. To help ensure these notifications are displayed to the user, the Do Not Disturb feature is ignored during the 24 hours prior to the enforcement.
Alternatively, on devices with iOS 18, iPadOS 18, and macOS 15, organizations can set the notifications to be displayed only 1 hour before the enforcement deadline and to show the restart countdown. This reduces the amount of notifications shown on devices—for example, if they aren’t directly assigned to a user (like a kiosk deployment).
To initiate and authorize the update from a notification or from Settings and System Settings, the system prompts the user for their passcode or password.
In case the user hasn’t installed the update before the local enforcement date:
iOS and iPadOS force the user to enter their passcode if one is set (unless it was entered earlier)
macOS force quits all open apps (regardless of whether any documents are open and unsaved) and performs a restart if necessary
On a Mac with Apple silicon, the Mac uses a bootstrap token (if one is available) to authorize the update or the Mac prompts the user for their credentials
To enforce the installation of an update, upgrade, or Rapid Security Response, a device must meet the same requirements as for a user-initiated update of the same type.
A key benefit of declarative device management is the autonomy of devices. Instead of triggering individual actions, the MDM solution declares the desired state and delegates the task to achieve that state to the device itself. A specific example of this behavior is a situation where the software update enforcement date was missed because the device didn’t meet the requirements. The device automatically detects that the declared state hasn’t yet been achieved and resumes the process when it’s connected to the internet.
To do so—if necessary—the operating system downloads and prepares the update and posts another notification letting the user know the install is past due and an attempt is made to perform the installation within the next hour. In case the process gets interrupted again for any reason, the process repeats the next time the device is powered on and connected to the internet.
Using status reports available with declarative device management, MDM solutions can also get increased transparency about the status of the installation—for example, waiting for, downloading and preparing, or installing the update. Meaningful error codes have been added in case the release couldn’t be applied or was unable to be successfully completed. Some examples of this are if the device was offline, if the battery charge was too low, or if not enough free space was available.
Updating iPadOS on Shared iPad
Software updates on Shared iPad devices can be initiated over the air using the MDM solution that the Shared iPad is enrolled in. If the device is physically connected, the Finder or Apple Configurator on a Mac can also be used.
To install an update on Shared iPad, users must be signed out but can be left cached on the device. If the installation requires more free space than what is currently available, cached user account data must be removed. Due to the autonomy of declarative device management, a device keeps retrying to install a new release until it’s successful.
To minimize downtime, updates to a Shared iPad should be scheduled to occur during off hours to minimize impact to users and the network.
For more information, see Updates and upgrades to iPadOS for Shared iPad.