4.2.3. Apple and Android Updates
💡 First Principle: On mobile platforms Apple and Google, not Intune, decide what an OS update contains and when it's released. Your policy can only shape timing and enforcement around the vendor's schedule. The newer the mechanism — Apple's declarative management, Android freeze periods, OEM firmware services — the more precisely you can shape it.
Apple: declarative device management. Intune now configures Apple updates with Declarative Device Management (DDM), and the traditional MDM-based update policies are deprecated. DDM software updates need iOS/iPadOS 17.0 or later or macOS 14.0 or later, enrolled through Device Enrollment or Automated Device Enrollment. You configure everything in the Settings Catalog, under Declarative Device Management, and there are two enforcement models plus a settings policy:
| Policy | Key settings | Use it when |
|---|---|---|
| Software Update Enforce Latest | Delay in Days, Install Time | You want devices always to reach the newest release, after a delay |
| Software Update (targeted) | Target OS Version, Target Build Version, Target Date Time, Details URL | You need a specific version installed by a specific date |
| Software Update Settings | Who can update, automatic download and install, Rapid Security Response, deferring visibility, notifications, major vs minor | You're shaping the user experience rather than forcing a version |
Delay in Days sets when the deadline is enforced, counted from Apple's posting date or policy creation; it doesn't control when the update is offered. Install Time is 24-hour local time with a leading zero, such as 01:00. So for an update Apple posts on the 3rd, a seven-day delay with an install time of 01:00 sets enforcement for 01:00 local time on the 10th. For targeted updates, if the target build and target OS version disagree, the OS version wins.
At the deadline, a user who hasn't updated gets a one-minute countdown, then a forced install and restart. A device that was off at the deadline gets a one-hour grace period after power-on. While an enforcement is assigned, the device ignores other software update settings.
Reporting needs care. Success in policy reporting means only that the configuration installed, not that the device updated. And once a device runs a later OS than an old policy targets, that policy reports an error — the device sees it as a downgrade attempt — so remove old version policies as you move forward. Update status appears under Reports > Device management > Apple updates, in the Apple software update failures report under Devices > Monitor, and per device. Intune checks Apple for new updates once a day.
Android: system updates and freeze periods. For corporate Android Enterprise devices — dedicated, fully managed and corporate-owned work profile — the System update setting lives in a device restrictions profile (Devices > Manage devices > Configuration > Create > Device restrictions > General):
- Device Default: updates when the device is on Wi-Fi, charging and idle.
- Automatic: installs immediately without user interaction.
- Postponed: delays for 30 days, then Android prompts the user; OEMs or carriers can exempt important security updates.
- Maintenance window: installs in a daily window, retrying for 30 days before prompting. Microsoft suggests it for dedicated or kiosk devices.
Freeze periods block updates entirely for a season. They're available only when System update is Automatic, Postponed or Maintenance window, require Android 9.0 or later, and each period can last up to 90 days. During a freeze, all system updates and security patches are blocked, including manual checks, and recurring periods must be at least 60 days apart. A retailer freezing 1 November to 31 December is freezing for 30 + 31 = 61 days, inside the 90-day limit.
Firmware over-the-air (FOTA). For rugged and Samsung fleets, OEM firmware services go further than the Android setting. Samsung Knox E-FOTA connects at Tenant administration > Connectors and tokens > Firmware over-the-air update > Samsung, supports one Knox E-FOTA account per tenant, and runs campaigns from Devices > Android > Manage updates > Android FOTA deployments that can lock devices to a specific firmware version. Zebra LifeGuard Over-the-Air supports dedicated and fully managed devices only (not corporate-owned work profile), and its deployments are "fire and forget": they can't be edited, include only devices eligible when the deployment was created, don't support assignment filters, and don't allow downgrades. Both carry licensing beyond basic Intune, so check the requirements for the OEM in the scenario. Without FOTA, device restrictions profiles work for every OEM.
⚠️ Exam Trap: A freeze period isn't a gentler version of Postponed — it blocks everything, including security patches and manual update checks, for up to 90 days. If a scenario needs security patches to keep flowing while feature changes wait, a freeze period is the wrong answer.
Reflection Question: You moved iPhones from a policy targeting iOS 26.0 to Enforce Latest, and now the old policy shows errors on hundreds of devices that are fully up to date. Why does it show errors, and what should you do?