Maybe this video from JNUC 2024 can answer some of these questions
You can run Self Service classic and Self Service + in parallel; however, this is only intended for testing purposes.
Jamf Pro already has the option to auto-deploy Self Service+ + as the default and will disable Self Service Classic deployment.
https://learn.jamf.com/en-US/bundle/self-service-plus-documentation/page/Self_Service_Installation.html
Self Service+ is becoming more integrated into Jamf, as opposed to Self Service classic. The Jamf Connect Menu Bar application is now built into it, and other tools and information will be available, such as security and protection info. making it more integrated.
Self Service+ will eventually replace Self Service classic, and support for Self Service classic for macOS will end in March 2026. - https://learn.jamf.com/en-US/bundle/jamf-pro-release-notes-current/page/Deprecations_and_Removals.html
From a user perspective there is very little difference between the Jamf Connect 2.x to Self Service Plus + Jamf Connect 3.x behavior. My biggest problem with this migration is how poorly Jamf notified us and how horribly its documented.
I perceive Self Service+ as a separate application that is not seamlessly integrated into Jamf.
Having two Self Service applications does not seem practical, and again, we would need to provide an explanation to our associates.
Self Service+ is seemlessly intergrated, you just need to make it your default Self Service in Jamf’s settings. Once you check that box, Jamf will automatically remove Self Service and Deploy Self Service+ to your devices and keep it updated.
We have not transitioned to Jamf Self Service+ and Jamf Connect 3.x due to concerns about potential confusion among employees and the need to train them on resetting passwords and utilizing the new Self Service+.
We transitioned 3 months ago, and there has not been a single service desk call. We did not even do a training campaign, just flipped the switches. The menu bar functions more or less as it does with Jamf Connect, Jamfs documentation is all over the place on this which confuses techs more than users. When a users password is coming close to expiring, they get the same menu bar notification and macOS toast notifications that they did with Jamf Connect. The UI is also identical to what it was with Jamf Connect.
Jamf Connect 3.x removes the capability to sync or change passwords via Intune
I’m not sure if I follow this statement. Jamf Connect is what handles password rotation and syncing with Entra if that is your IDP. Intune is not really involved here unless you are using Intune as your MDM, at which point Self Service and Self Service + would not be relevant. Due to API changes on the Microsoft side last year, Intune is not even really involved in comanagement anymore; that is Entra and Jamf with Intune really only holding the token to facilitate the communications.
I’m not sure if I follow this statement. Jamf Connect is what handles password rotation and syncing with Entra if that is your IDP. Intune is not really involved here unless you are using Intune as your MDM, at which point Self Service and Self Service + would not be relevant. Due to API changes on the Microsoft side last year, Intune is not even really involved in comanagement anymore; that is Entra and Jamf with Intune really only holding the token to facilitate the communications.
Yes correct, i did mean Entra, we register with Company Portal to Azure for compliance purposes also...
