Discussion

Managing macOS Sequoia and Sonoma Privacy Permissions at Enterprise Scale

0 helpful
14 replies

Hi everyone,

As macOS environments continue to expand in enterprise IT infrastructure, managing Privacy & Security settings (TCC / System Extensions) across remote fleets is becoming a growing challenge.

While MDM profiles (PPPC) handle most app permissions smoothly, recent macOS updates have introduced tighter user-prompt restrictions around screen recording, local network access, and background items that often trigger unexpected prompts for end-users—even when profiles are properly deployed.

I’d love to hear how other IT admins and sysadmins are handling this balance:

  1. Are you enforcing zero-touch configurations via declarative device management (DDM)?

  2. How are you dealing with non-standard developer tools or internal software that require elevated security permissions?

  3. What MDM solutions (Jamf, Kandji, Intune, etc.) are giving you the smoothest compliance workflows for macOS lately?

Looking forward to hearing your strategies and best practices!

Reply

14 replies

by oliviaparker09

We’ve had good results with a layered approach: use MDM/PPPC for standard permissions and DDM where supported, while keeping exceptions for internal tools tightly scoped. For developer apps, clear documentation and testing on each macOS release are especially important. Jamf and Intune both seem worth evaluating depending on the existing environment.

by Freevpnmac

I’ve found that the biggest challenge is keeping the security experience consistent for users while still allowing the tools they actually need. For non-standard applications, it seems especially important to test PPPC and system extension configurations before deploying them broadly, since newer macOS versions can introduce additional prompts.

For remote Mac fleets, I’d also pay attention to network security alongside the MDM configuration. A VPN can be useful when employees are accessing company resources or working from untrusted/public networks, but it should complement—not replace—proper MDM and endpoint security controls.
I’d be interested to hear which MDM platform others have found easiest to maintain as macOS permissions continue to change.

by rproffitt

How will you stop me from pulling out my phone and recording the screen?

Foolish goals there.

-> I was a developer and the way we handled the corporate device management goals was to tell them to fix it or go away.
In the end we were the CREATORS of the company product so top management REPLACED the IT LEADERS and we got back to work.

As to those MDM "solutions", they had NO PLACE in the dev groups and labs.

by Carter Gray

DDM and PPPC profiles are the safest approach for zero-touch macOS management. For internal tools, keep permissions narrowly scoped and test profiles on each macOS release. Jamf and Intune both work well, but good profile testing is key to avoiding unexpected user prompts.

by Pedro Carlton

Great discussion. In my experience, the key is to keep PPPC and system-extension policies as standardized as possible, while using DDM for configurations that need to stay consistent across the fleet. For internal or developer tools, I prefer explicitly defining the required permissions rather than granting broad access.

For MDM, Jamf has been particularly solid for macOS-focused environments, especially when combined with proper compliance monitoring and automated policy deployment. The biggest challenge still seems to be handling new macOS privacy changes without creating unnecessary prompts for end-users.

by Jimmy Menk edited

I’ve seen a similar challenge with businesses that rely on Mac-based tools for day-to-day operations. For example, a dumpster rental company may use internal scheduling, dispatch, customer management, or route-planning software that needs additional permissions to work properly.

In those cases, having the right MDM policies in place can make a big difference, especially when multiple employees need consistent access without repeated security prompts. I’d also be interested to hear which MDM setup works best for smaller service businesses managing remote Macs

by saltgravity25

For the common apps, I’d keep as much as possible managed through PPPC and your MDM, then treat developer tools and other exceptions separately. I’d also test any macOS update with a smaller group before rolling it across the whole fleet. Privacy changes are one of those things that can suddenly turn a previously working setup into a lot of support tickets.

For remote teams, having a documented process for the permissions that still require user action matters a lot too. A short set of instructions with screenshots is usually better than expecting employees to figure out what an unfamiliar macOS prompt actually wants.

by rproffitt

In the end, we had no use for them. The entire C suite knew what the problem was and it was the IT leaders that had to go in the end.

The devs made the products, the IT lead didn't understand that if you monkey with production you get the boot.

by Henry Robt

Managing privacy permissions across macOS Sequoia and Sonoma can become challenging at enterprise scale, especially when different applications require different access. A centralized approach with consistent policies, clear deployment settings, and reliable reporting would make it easier for IT teams to manage permissions without repeatedly handling individual Macs.

by vztwo ae

We’ve been trying to keep macOS management as standardized as possible through MDM and PPPC profiles. For internal or developer tools that need additional permissions, we usually test them first and create specific profiles rather than granting broad access.

DDM looks promising for reducing manual intervention, but compatibility with newer macOS security changes is still something we’re monitoring closely. Jamf has generally provided a smooth workflow for compliance and permission management in our experience.

by rproffitt

For us it, without fail the IT would not be able to "fix it" for months.

It didn't take long for our senior management to step it and send IT to do what they do best and leave production alone.

by alinah929

For managed Macs, using MDM/PPPC profiles for known applications and system extensions provides the most consistent zero-touch experience. Keeping the profiles aligned with the latest macOS requirements is also important, since Apple continues to tighten privacy controls.

For internal or non-standard tools, I’d recommend creating specific PPPC/System Extension configurations rather than granting broad permissions. Testing these profiles on a small pilot group before deployment can prevent unexpected prompts across the fleet.

For compliance, Jamf, Kandji, and Intune can all work well, but the best choice depends heavily on how much macOS-specific management you need and how deeply the organization is already invested in a particular ecosystem.

One thing that has helped is maintaining a clear inventory of applications that require Screen Recording, Accessibility, Full Disk Access, Network Extensions, or other elevated permissions. That makes troubleshooting new macOS updates much easier.

by Robert Carlos

For larger fleets, I’d keep PPPC profiles and other privacy settings managed through MDM wherever possible. I’d also test internal tools on each macOS release before deployment, since permission behavior can change between versions and cause unexpected prompts.

by jonoliver

For enterprise Mac fleets, I’d use MDM/PPPC profiles and DDM wherever possible for a zero-touch baseline. For internal or developer tools, package the required system extensions and permissions through managed profiles rather than asking users to approve them manually.

Jamf, Kandji, and Intune can all work well; the best choice usually depends on how much Apple-specific management and automation you need. Keeping macOS and configuration profiles standardized also helps reduce unexpected prompts.

Your reply

Posts from new accounts enter the moderation queue before publishing. No advertisements, promotional content, or personal attacks. See the community guidelines.