Skip to main content

Jamf Pro 11.25 Now Available

  • February 17, 2026
  • 10 replies
  • 3281 views
PCalomeni
Forum|alt.badge.img+13

Update 23 February 2026: Standard Cloud upgrades have been rescheduled for the weekend of 6–7 March 2026 (details below). We appreciate your patience with the revised schedule.

 

Today we are releasing Jamf Pro 11.25; highlights include:

Branding Self Service+ for macOS via Jamf Pro

You can change the Self Service+ application name and icon using Jamf Pro and Self Service+ 2.15.0 or later if Self Service+ is set as the default end user application. Previously, modifying Self Service branding settings in Jamf Pro only altered these attributes in the Self Service classic application.

Improvements for OIDC-Based Single Sign-On Through Jamf Account

  • The Jamf Pro login page retains the last-used identity provider (IdP), eliminating the need to reenter an email address. This requires users to allow cookies from jamfcloud.com.
  • Ending a session in any Jamf web app integrated with OIDC-based SSO through Jamf Account will end the same session in Jamf Pro. Likewise, ending a session in Jamf Pro will end the same session in other web apps. This does not end active user sessions for your IdP across other applications.

Hosting Service Discovery Files for Account-Driven Enrollment in Jamf Pro Using the Jamf Pro API

You can use the Jamf Pro API to configure Jamf Pro to host enrollment information for use with account-driven enrollment methods. This eliminates the previous requirement to maintain your own service discovery infrastructure and self-host the JSON files on the same verified domain as your Managed Apple Accounts. Jamf Pro can serve as the fallback service discovery if your organization cannot or prefers not to self-host these files.

 

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 6 March at 1300 UTC 6 March at 1900 UTC
ap-northeast-1 6 March at 1500 UTC 6 March at 2300 UTC
eu-central-1 6 March at 2300 UTC 7 March at 1000 UTC
germanywestcentral Azure 6 March at 2300 UTC 7 March at 0100 UTC
eu-west-2 7 March at 0000 UTC 7 March at 0700 UTC
us-east-1 StateRAMP 7 March at 0500 UTC 7 March at 0900 UTC
us-east-2 7 March at 0500 UTC 7 March at 1400 UTC
central-us Azure 7 March at 0600 UTC 7 March at 0800 UTC
us-west-2 7 March at 0800 UTC 7 March at 1900 UTC

 

 

      10 replies

      sjgrall
      Forum|alt.badge.img
      • sjgrall
      • New Contributor
      • February 17, 2026

      I realize that Self Service classic is deprecated, but was the branding issue fixed in Self Service classic as well? The release notes imply that it was fixed only for Self Service+. We have held back on Self Service+ because the branding wasn’t reliable in the past, so we’ll still have classic in our environment for a bit longer (while we pilot Self Service+) and were hoping it was fixed there too.

       

      “[PI149413] Fixed: Self Service+ and Self Service classic for macOS fail to display branded icons and instead display the default icon. This issue is resolved in Self Service+ for macOS 2.14.0 or later.”

        mvu
        Forum|alt.badge.img+22
        • mvu
        • Jamf Heroes
        • February 17, 2026

        I like.
         

        • The Jamf Pro login page retains the last-used identity provider (IdP), eliminating the need to reenter an email address. This requires users to allow cookies from jamfcloud.com.
          DrewManor
          Forum|alt.badge.img+13
          • DrewManor
          • Employee
          • February 18, 2026

          ​@sjgrall the branding display issue has also been resolved in Self Service classic, with the fix included in Jamf Pro Release 11.25. The classic experience received the same correction in that release.

          Given your phased approach — continuing with classic while piloting Self Service+ — you should be in good shape on both fronts. Please don't hesitate to reach out if the branding issue resurfaces in either experience; we'd want to know right away if it does.

            Jordy-Thery
            Forum|alt.badge.img+15
            • Jordy-Thery
            • Valued Contributor
            • February 18, 2026

            The changes for Account Driven Enrollment sure are nice. 😊

            gzilla13
            Forum|alt.badge.img+4
            • gzilla13
            • Contributor
            • February 25, 2026

            Still seeing issues with Self Service+ holding on to the icon while closed. Seems to eventually fix itself but not on installation of the app

              S
              Forum|alt.badge.img+1
              • surfwolf-FLA
              • New Contributor
              • February 28, 2026

              Ya know what would be really great?  If you sent out updates to the schedule to people subscribed to the update announcements.  We are busy people and don’t check this page every day.

                J
                Forum|alt.badge.img
                • justin.saboo
                • New Contributor
                • March 2, 2026

                The branding issues listed within PI149413 are still an ongoing issue. I’ve had an open ticket with Jamf for the past 2 weeks going over these issues. Branding is still a major issue within Self Service+. Even tested on a computer that doesn’t have Self Service Classic installed.

                 

                So far, their response has been to just go ahead and set Self Service+ as the default app and that “the problems should go away”. However, since these issues have been going on since 1.0, I’m not moving forward with Self Service+ until the issues can be resolved and it can be properly tested without deploying to an entire fleet first.

                  cbanaszak
                  Forum|alt.badge.img
                  • cbanaszak
                  • New Contributor
                  • March 2, 2026

                  The branding issues listed within PI149413 are still an ongoing issue. I’ve had an open ticket with Jamf for the past 2 weeks going over these issues. Branding is still a major issue within Self Service+. Even tested on a computer that doesn’t have Self Service Classic installed.

                   

                  So far, their response has been to just go ahead and set Self Service+ as the default app and that “the problems should go away”. However, since these issues have been going on since 1.0, I’m not moving forward with Self Service+ until the issues can be resolved and it can be properly tested without deploying to an entire fleet first.

                  Branding is still a whole mess for this rollout and you can’t even hide the menu bar icon! We are Pro only customers, I don’t need any Connect functionality in here, but I’m now forced to have another menu bar app for our users that does absolutely nothing.

                    Ondrej_Krupka
                    Forum|alt.badge.img+7

                    Hey everyone,

                    We've seen reports of the Self Service+ icon reverting to the default or appearing as a generic folder after branding is applied. We've investigated and want to share what's going on.

                    macOS maintains a system-wide icon cache for all apps. When Self Service+ applies new branding, the app bundle is updated correctly — but the system cache may still hold the previous icon. While SSP is running it displays the branded icon directly, but when the app is closed the system falls back to the cached (old) icon. This can make it look like SSP "loses" its branding, but the branding itself is intact.

                    The cache eventually refreshes — we've observed it happening after logout, restart, or overnight — but we don't have certainty on exactly when or what triggers the refresh. There is no supported way for apps to force an immediate cache rebuild — this is OS-level behavior that affects all macOS applications.

                    As a workaround, Log out and back in, or restart the Mac. These have been observed to trigger a cache refresh, though the exact timing may vary.

                    Our current findings point to the macOS icon cache as the likely cause, but we're continuing to investigate. If you're seeing this behavior, we'd appreciate your help — please share the following with us:

                    • Steps to reproduce the icon revert (what you did, when the icon changed back)
                    • macOS version of the affected device

                    This data will help us build a case for opening a feedback request with Apple to improve icon cache handling at the OS level. Thank you for your patience and for all the reports that helped us get this far.

                      sara_graves
                      Forum|alt.badge.img+12
                      • sara_graves
                      • Employee
                      • March 4, 2026

                      ​@cbanaszak - just a light mention on the “can’t even hide the menu bar icon,” we hear you and you’re not alone.  We do have this in active development at this time.  

                      Terms & ConditionsCookie settingsAccessibility statement