← Blog

Jamf Pro: organise release monitoring before 2027

Created November 15, 2026 · Publication analysed: Jamf, November 10, 2026 · Source checked November 15, 2026.

A release announcement should lead to a traceable IT decision. Jamf’s announced change of channel is an opportunity to check who receives information, who assesses it and who covers an absence.

1. The change confirmed by Jamf

In its November 10 announcement for Jamf Pro 11.34, Jamf says that emails announcing Jamf Pro releases will stop in early 2027. The vendor asks users to sign in to Jamf Nation and select “Release Announcements” through “Subscribe to Updates”. It does not give an exact transition date.

This guide covers the organisation of release monitoring. For the functional changes in that version, see our Jamf Pro 11.34 analysis of SSO and sensitive-action logging.

2. Assign an owner and a deputy

Our recommendation is to assign monitoring to a function, then name an owner and a deputy with their own authorised access. Avoid sharing an account to provide continuity. Check subscriptions in the interface and document the channel, check date and internal recipient.

Also define a periodic check of the official announcements page. This can identify a publication missed by the usual process. Set the frequency according to your risk and resources; this is not presented as a Jamf requirement.

3. Turn an announcement into a decision record

Information to capture

We propose a record containing the official link, publication date, affected product and version, instances to check, assessment owner and next action. Add the latest review date and an explicit status: awaiting assessment, pilot to prepare, action scheduled or no action with a documented reason.

Qualification questions

Does the publication change a workflow you use, a dependency or a security control? Do detailed notes need reviewing? Who validates the business impact? Record uncertainties rather than inferring compatibility from the announcement title alone. Receiving a message does not prove that a version has been assessed.

4. Underside analysis: separate receipt from validation

Our view is that the main weakness lies between information and operational ownership. An individual subscription is insufficient to organise a collective decision. Connect each relevant announcement to your change process: scope, testing, approval and evidence of the outcome.

For a managed Apple fleet, we recommend selecting tests based on the workflows actually used: enrollment with Apple Business Manager and Automated Device Enrollment, administrator access, application distribution or identity integration. This is a proposed checklist, not an announcement of changes to these functions. Identify the network and access requirements for the pilot as well.

5. What this changes for a Belgian or French organisation

For a small business, a shared list with an owner and a deputy may be enough. For a mid-sized business, large enterprise or public body, we recommend a common assessment followed by a decision for each environment. An organisation operating in Belgium and France benefits from keeping a single official source and instructions its teams understand, rather than two monitoring processes that diverge.

If a service provider operates the MDM, specify who monitors announcements and who authorises changes. Ask for evidence of ownership rather than just a forwarded email. Responsibilities should remain explicit even when several teams share operations.

6. Test the process before the transition

Use an existing announcement as an exercise. The deputy should be able to find the source, identify the relevant environment and record a decision without relying on the owner. Then check receipt when the next real announcement arrives; the exercise alone does not demonstrate that the new channel works.

Our proposed acceptance criterion: every relevant announcement has an owner, a dated decision and a next action where necessary. Resolve access issues, missing deputies or approval gaps before adding automation.

Underside, an Apple Business Partner, supports Apple fleet management, security and lifecycle operations in Belgium and France. Discuss your Apple and Jamf operations.

Source : Jamf — Jamf Pro 11.34 Now Available (2026-11-10).

LinkedIn · X · Facebook