Jamf Connect Reviews

My main use case for Jamf Connect is for single sign-on. For mobile devices, we use Jamf Connect to sync the IDP password with the local password of the device so that the user only ever has to have one password. Jamf Connect helps the user change their password for the IDP and to sync it with their local password.

The ability to have a single password for the local device and the same password for the IDP is part of our security requirements. Jamf Connect integrates with multi-factor authentication from any IDP and facilitates initial device enrollment. It ensures that when a new user sets up the device, they sign in with their IDP username and password, which then creates the profile on the device. Furthermore, Jamf Connect is now integrated into Jamf Self Service Plus, providing a single dashboard for user password management and allowing users to sync and change their passwords. Additionally, Jamf Connect enhances security by offering two-factor authentication and permitting users to manage or seek help through support features directly within the app.

The integration of Jamf Connect within Self Service Plus has removed the need for multiple apps, consolidating them into one application. However, there is a concern about pricing because Jamf Connect is a separate application that requires additional payment.

I have been working with Jamf Connect for the past four years.

For stability, I would rate it a 10 because we have not had any issues with Jamf Connect.

There is not an issue with scalability; you just have to buy the additional licenses required if your Apple estate increases. Jamf will not stop you from going beyond your required licenses; you will just pay for the overspill when your renewal comes. Therefore, it is very scalable.

There is a support feature within the actual web console where you can chat with technicians in Jamf. They have tier levels of support, and we are currently on the silver tier, which includes a dedicated engineer and a matrix for escalation. I am satisfied with the response time.

When I personally got into Apple device management, Jamf Connect was the first tool that I actually started using because there was none other at the time. We have evaluated other solutions such as InTune, SOTI, and Kandji. Kandji comes closest as it provides a simplified way of managing Apple devices similar to Jamf.

The initial setup process for Jamf Connect is quite simple because it takes information from your IDP. As long as your IDP provides the correct data, it is straightforward. You can also brand it to your organization's requirements.

We did it ourselves. We did not need any integrators to help us with it.

We purchased Jamf Connect directly from Jamf.

We decided to stay with Jamf based on it being the best tool for managing Apple Macs. For iOS devices, InTune could be financially sensible if your organization is embedded into Microsoft, potentially offering free licenses.

I would recommend Jamf Connect if you are interested in having less complexity in password management for users using mobile Apple Macs. It provides security and fully integrates with FileVault encryption, allowing you to encrypt the user profile from device setup. I give this product an overall rating of 9.

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 features of Jamf Connect that I have found most valuable so far include the ability to sync the password with the Active Directory or Azure, and we can provide an option for users to connect to the self-service or get admin rights for a couple of minutes, around half an hour. Those are the two key features which are very awesome and they are working well in the person project.

One area of Jamf Connect that I think could be improved is the recent merger with Self Service Plus, which is a solution we did not want. As a technical person, I do not want to see that because these two are separate things and should be kept as separate. After the integration, they removed the menu bar option for the previous users of Jamf Connect, which is odd for the user because they know where they need to click to sync the password or go to the self-service and other options. However, with the integration of Self Service Plus, it is not there. That is a minus point as of now.

For stability and reliability, I rate this aspect as a ten.

I would rate how scalable Jamf Connect is between nine to ten. The reason I rate it this way is that for premium customers, Jamf gives them the option to delay updates. For normal subscription clients, they push the version updates directly while informing them of the update schedule. For premium users, they ask if they should implement the update this time or wait. I think they should ask every customer beforehand about changes, allowing them to skip one or two versions, but for normal customers, they should at least offer the opportunity to skip two version updates.

I rate the technical support of Jamf between nine to ten, apart from one incident. Regarding the incident I mentioned, I would classify it, but the issue rate them a seven.

Neutral

