Jamf Self Service+ mobile: plan the iPhone and iPad migration
Jamf has made Self Service+ available on Apple mobile devices. Fleets running iOS and iPadOS 17 or later may move to the new app when automatic updates are enabled, while older releases remain on a compatible Self Service version. This transition should be managed as an IT service change, not merely a refreshed interface.
1. What Jamf announced
Jamf Pro 11.31 notes state that Self Service+ for mobile was released on the App Store on July 20, 2026. Jamf documents Self Service+ 12.0.0 or later for iOS and iPadOS 17+, while devices on iOS or iPadOS 15 to 16 remain on Self Service 11.4.2 at most. Older devices receive their latest compatible version.
The change therefore does not impose one application across the entire fleet. It creates coexistence by OS version that inventory, support and operating procedures need to expose. Jamf also states that mobile Self Service does not support single sign-on workflows, so teams should not promise an SSO experience that the documentation excludes.
2. Retain control of the schedule
Eligible devices may move to Self Service+ when automatic updates are active. To control the timing, Jamf directs administrators to select manual Self Service installation in the Jamf Pro iOS settings and disable automatic forced app updates, either globally or on the Self Service app record.
This control supports deployment rings: IT, pilot users, critical business groups, and then general availability. It prevents an interface, sign-in or catalog change from landing on every device at once before support scripts are ready.
3. Validate the complete journey, not just installation
A pilot should verify installation through device-assigned licensing so users are not asked for an Apple Account, catalog access, authentication when required, installation of authorized apps and profiles, in-house app updates, and access to support information.
Negative paths matter too: an out-of-scope device, unavailable license, disabled app, filtered network, older OS release, or user without the expected directory account. Teams need to distinguish a Self Service+ defect from an Apple Business Manager issue, a pending MDM command, or a network restriction.
4. What changes for a Belgian or French organization?
For an SMB, the priority is avoiding two undocumented operating procedures based on device age. For a mid-market company, large enterprise, or public institution active in Belgium and France, the rollout needs FR/EN guidance, a representative pilot, and a clear matrix linking OS version, Self Service version, and available capabilities.
IT leaders should connect the migration to the iPhone and iPad support lifecycle. Security teams need to validate authentication paths and app assignments without attributing undocumented SSO capabilities to Self Service+. Support teams require screenshots, labels, and procedures for the two app generations that may coexist.
5. Underside analysis: manage the portal as an internal product
Our view is that Self Service+ is becoming a significant front end for mobile IT services. Quality is not the number of icons displayed; it is the successful installation rate, the time required to access a business app, and the number of tickets users need to complete an autonomous action.
This migration complements the governance of the Apple managed app catalog: Apple supplies distribution mechanisms and Jamf structures the experience, but the organization remains accountable for licensing, scope, copy, support, and evidence.
6. Recommended action plan
- Inventory iOS and iPadOS releases and the installed Self Service version.
- Review manual or automatic installation and forced-update policy.
- Build a pilot covering recent devices, older releases, and critical roles.
- Test device licensing, catalog, authentication, in-house apps, profiles, and support links.
- Update FR/EN procedures and communications before each rollout ring.
- Measure installation success, lead times, and tickets before broad deployment.
Goal: evolve mobile self-service without turning an app update into a catalog, identity, or support outage.
Plan your Jamf migrationOfficial sources: Jamf Pro 11.31.0 — Notice History by Release, Self Service Version Requirements, and Self Service for Mobile Settings in Jamf Pro.