Noting that you are using Jamf, another approach that I have heard of (and am considering) is using a Self Service policy called “Make Me an Admin”. This is a script written by Jamf Professional Services and published on their Github - https://github.com/jamfprofessionalservices/MakeMeAdminPy
The idea is that during typical usage, no one has admin rights. But if they come across something where they need admin rights, you can use this to temporarily make them an admin. The script has some built-in safety controls to make sure that they don’t create additional local admin accounts or change the password for an existing local admin account. If you don’t want them to use this all the time, you could set the execution frequency on the policy to Once every week (or day or month). Then, you can audit how often a person is requesting admin rights, and have a conversation with them if it gets excessive.
Regarding some of the other specific issues, it’s important to help people understand that part of being in the working world is working within the parameters of your organization. As an example, for some reason (or reasons), your organization made the decision to standardize on Office 365 for productivity and staff collaboration. Maybe not everyone sees that as the right decision, and there may be a point at which your organization decides to change that standard. But the fact is, your organization made that choice, and being a productive, useful member of your organization means you use Office 365. Welcome to being a responsible, functioning adult! Using a non-standard tool will likely make working with your colleagues more difficult, and in fact may make working together to accomplish the mission of your church considerably less effective. Yes, there is room for freedom and choice. But when it comes to the core tools of your ministry (email, productivity suite, church management system, etc.), there is no choice. That is a business decision that your church has made so that you can effectively work together as a staff to grow the Kindgom of God.
The Ferrari metaphor is actually excellent and useful. He is right, not allowing any sort of admin rights is like putting a 65 mph governor on the Ferrari. But there are very few opportunities where you can safely drive the car above 70-80 mph. That’s why there are speed limits, road lines, traffic signs and lights. If you think about it, the only truly safe place you can open up in a Ferrari is on the track. But a track doesn’t get you anywhere. All you are doing is driving in a fancy circle. It doesn’t get you any closer to a destination. Lawfully participating in normal highway traffic is like following the technology guidelines of your organization. A Ferrari of a computer can get you up to highway speeds and into the creative flow quickly. Or you could go over to the track and have a great time doing whatever you want, but the rest of us over here using the organization’s tools to travel towards our mission destination aren’t being helped by that.
Just my (longer than I thought it would be when I started) $0.02. I know the struggle that you are experiencing. We have had similar conversations. We always try our best to turn a “no” into a “yes,” but sometimes due to organizational (NOT IT/Tech department) choices, it has to stay “no.”