I usually participate in the initial setup of Jamf Connect. My usual setup process for Jamf Connect involves first discussing with the client and the client technical team if it is available. We ask them how they want the end user to see the tool. We come up with two to three different configurations where certain features are available or not. In the basic one, we publish all the features of Jamf Connect and show them that this is the basic one. This is the one where a user can see limited features. If they are utilizing the self-service, we can include it, or we cannot include it. We also highlight an important part for some customers regarding how often it syncs the password or checks the password, every five minutes, fifteen minutes, or one hour. We bring these kinds of solutions to the front of the customer, showing them the real-time configurations, not a PowerPoint. We explain to them, and occasionally we take parts from different configurations and come up with a customized one for that customer, depending on their needs from an end-user and technical point of view, as well as their MFA solution.

We have a very good team of Jamf admins, and while we initially discuss with them, I would say that once a month, for any client, we open a ticket for Jamf technical support.

After the pandemic, my customers prefer the deployment of Jamf Connect on the cloud. However, for distributions, we prefer that the point should be local depending on the site and the number of devices we manage. Everything is on the cloud, but distribution points could be local.

To be very honest, my experience has been that initially, it was a bit challenging for us as well, but after one integration, we understood everything, and after that, it is seamless for us. However, sometimes clients have different expectations, perhaps based on information they have found on the internet or from someone else. They are seeking that kind of option in Jamf Connect, but if it is not available, we cannot do anything. We explain to them politely that this is not a part of Jamf Connect. We cannot embed it because it is not developed by the vendor's team. We can work on the expectations they have, looking for free or open-source tools or priced ones, where our sales team comes into the picture. Depending on the environment and client requirements, things vary.

A potential challenge for new users of Jamf Connect during the deployment stage, as I have seen, is that initially they face many problems. After our first implementation, we created common questionnaires and steps and, with each version change of Jamf Connect, we prepare documents to float to new users. We inform them about upcoming changes they will notice on their devices, such as the screens they will see, their login credentials, and how often their passwords will change or sync. If their password is mismatched, they will encounter similar screens. After that, they generally understand well. We also provide that document and other technical materials to the service desk teams, so if one hundred users come from a pool of ten thousand, they know what to explain. In rare cases, they need to do troubleshooting because if it is a new configuration, issues are somewhat rare, but in the technical world, they can arise. We explain to the service desk team what they need to do in those scenarios. We have already implemented Jamf Connect in seven different clients without issues reaching us; our service desk team has fixed those issues.

I use Jamf Connect for identity and access management.

Jamf Connect has quite a nice interface, and the password synchronization and SSO elements are particularly good.

The provisioning feature is really helpful because of the single password to sign on, which allows easier account management for new users coming from a Microsoft environment to a Mac. If you were not using Jamf Connect, you would typically have a separate local account password.

The metrics we use to evaluate effectiveness in handling user authentication or access management include fewer reports of issues when accessing devices or signing in, so I would imagine it has been an improvement in that area.

User training has room for improvement.

This improvement would benefit from more documentation, and I would appreciate seeing more automation pieces as well. I do not think there is a massive AI-driven policy with Jamf Connect based on my exposure to it, and that would be an area for improvement.

I believe there could be more AI-driven policy recommendations than Jamf Connect currently offers.

I have been using Jamf Connect for two years.

I do not notice any problems with Jamf Connect versus other solutions, so I would say it works as intended.

I assess the scalability of Jamf Connect as fitting my company requirements with a score of seven.

For technical support, I would rate my experience with an eight.

Positive

I do not think we had another solution in place previously for Mac devices, which is why we switched.

The deployment of Jamf Connect was satisfactory from my understanding; it was not complex or challenging.

About 25 users work with Jamf Connect.

I have seen a return on investment in terms of slight improvement in time.

The improvement probably saves a few hours a week.

Regarding pricing, I would say Jamf Connect falls at an eight on a scale where one is cheap and ten is expensive.

I am a customer and I am fine with being a reference, and I would prefer this review to be fully anonymous.

