Skip to main content

Software update deferrals deprecated?

  • November 11, 2025
  • 2 replies
  • 135 views

Forum|alt.badge.img+14

In the Other changes and Improvements from the release of 11.22 there was a mention that the deferral of updates with some payloads was deprecated with the 26’s and to use Blueprints going forward  However in the Configuration Profiles for both devices and computers it is not stated that this setting is deprecated.  

2 replies

h1431532403240
Forum|alt.badge.img+6

Hi bfrench,

Great observation! You've identified a documentation gap that many admins are noticing. Let me clarify the current situation regarding software update deferrals and deprecation status.

What's Actually Being Deprecated

At WWDC 2025, Apple announced that traditional MDM software update management is deprecated and will be removed in 2026. This includes:

  • MDM software update commands (ScheduleOSUpdate, etc.)
  • The com.apple.SoftwareUpdate payload
  • Legacy restrictions related to software updates
  • MDM software update queries

The Confusion Around Configuration Profiles

You're correct that the Configuration Profile UI in Jamf Pro doesn't explicitly mark these settings as deprecated. This is because:

  1. The underlying payloads still function on current OS versions (iOS/iPadOS 18.x, macOS 15.x)
  2. Deprecation is forward-looking — these settings will stop working on iOS/iPadOS 26 and macOS 26 (Tahoe), expected in late 2026
  3. Jamf's UI hasn't been fully updated to reflect Apple's deprecation timeline

What Should You Use Instead?

Apple and Jamf recommend migrating to Declarative Device Management (DDM) via Jamf Pro Blueprints:

Using Blueprints for OS Update Deferrals:

  1. In Jamf Pro, go to Blueprints in the left sidebar
  2. Create or open a Blueprint
  3. Select Software Update Settings
  4. Click Configure for Deferrals
  5. Set deferral days (1-90) for major and/or minor updates

Important: Jamf recommends setting major and minor deferral values to the same integer (e.g., 30 and 30) to avoid potential rollback issues.

Requirements for Blueprint Deferrals:

  • Enable OIDC-based SSO through Jamf Account
  • tvOS 18.4+, iOS/iPadOS 18+, macOS 15+ (supervision required for iOS/iPadOS/tvOS)

Timeline Summary

Timeframe Status
Now (iOS 18/macOS 15) Legacy payloads still work, but start migrating to DDM
iOS 26/macOS 26 (2026) Legacy payloads deprecated but may still function
iOS 27/macOS 27 (2027) Legacy payloads expected to be completely removed

Jamf Pro 11.22 Context

The Jamf Pro 11.22 release notes mention this deprecation in the "Other changes and Improvements" section. The Configuration Profile settings remain available for backward compatibility, but new deployments should use Blueprints.

Key Takeaway

While the settings aren't marked as deprecated in the Jamf Pro UI, they effectively are for Apple's newer operating systems. The recommendation is:

  1. Start testing Blueprints now for software update management
  2. Plan migration before iOS 26/macOS 26 release (expected Fall 2026)
  3. Keep existing profiles for devices running older OS versions that don't support DDM

References:

Hope this clarifies the situation!


Forum|alt.badge.img+14
  • Author
  • Valued Contributor
  • January 14, 2026

Thanks for this extremely thorough explanation.