Yes, if you follow @jbutler47's steps above it will disable any
notification that a background item was added, but not the actual
application notifications. NoMAD will continue to prompt users when
their passwords are mismatched/approaching expiratio...
Here's what I got to finally work. Save the below as a .mobileconfig
file, and then upload it to Jamf after updating your org name. You'll
have to generate new PayloadUUID's with uuidgen in terminal if you use
this as a template for other application...
It's not the same, but the closest thing I could find; Daniel
Maclaughlin gave this talk about disabling Jamf Connect local sign in
via Azure events, I'm sure the workflow is similar enough.
https://www.youtube.com/watch?v=Nvr17J1ON-I and on his gith...
In your Jamf Pro Settings > Global Management > Enrollment Customization
you need to create a New Enrollment Customization Configuration that has
a pane with "Single Sign-on Authentication" This may be helpful:
https://docs.jamf.com/technical-papers/...