I would recommend Jamf Connect and advise that if you are looking to manage Mac devices in an Azure environment, it is the perfect tool to help you do that. I would rate this review an eight overall.

Jamf Connect is used for logging in from the Mac to our Okta, or connecting to my organization network, which helps Mac connect with the office network without any VPN.

Whenever we log in to our Mac, it is able to connect with my office network. Jamf Connect also enables password synchronization between my cloud account and my local machine, so whatever password is in my cloud, I can use on my Mac.

Jamf Connect is a simple tool that is helping a lot of Mac users connect to their office credential network.

In my opinion, password synchronization is the best feature Jamf Connect offers.

Password synchronization makes my life easier because we do not have the headache of maintaining a separate password for our office Okta and for Mac. Whatever password we have given for Okta, the same password can be used on my Mac. This helps a lot since we are not bound to create two passwords or remember multiple passwords, as just one password can be used for both Okta and macOS.

Jamf Connect has positively impacted my organization because most of the employees are using Mac, including all the developers, cloud engineers, and the cloud support team, who are using Mac in their day-to-day life. This means the IT team does not need to create accounts for everyone, making Jamf Connect very useful since 80% of our organization employees are using Mac.

It has definitely reduced the IT support burden. I can say that 31% of Mac tickets are password-related, costing an average of 70 or 80 dollars for just one ticket, and that has been drastically reduced with the automation of these tasks through Jamf Connect. IT members do not need to perform password resets, and it has also enhanced our security in our organization, which was further improved by eliminating Active Directory binding after we got Jamf Connect in our organization.

Jamf Connect is pretty good software and well developed. I just wish it would also be available for Windows, but I am not sure if it is there or not.

I have been using Jamf Connect for the past four years.

Jamf Connect is stable.

Jamf Connect's scalability is good. We have around 700 to 900 employees using Jamf Connect, and we are not getting any issues at all.

We never got a chance to talk with the customer support.

I am pretty sure we have just two IT team members who handle Jamf Connect, meaning we do not require many people in the organization to manage Jamf Connect, which is a good savings for us.

My advice to others looking into using Jamf Connect is definitely to go for it. Jamf Connect is a good tool if you are using Mac. I would rate this review a 10.

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.

We previously used Jamf Connect to synchronize local accounts with our identity provider, but we faced challenges due to limitations that prevented us from deploying user-level configuration profiles.

Jamf Connect allowed us to fully customize everything, offering a branded way to change passwords and manage integration with Entra instead of LDAP. However, due to limitations, such as not creating MDM-capable users during pre-stage enrollment and the inability to deploy user-level configuration profiles, we faced challenges.

There is room for improvement with Jamf Connect in reducing its cost and overcoming limitations during pre-stage enrollment, which prevent it from creating MDM-capable users. This limitation affects our ability to deploy user-level configuration profiles.

I have been using Jamf Connect for over a year.

I never contacted technical support because I did not have any issues or questions that required their assistance.

Neutral

We are transitioning to Platform SSO, an open-source tool from Microsoft and Apple, due to Jamf Connect's cost and limitations with user-level configuration profiles.

The initial setup of Jamf Connect was straightforward with clear instructions provided in the documentation. The technical part took about a week, considering change request flows and everything.

The ROI was insufficient due to the per-device license cost for Jamf Connect. Even though we are a large company, the monthly rate for each enrolled device added up quickly.

Jamf Connect requires a per-device license fee, which becomes quite expensive given our large company size. Each device that gets enrolled with Jamf Connect requires a monthly license payment.

We evaluated Platform SSO as an alternative to reduce costs and overcome the limitations we faced with Jamf Connect.

I would recommend Jamf Connect depending on the specific needs of the organization, particularly for those not reliant on user-level configuration profiles. 

I rate the solution six out of ten.

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 am already using Jamf Pro and Jamf Connect together.

