Skip to main content

Jamf Pro 11.23.1 Now Available

  • December 16, 2025
  • 1 reply
  • 236 views

PCalomeni
Forum|alt.badge.img+13

Today we are releasing a maintenance version of Jamf Pro; highlights include:

 

Resolved Issues
Jamf Pro Server
  • [PI122411] Fixed: After making changes to a user level configuration profile that is made available in Self Service, Jamf Pro unexpectedly redistributes the profile when devices update inventory, sometimes resulting in devices losing network access.
  • [PI134378] Fixed: When attempting to upload a file (e.g., configuration profiles, in-house apps, eBooks, certificates) the page refreshes or the Upload dialog closes before the upload is complete.
  • [PI148308] Fixed: The Jamf Pro API endpoint POST /v1/devices/{id}/erase does not clear Activation Lock for computers, despite clearing Activation Lock when erasing computers with a remote command via the Jamf Pro interface.
  • [PI148751] Fixed: Attempting to create or retrieve patch software titles using the /JSSResource/patchsoftwaretitles endpoint of the Classic API results in a 500 Internal Server Error.

 

For additional information on what's included in this release, review the release notes via the Jamf Learning Hub.

To access new versions of Jamf Pro, log into Jamf Account with your Jamf ID. The latest version is located in the Solutions section under Jamf Pro.

 

Cloud Upgrade Schedule

Your Jamf Pro server, including any free sandbox environments, will be updated based on your hosted data region below. Review this guide if you need assistance identifying the Hosted Data Region of your Jamf Cloud instance.

To upgrade manually: Log in to Jamf Account, click View details on the Jamf Pro tile, and then click Upgrade on the appropriate instance. Note: This capability is not available for GovCloud environments and is disabled for all instances one day prior to when the scheduled standard upgrades begin.

Subscribe to product alerts to receive real-time updates.

 

Hosted Region Begins Ends
ap-southeast-2 9 January at 1300 UTC 9 January at 1900 UTC
ap-northeast-1 9 January at 1500 UTC 9 January at 2300 UTC
eu-central-1 9 January at 2300 UTC 10 January at 1000 UTC
germanywestcentral Azure 9 January at 2300 UTC 10 January at 0100 UTC
eu-west-2 10 January at 0000 UTC 10 January at 0700 UTC
us-east-1 StateRAMP 10 January at 0500 UTC 10 January at 0900 UTC
us-east-2 10 January at 0500 UTC 10 January at 1400 UTC
central-us Azure 10 January at 0600 UTC 10 January at 0800 UTC
us-west-2 10 January at 0800 UTC 10 January at 1900 UTC

1 reply

BCPeteo
Forum|alt.badge.img+11
  • Contributor
  • December 16, 2025

Thanks for the quick update!