Jamf Connect

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.

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.