We fetch reports very easily, which helps us for audit purposes. We use the reporting function extensively.

We use multi-factor authentication in Jamf Connect.

We provision users via Jamf Connect only.

I am satisfied with the reporting part of Jamf Connect.

I see a potential area of improvement for Jamf Connect from the commercial side, not from the technical side, because technically we do not have any issues. It is majorly the pricing. For the India market, it is very significant. Jamf should work on the pricing front so that it becomes more affordable for customers and adoption will increase for a market like India. India is a huge market for companies, and from that perspective, the price should be very affordable rather than becoming more expensive. Every year they make their product more expensive in India, which makes procurements more complex for us.

Response time is something which Jamf Connect can work on for the India market.

I have been working with Jamf Connect for five to six months.

I would rate the stability of Jamf Connect as nine out of ten.

The scalability ability of Jamf Connect receives a rating of ten out of ten.

I would rate technical support for Jamf Connect as eight.

The initial setup process for Jamf Connect requires first-time hand holding from the experts. Once the Jamf Connect expert explains the process, the knowledge transfer and everything is given properly, and then it is good to go from the IT perspective.

Platform SSO is something which gives direct competition to Jamf Connect. It is a free feature from Microsoft.

We purchased the solution directly from the vendor for Jamf Connect via a Jamf partner. My overall review rating for Jamf Connect is nine out of ten.

The primary use cases of Jamf Connect in my customer's company include the login screen, dual login screen, and integration with Okta IDP.

Jamf Connect has helped by disabling the network login screen, ensuring users only need to enter their password once, which has made the client very happy. This has greatly improved IT security and user management.

Most valuable features of Jamf Connect is its ability to streamline user authentication and identity management for macOS devices. It enables single sign-on (SSO) capabilities, allowing users to log in with their cloud identity credentials (like Azure AD or Okta) instead of traditional local accounts. This not only simplifies the login process but also enhances security by centralizing user management and reducing the risk of password-related issues. Additionally, Jamf Connect supports features like password synchronization and account provisioning, making it easier for IT teams to manage user access across devices.

I have been familiar with Jamf Connect for less than eight years. I recently deployed it, and it is working fine.

Jamf Connect is really useful for security purposes and scalability. It eliminates the need to bind Mac devices to Active Directory, allowing local user and password syncing directly. This makes it more compatible with Apple devices.

The initial setup of Jamf Connect involved thorough planning, and once the configuration policies were created, the deployment was very quick.

I am not involved in the pricing of anything in my current or customer's company.

I would recommend Jamf Connect to companies who do not want to bind their devices to Active Directory due to compatibility issues with Apple devices. Active Directory works, but there are many complications with password syncing and keychains.

I'd rate the solution nine out of ten.

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.

It has a lot of features, but it's still simple to use.

The logs are an area with a shortcoming. The area that needs to be made simpler is while we are checking the logs to see what happened. Overall, it is performing very well for us.

There is one feature called FileVault login, but I'm not sure if it's a macOS limitation or if it is impacting Jamf Connect. I'm not certain about one thing, which is figuring out the behavior of the FileVault restart, like an authenticated restart.

I have been a customer of Jamf Connect for close to three years now. We are using the latest version.

It used to have bugs, but they were quickly resolved. I don't recall it ever breaking down significantly. There might have been a few individual cases, but those were quite rare. I rarely receive requests to fix any broken Jamf Connect because it is quite stable.

There are 2500 users using this solution.

I contacted customer service a time ago about some bug-related issues.

For the setup phase, you have a guide in the middle to guide you through. You can perform a super basic configuration for it, and it will still work. If you want to go super advanced, it can become a bit tricky, but it's not mandatory to do so. The initial setup is not super simple, but it's in the middle.

It does take some time to understand how it functions and to link it with your identity provider because you need to learn about the tool. It's not like you install it and go. You still need to configure it, but afterward, it requires zero maintenance.

