When the screen was resized, the horizontal dimension in particular has given us some challenges technically. The branding image historically had issues with zooming. As a suggestion, utilizing the secondary header only (keeping the main header blank) for the branding name will allow more characters and render centered next to your branding icon. We are looking to improve the custom naming and exploring font size / number of lines in order to meet needs. I would like to take a small window to talk about some details mentioned in order to hopefully provide some clarity. Product, UX and Engineering are all reading your insights here and discussing next steps. Need assistance identifying the Hosted Data Region of your Jamf Cloud instance? Check out this guide to find out how.įor real-time messages about your upgrade, subscribe to alerts.įor information on what's new in Jamf Pro 10.27, please review the release notes. Your Jamf Pro server, including any free sandbox environments, will be updated to Jamf Pro 10.27 based on your hosted data region below. For additional information about Jamf Pro upgrade paths, see the Incremental Upgrade Scenarios Knowledge Base article.

For instructions, see the Upgrading to MySQL 8.0 Knowledge Base article. Upgrades to Jamf Pro 10.27 or later will fail if you have an older version of MySQL installed you must first upgrade to MySQL 5.7.8 or later (MySQL 8.0 is recommended). Jamf Pro 10.27 includes a database performance enhancement which requires MySQL 5.7.8 or later. Important Note: MySQL recommended for Jamf Pro 10.27 This release also includes Self Service and security updates, as well as a number of improvements to day-to-day workflows. We are staying on top of this, since we have a lot of customers who want what you are aksing as well.We are excited to deliver two significant integrations with the latest version of Jamf Pro including an integration with Azure AD for scoping and authentication and the ability to deploy a Jamf Protect installer package from Jamf Pro. Long story, i know, but just wanted to share what is possible (and workable) for now in our opinion. I am aware that having two MDM solutions is not optimal, but with SSO between the Jamf Pro management console and Azure AD, you can access Jamf Pro settings with your AzureAD credentials (since the latest update). When using Jamf pro you can somehow (yes im the windows guy, not the Apple guy :) ), configure that the user cannot change jamf connect settings. The laptop keeps working if you block the AzureAD account. But users can disable this themselfs, causing issues and I don't really see the point on syncing since you can't control the local account. Its just a account sync that syncs passwords. Jamf Connect on its own, so without Jamf pro, does not work very user friendly in our opinion. We have tested the first part yesterday and will hopefully test the Jamf connect next week. So far, this is the best we could find for now.

When the initial configuration is done, we want to push Jamf Connect to sync the local password with the AzureAD credentials. After that, the user is asked to create a local account on the macbook.

The idea we have now is that we use Azure AD as the identity provider and use the AzureAD credentials to enroll a Macbook (supports MFA) via Apple Business manager. Yesterday we tested the latest Jamf Pro release (10.27.0 - What's New - Jamf Pro Release Notes | Jamf ) that has a better AzureAD integration. We sell and configure multiple MDM solutions and focus moslty on Intune and Jamf and are Windows and Apple specialists. We are having the same issues, but haven't found the best solution.

Jamf pro 10.27 release notes