Product Manager at a tech consulting company with 201-500 employees
Real User
Top 5
Mar 27, 2026
I am using Jamf Connect majorly for password synchronization. The idea behind Jamf Connect is to synchronize passwords between user accounts residing in my directory. This use case helps us to receive fewer tickets from users. Jamf Connect is very simple for us to use, and it is oriented towards productivity. We save time by eliminating a lot of tickets from end users. We also see more productivity from the IT department. Since the cases are reduced on the ticket side, they are more productive and efficient in designing other workflows. This benefits both IT and end users.
Jamf Connect is valuable for new users who are Mac users but have never worked in an Active Directory domain or have independent Macs. Initially, there was skepticism about this feature, but after a couple of weeks, it proved to be a good tool because many users are using multiple devices. They are not bound to one device; sometimes they use one Mac, one Windows, one Mac, one Linux, one Windows. For those kinds of users, it is an awesome solution because it syncs their password across the devices they are using, which was not the case previously. Regarding multi-factor authentication in Jamf Connect, we are already using that in one of the customers, and it is working fine. However, it depends on the MFA provider, not with Jamf Connect itself. Jamf Connect simply integrates with MFA, guiding it to which MFA it needs to connect, and it is there. MFA is kind of separate; it is not a part of Jamf Connect, but we can use MFA with Jamf Connect, and it is working fine. My experience assessing Jamf Connect's integration with cloud identity providers like Okta and Azure AD has been seamless. We got the proper support from Okta, and we did it perfectly fine. Another integration we did with Azure is also fine, and we are looking for another one integrated with Google service.
Senior Endpoint Engineer (macOS/Jamf) at PVH Corp.
Real User
Top 5
Dec 3, 2024
The main use case for Jamf Connect was to synchronize local accounts with the identity provider, like Entra. However, due to some limitations with the enrollment sequence and user limitations, we decided to discontinue using it.
Solution Lead Engineer at a tech vendor with 10,001+ employees
Real User
Top 5
Jun 21, 2024
Normally, I use it for login. As an example, I can log in to my Mac using Jamf Connect. Also, single sign on. We also integrate and complete implementation for new clients.
Jamf Administrator at a financial services firm with 10,001+ employees
Real User
Jul 20, 2023
Jamf Connect is utilized to connect devices to our corporate applications from a single device through the cloud. We have migrated approximately 400 users already, but we still have a few more to go.
Jamf Connect is a tool for authentication. Essentially, macOS devices use it to authenticate with your identity provider for accessing different services. You can use it to connect to your identity provider, such as Azure, and authenticate with your macOS devices using Azure Authenticator. The same applies to other authentication methods, like the one in Google. They enable authentication of macOS devices using the store.
Information Technology System Administrator at General Assembly Space, Inc.
Real User
Jun 8, 2023
Primarily, we wanted to use it as a tool to enable multifactor authentication for our Mac users in both business entities. The goal was to integrate with identity providers such as Microsoft Azure, Okta, and another one that I'm currently blanking on. In addition to multifactor authentication, it also helps retain the credential set in the Jamf Connect tool once you're logged in. This eliminates the need to log in repeatedly across various web applications, as it integrates and sends the necessary messages to the identity provider (IDP). So it's both a user convenience and an enhanced security feature.
Senior Analyst at a tech vendor with 10,001+ employees
Real User
Jun 5, 2023
We use Jamf Connect to provide Azure connectivity with MacOS devices. Azure Active Directory policy changes on Azure are reflected on the MacOS devices and user accounts. About 1,000 users at my organization use Jamf Conect to log in. Around 5 percent cannot use the solution because it's unavailable on their device.
Jamf Connect simplifies deployment and user authentication by integrating seamlessly with Azure AD and Active Directory, providing centralized identity management and minimizing password-related issues.Leveraging its capabilities such as single sign-on, multi-factor authentication, and password synchronization, Jamf Connect enhances security and user management efficiency. Users can easily manage accounts across multiple devices and IDP providers like Okta, benefiting from an intuitive...
I am using Jamf Connect majorly for password synchronization. The idea behind Jamf Connect is to synchronize passwords between user accounts residing in my directory. This use case helps us to receive fewer tickets from users. Jamf Connect is very simple for us to use, and it is oriented towards productivity. We save time by eliminating a lot of tickets from end users. We also see more productivity from the IT department. Since the cases are reduced on the ticket side, they are more productive and efficient in designing other workflows. This benefits both IT and end users.
I use Jamf Connect for identity and access management.
Jamf Connect is valuable for new users who are Mac users but have never worked in an Active Directory domain or have independent Macs. Initially, there was skepticism about this feature, but after a couple of weeks, it proved to be a good tool because many users are using multiple devices. They are not bound to one device; sometimes they use one Mac, one Windows, one Mac, one Linux, one Windows. For those kinds of users, it is an awesome solution because it syncs their password across the devices they are using, which was not the case previously. Regarding multi-factor authentication in Jamf Connect, we are already using that in one of the customers, and it is working fine. However, it depends on the MFA provider, not with Jamf Connect itself. Jamf Connect simply integrates with MFA, guiding it to which MFA it needs to connect, and it is there. MFA is kind of separate; it is not a part of Jamf Connect, but we can use MFA with Jamf Connect, and it is working fine. My experience assessing Jamf Connect's integration with cloud identity providers like Okta and Azure AD has been seamless. We got the proper support from Okta, and we did it perfectly fine. Another integration we did with Azure is also fine, and we are looking for another one integrated with Google service.
The main use case for Jamf Connect was to synchronize local accounts with the identity provider, like Entra. However, due to some limitations with the enrollment sequence and user limitations, we decided to discontinue using it.
The primary use cases of Jamf Connect in my customer's company include the login screen, dual login screen, and integration with Okta IDP.
Normally, I use it for login. As an example, I can log in to my Mac using Jamf Connect. Also, single sign on. We also integrate and complete implementation for new clients.
Jamf Connect can replace the existing IdP and gives better hand holding capability for your devices.
Jamf Connect is utilized to connect devices to our corporate applications from a single device through the cloud. We have migrated approximately 400 users already, but we still have a few more to go.
Jamf Connect is a tool for authentication. Essentially, macOS devices use it to authenticate with your identity provider for accessing different services. You can use it to connect to your identity provider, such as Azure, and authenticate with your macOS devices using Azure Authenticator. The same applies to other authentication methods, like the one in Google. They enable authentication of macOS devices using the store.
Primarily, we wanted to use it as a tool to enable multifactor authentication for our Mac users in both business entities. The goal was to integrate with identity providers such as Microsoft Azure, Okta, and another one that I'm currently blanking on. In addition to multifactor authentication, it also helps retain the credential set in the Jamf Connect tool once you're logged in. This eliminates the need to log in repeatedly across various web applications, as it integrates and sends the necessary messages to the identity provider (IDP). So it's both a user convenience and an enhanced security feature.
We use Jamf Connect to provide Azure connectivity with MacOS devices. Azure Active Directory policy changes on Azure are reflected on the MacOS devices and user accounts. About 1,000 users at my organization use Jamf Conect to log in. Around 5 percent cannot use the solution because it's unavailable on their device.