It's a good and stable tool, so you should use it if you have a need. It's not complicated. It simply needs to authenticate the user, and it does its job.

Overall, I rate the solution a nine out of ten because it functions as it should. There are practically no issues with it.

In the coming future, Mac will no longer support AD joining. So, what Jamf Connect does is seamlessly connect your Mac to your Azure AD, which is a cloud-based active directory. We use Jamf Connect to encrypt our hard drive, create user accounts, and for zero-touch deployment. Zero-touch means that we can simply hand over the Mac laptop to the user. They can open it, connect to the internet, and log in with their email address and password. At the same time, it will create an account on the Mac and join it to Azure AD. These are the benefits we are getting, and we can do all of this in just a minute.

It used to take around ten to fifteen minutes to join the Mac to the domain, then can restart, then log in with the username, and password. It's a very hefty process, and it's a pretty manual job. 

Now it's much quicker and not a manual job. Within a minute, your hardware will encrypt, your Mac will connect to the domain, and your account will be created with the domain account.

The most valuable feature of Jamf Connect is the Azure AD joining feature. You can seamlessly join your Mac to Azure AD without third-party involvement or support engineer assistance. Normally, an engineer would create an account, generate a password, and give it to the user. But with Jamf Connect, we can simply use the user's email address and password since we create an account on the Mac. That's the benefit.

Moreover, Jamf Connect is a very mature product with lots of documentation. It takes more than a year to study everything about Jamf Connect. It has many configuration options. Jamf Connect also supports other IDP providers like Okta and OneLogin.

Jamf Connect supports not only Azure but also Okta and other IDP providers. It's a very good feature.

In Jamf Connect, during the account creation process, I would like to have a more seamless experience. Currently, after my MFA approval from Azure, it asks me to create a password, which I find unnecessary. I'm not sure if this feature exists or not, but I couldn't find it. This is one thing I need. Additionally, in Jamf Connect, it can be configured with multiple MDMs. In the MDM, if a Mac is joined to Azure, I want the generic Pro console to show that the Mac is joined to Azure in the inventory section. Currently, it shows "no domain account found" in the inventory section even though the Mac is joined to a domain. If Jamf Pro and Jamf Connect can implement this feature, it would be beneficial for inventory purposes.

Another feature I would like to see is the ability for Jamf Connect to continuously remind users to change their password when it expires. Because every company has a policy that every 90 days, the password will be expired, so let's say today my password is expired. Jamf Connect should pop up continuously pop up to enter my password. 

Jamf Connect should continuously pop up to me to enter my password. But that's not happening. When I click on Jami Connect, it shows that my password has expired, but it doesn't prompt me to update it. So normally, users would connect to IT support to reset their password.

The new password is generated, but the issue is that Jamf Connect syncs the password with the machine and Azure AD. So let's say you have your new password. It's updated in Azure AD, but if it's not synced with your Mac, you have two passwords to log in. You have one password for accessing the email and a separate password for the machine. Of course, users can sync it, and it's just a five-second job. But the problem is that users are lazy, so they don't sync it immediately. They say they'll do it tomorrow. If Jamf Connect immediately changes the password, it should give a notification, but notifications can be ignored. But if a pop-up message appeared every thirty minutes or one hour, it would be very annoying for the user. Notifications can be ignored, but pop-ups are very annoying. So they would be forced to enter the new password and sync the old password. Having a persistent pop-up message would ensure users update their passwords promptly.

We are using Jamf Connect and Jamf Pro, both. We have been using it for almost three years. We are currently using version 2.24.

I would rate the stability a ten out of ten. It is very stable. 

I would rate the scalability a ten out of ten. Jamf Connect has changed the way Mac is used. After Jamf Connect, Jamf Pro was released long back, maybe 10 to 15 years ago. But Jamf Connect was previously called Nomad. Nomad was a company created by three friends who developed a small application to sync any password with your Mac and active directory password.

