We use the solution for user account authentication and deployment purposes.

The solution provides our customers with a seamless experience logging in with their existing credentials.

The solution's most valuable features are integration with an active directory and ease of deployment.

The solution's UI could be more user-friendly for the setup process.

We have been using the solution for a year.

I rate the solution's stability a ten out of ten.

I rate the solution's scalability a ten out of ten.

The solution's initial setup process is straightforward.

The solution's price is reasonable.

I advise others to use the solution for its support features. I rate it a ten out of ten.

We use the solution for Azure authentication. 

The tool supports different types of authentication. It also integrates seamlessly if you are using other Jamf products. 

We have faced issues with the product's configuration. If we use the tool with other business manager solutions, then there is the issue of naming conventions. The tool needs to be careful with newer updates so that it doesn't break any of the existing configurations. 

I have been using the product for two years. 

I would rate the product's stability a nine out of ten.

I would rate the product's scalability a nine out of ten. 

We contacted the tool's support regarding an issue with configuration and they were not able to trace the exact problem. 

The product's setup requires a lot of team coordination if your organization is big. We need to create applications in Azure AD and grant permissions so that the authentication process works seamlessly. The product's setup is straightforward and fast and depends on the documentation. The solution's deployment took around 10-15 days to complete. 

We pay 2 dollars per device monthly. For the plus version, you have to pay 4 dollars per month. I think the product will give discounts based on the number of users and devices. 

I would rate the solution a nine out of ten. 

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. 

We required a solution during the pandemic to sync user local passwords with IDP passwords.  

The solution needs to improve its licensing. Instead of having separate licensing files for Jamf Pro and Jamf Connect compared to other MDMs. 

I have been working with the product for three years. 

I would rate the solution's stability a ten out of ten. 

I would rate the product's scalability an eight out of ten. My company has around 2000 users for the product. 

You can accomplish setup if you follow the tool's documentation. However, you will need to have three to four configuration profiles. 

I would rate the product a seven out of ten. 

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. 

Jamf Connect is a pretty simple and straightforward tool overall. It has basically two components. First, there's the component that manages the login window experience on macOS, and then there's the component that manages the experience after you log in, integrating with the sites and everything else.

The only real thing that I could say could use improvement is that sometimes there are minor bug issues here and there, which seems to be the case with many Jamf products. They constantly bring out new features and implement many things to support the community. 

However, sometimes they have regressions or bugs that resurface in later versions, which can be frustrating considering the professional-level software you are paying for. It seems like they should be more thorough in their code development and testing. So, overall, it's just a lack of consistent experience sometimes with some of their features. On the flip side, they do provide great support overall.

I have implemented Jamf Connect at two different business entities over three years. So I've been looking into it for about four years in total. I've been familiar with it over the last three years.

It is very stable. The only minor issue I have encountered is that sometimes when new users receive their machines, there is a slight timing issue where our custom wallpaper background image doesn't appear before the Jamf Connect login window. Instead, they briefly see the default macOS login screen. It's a small compliance concern since they didn't see the special image the very first time, but overall, it's not a significant problem.

I would rate the stability a ten out of ten.

Scalability-wise, on a scale from one to ten, I would rate it very high. It's a relatively small client running on your local computer that communicates with your IDP. If you're using an Active Directory solution in-house, it can sync up with that as well. So it's quite flexible in terms of compatibility.

In our organization, around 500 users use Jamf Connect.

The customer service and support are great. If we go back five or more years before they became a publicly traded company, Jamf had excellent support. However, since their big public offering two, three, or maybe four years ago, it feels like they have declined a bit. This is often the case with publicly traded companies, as their objective shifts from providing great products to maximizing shareholder value. So instead of a ten, I would give them an eight. They are still pretty good.

Positive

I would rate my experience with the initial setup a ten out of ten.

We were also implementing Jamf Pro and Jamf Connect for device deployment, specifically for zero-touch device deployment. This way, we can easily send the devices to new users and have them log in with their IDP credentials the first time. However, I encountered one issue, which was more due to my lack of knowledge. When I reached out to support, they couldn't provide a solution for me initially. But once I understood how to do it, the process worked smoothly. I was able to implement it repeatedly while experimenting with different settings to meet my organization's needs and get the job done, especially in the context of zero-touch enrollment, where things can be a bit tricky. It seems like the issue I faced was related to the zero-touch enrollment process and the pre-stage enrollment of pro users. It wasn't a problem with Jamf Connect itself.

In my mind, I was operating under the assumption of running Jamf Connect. I was authenticating to the same Identity Provider (IDP) but through the web view that's built into MacOS's setup process. So, I was wondering why it worked in that setup process but didn't work when I tried to authenticate directly through Jamf Connect. Instead, it redirected to the web view.

I have worked in on-prem organizations, including my current one. The previous organization I worked for used the public cloud. Basically, if you had a Pro DataPoint, you could walk around with a drive and plug it into multiple computers. However, that method is not very efficient in the modern era. It's more convenient to use other mobile device management solutions that work with macOS to deploy it. So it's not dependent on using Jamf's infrastructure, but it works better with their built-in app solution, making it more of a one-click job rather than having to perform multiple tasks yourself to set it up.

It's relatively inexpensive. However, there aren't many other players in this specific space offering what Jamf Connect does. There's an open-source product called NoMAD that was acquired by Jamf, which they rebranded and repackaged as Jamf Connect. Of course, free is great, but NoMAD only provided active directory integration and IDP integration. There are a few plugins available, like Microsoft's login plugin and Apple's deprecated login plugin from a few years ago, which essentially have similar functionality as the modern macOS.

All of those other options were free, but they didn't offer the same breadth of capabilities as Jamf Connect. Additionally, you would still need to pay for the other aspects of those provider services. For example, Microsoft bundled it with other services for users of Azure Office 365. So, up until a few months ago, the Microsoft product was technically in beta and not fully supported for production environments due to potential support limitations. However, it has now been released as a non-beta product, providing full support.

I'll give it a ten. It's a great product. I can't imagine how we could go back to life before we had it in our environment. It simplifies managing our devices, simplifies the user login experience, and improves the quality of service. Users don't have to log in to each and every website individually with their credentials.

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.

The most valuable feature is ease of access. It's convenient to do things like resetting passwords. Previously, users were bound to their domain. We had to bind the user to the domain and log them in through the AD. Now, using Jamf Connect, we don't face any of these challenges. Resetting passwords is hassle-free so we can regularly rotate passwords according to best practices. 

We've had some issues when users restart their devices because the device asks for credentials afterward. Jamf Connect asks for a username, password, and MFA. 

I have worked with three all three Jamf products for the past year: Jamf Pro, Jamf Connect, and Jam Protect.

I rate Jamf Connect eight out of 10 for stability.

I rate Jamf Connect eight out of 10 for scalability.

I rate Jamf support nine out of 10. 

Positive

Deploying Jamf Connect isn't complex. 

I rate Jamf Connect eight out of 10. I like it better than any other MDM I've used for Apple devices.