Azure Multi-Factor Authentication (Discontinued) vs. Jamf Connect

If your solution falls within their standard use case or you have Office 365 - then it makes total sense. If you need a lot of customization or have a really specific business process that causes you to deviate from the standard flow it usually makes more sense to create a custom solution

Incentivized

Jamf Connect is a nice and customizable tool for password change or password sync and account creation during an enrollment process. The configuration is not very easy to understand at the start. Especially if an iDP comes into play and you don't have an idea with Azure or similar services. With Jamf Connect ad bind is dead on macs.

• Ease of use
• Interoperability
• Industry standard

Incentivized

• password sync works very well
• regular updates to Jamf Connect with improvements
• small and simple tool
• Account creation is now on next level after we don't need AD Bind

• It can be difficult to work with when deviating off the standard use cases

Incentivized

• the Jamf configuration app for the config profiles looks not really Jamf-like
• Why are under "Jamf Connect Deployment and Update Settings" in Jamf Pro all possible configuration profiles listed? We have some and I don't think there had to list every!?
• how the Jamf Connect updates work under "Jamf Connect Deployment and Update Settings" is very unclear. i.e. for troubleshooting

Honestly, they are very similar as is much of their offerings. It really comes down to which ecosystem are you already invested in? It doesn't make a lot of sense to try and interop with every cloud vendor - pick one and use them. While there used to be substantial differences in the cloud platforms, they are at basic parity now

Incentivized

• Overall, it's a really good value compared to building a custom solution that you have to maintain

Incentivized

• we need more time to understand how Jamf Connect and the configuration "really" works