But then, Jamf acquired that company, and within two to three years, they did a wonderful job. Now many organizations are happy to use Mac because of Jamf Connect and the enhancements it brings, such as Azure AD integration and more. In my organization, there are 580 users using Jamf Connect. 

I have been working with this solution since it was launched. It is my bread and butter. So, in the environment where I work, I set up both Jamf Pro and Jamf Connect from scratch.

So the setup is not complicated for me. But sometimes, yes, sometimes I face issues or need some enhancements. Because Jamf and Apple, App Store, and Jamf bring new features with every update. So, sometimes we are not aware of these new features coming in all these files. We need to spend some time studying it. That is the only hurdle for me. Otherwise, I have no issues.

Jamf Connect is not a server, basically. Jamf Connect is simply an application, a tool, like how you use Chrome, Word, Excel, and PowerPoint. It's a tool that is integrated with your Azure cloud. So, one thing to remember is that Jamf Connect will only work on the cloud. Cloud means the IDP provider you are using, like Office 365 for email. So, Office 365, Okta, those should be allowed. But whether it's on-premises or not, it doesn't matter.

So, basically, we deploy Jamf Connect using any MDM tool. You can use any MDM tool to deploy Jamf Connect. In our case, we use Jamf Pro. And once you deploy it, Jamf Pro pushes the application to all users. Then, on the next page, there is a configuration file installed on the machine. The configuration file includes details about your Azure Ready and policies in Azure, such as password expiration every 90 days or getting a notification 15 days before password expiry.

These configurations are pushed to the machine, and Jamf Connect captures them. So, Jamf Connect is not a cloud or something like that. It's simply an application that captures configurations.

Jamf Connect is not cheap. It's not expensive either, but I think they should reduce the price. The reason is there is one more MDM called Kandji, which is still new. They have the same features as Jamf Connect, but it's not as advanced. It's like a passport. They have an application called Passport.

It provides around 15% to 20% of the features of Jamf Connect, and they provide it for free. Like, if you buy both Kandji and Passport, it will be free of cost. If you only buy Passport, it will be a very small amount. But Jamf Connect should reduce the price a little bit, not much. 

There is room for improvement in the pricing model. I would rate the pricing a seven out of ten.

It is an excellent product. I would rate it a ten out of ten. 

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.

We have a test environment where we implement Jamf Connect for new clients as needed. I am primarily involved in the implementation side, so I don't have extensive experience with all the features.

The multifactor authentication process in Jamf Connect is a useful feature, primarily for security purposes. It adds an extra layer of security compared to just entering a password. Our company definitely values and requires multifactor authentication to protect data.

There is room for improvement in the pricing. It could be a little lower.

I have been using it for four to five years now. 

The stability is good. You just need to know some information to use it effectively. It's good for users.

We haven't received any complaints from clients regarding issues with it. So far, it has been good and stable, with no issues.

Jamf Connect's expandability, or its ability to work with other tools and services, is good. I would rate it a ten out of ten. 

I would recommend it for medium-sized companies.

It's not too bad, but there is a delay in response to queries. We don't get responses as quickly as we would like. Compared to other tools like Microsoft, Jamf's support could be improved.

Neutral

I can't compare Jamf Connect with any other product because it's specifically designed for Mac and integrates well with Jamf Pro. It's unique in that aspect.

The initial setup is very simple. I've done it many times. All the documentation is provided by Jamf, so anyone can do it. You just need to understand the background information on how it works.

If everything is clear from the client's end, like with Windows Server and Azure AD, it takes very little time. It's quickest when we have all the necessary information upfront.

Primarily, it's a product for macOS.

It's definitely on the higher side for clients. I would consider it a high price. If it were lower, it would be an improvement.

It is easy to integrate into any existing IT workflow.

I would give the tool itself a ten, but because of the support issues, I would rate it a nine out of ten.