A managed Mac no longer receives the expected Accessibility permission from an old profile, or your team is preparing for a system upgrade.

Fastest answer: Stop treating the old PPPC Accessibility authorization as a long-term method. Apple marks it deprecated starting with macOS 26.2 and says its authorization capability is removed in macOS 27.0; Apple points administrators to declarative management with an app-settings Privacy configuration. Inventory your profiles and confirm your management solution supports the replacement before you migrate. (Apple’s PPPC service dictionary · Apple’s app-settings Privacy object)

This guide is for you if you maintain macOS privacy configuration profiles, plan upgrades to macOS 26.2 or later, or design Accessibility permission policies for managed apps. It focuses on organization-managed authorization—not the separate process for an individual user to approve an app manually.

Last reviewed October 19, 2026 against Apple’s Device Management documentation. Apple’s stated version behavior is the confirmed baseline; check the linked documentation again when Apple updates it.

What changes for Accessibility permissions in macOS 26.2?

Apple’s PPPC service dictionary identifies Accessibility as a service whose authorization through the legacy configuration method is deprecated starting with macOS 26.2 and removed in macOS 27.0. Deprecation is a warning to plan a replacement; removal means you should not expect that old method to continue granting the permission on the named system version. (Apple’s Accessibility service entry)

The scope matters. This is a change to the Accessibility authorization capability in the PPPC service dictionary. Do not infer that every PPPC service, every privacy setting, or every configuration profile changes in the same way. Verify each service against its own Apple documentation rather than replacing an entire privacy policy based on this one entry.

The affected group is also specific: administrators who use managed configuration to grant Accessibility permissions to apps. A user approving an app in macOS settings is a different workflow. This change does not, by itself, establish that a user’s manual approval process has been removed.

Treat macOS 26.2 as the point to start migration work, not as proof that your existing profile has already failed.

Will legacy PPPC still grant Accessibility in macOS 27?

Apple’s documented direction is clear: the old PPPC Accessibility authorization capability is removed in macOS 27.0. Do not plan to rely on a legacy profile to grant that permission on macOS 27.0. (Apple’s PPPC service dictionary)

That statement does not establish when macOS 27.0 will be released, or whether Apple will make additional changes before release. It also does not tell you whether a particular management vendor has implemented the replacement. Treat the documented removal as a planning checkpoint, and verify both Apple’s current documentation and your management platform’s implementation before scheduling production upgrades.

A profile can still appear in a management console or report as successfully delivered while the intended permission is not effective. Delivery status and authorization outcome are different signals. Your migration checks must examine the app’s identity, the installed configuration, and the resulting permission behavior on the target Mac.

Measure the change against four management indicators

Use the following indicators to determine what is affected and what you need to validate. Apple documents the version transition and replacement direction; your fleet inventory and tests determine whether a specific app and management workflow are ready.

Indicator What to inspect Decision value
Legacy profile status Profiles that configure the PPPC Accessibility service, including the relevant app entries Identifies policies that rely on the authorization method Apple has marked for removal
Target OS Current and planned macOS versions for managed devices Separates existing deployments from upgrade groups that need the new approach
Replacement capability Whether your management solution can deploy declarative management app-settings Privacy configuration Shows whether you can migrate through your current workflow or need another deployment plan
Authorization outcome Whether the intended app receives the required Accessibility access and completes its managed task Confirms effective permission, rather than profile delivery alone

Start with the exact service and application entries in your profiles. Record which devices receive them, which app identity each entry targets, and which system versions those devices run or are scheduled to run. Keep unrelated PPPC services out of scope unless their own documentation calls for a change.

Do not assume that support for ordinary configuration profiles proves support for this replacement. Apple describes app-settings Privacy as part of declarative management. Confirm that your specific management product supports the required declaration, payload structure, and device workflow.

What replaces the old profile?

Apple points to the app-settings Privacy configuration within declarative management as the migration direction. The relevant references are Apple’s app-settings Privacy object and the broader app-settings documentation. Apple also describes how declarative management fits into device management in its declarative management integration guide.

The change is more than renaming a payload. Your team needs to compare how it builds the current profile with how the new declaration is authored, assigned, delivered, and monitored. The Apple documentation defines the Apple-side configuration direction. It does not, on its own, confirm that every management console exposes the feature, that every supported device can use it, or that your existing app identity entries transfer unchanged.

Use that distinction when speaking with your management provider or platform team. Ask for the supported configuration format, the eligible device and OS conditions, the reporting available for declaration state, and the documented removal or rollback procedure. Then test those answers on a device under your own management workflow. Until you have evidence from your actual platform, describe vendor support as unverified—not as a confirmed capability.

The data model also affects how you plan operations. Apple’s guide to using the declarative management data model to scale devices is useful context for teams that need to reason about managed state and device reporting. It does not replace testing the specific Privacy declaration you intend to deploy.

Migration decision conditions

  • If your current PPPC profile contains an Accessibility service entry and the target group includes macOS 26.2 or later, then include that profile in the migration inventory; do not assume other PPPC services are affected.
  • If your management solution documents support for the required declarative management app-settings Privacy configuration, then validate it in a test group before production rollout.
  • If the console lacks the relevant configuration, or the provider cannot confirm the deployment and reporting workflow, then hold that group’s upgrade until you have a supported replacement or a reviewed interim plan.
  • If the replacement is deployed but the target app does not receive effective authorization, then pause expansion and investigate app identity, configuration state, and the device’s resulting permission behavior.
  • If the application can be approved only through a user-driven workflow in your environment, then document that operational requirement explicitly; do not label it an equivalent managed grant without testing and approval from your security team.

Verify the replacement before changing the fleet

Treat Accessibility as a high-impact permission in your operational review: the app’s intended use may depend on interacting with the user interface. A misapplied grant can therefore disrupt a managed workflow, while an overly broad grant can exceed the access your policy intended. Define the minimum app scope and the expected behavior before changing the payload.

First, inventory the old configuration

Export or inspect the active profiles that use the PPPC Accessibility service. For each relevant entry, record the application identity, the profile assignment, the device group, and the systems currently in that group. Check for overlapping profiles or old assignments that could make a test result hard to interpret.

Do not count a profile merely because its name suggests that it controls Accessibility. Confirm the actual service and application entry in its payload. This is how you distinguish affected authorization rules from unrelated privacy settings.

Next, confirm your management path

Compare your present deployment process with the declarative management option. Ask your platform owner or provider to demonstrate how the app-settings Privacy configuration is authored, assigned, sent to a device, and observed after delivery. Check whether the workflow identifies a declaration as active, failed, or pending, and whether administrators can tell those states apart.

Apple’s documentation is the authority for the configuration model and the stated deprecation boundary. Your management console’s feature claims are not proof that the exact configuration you need works. Capture the management product version and test result in your internal change record, but avoid treating an untested statement from a support conversation as a production validation.

Then, build a controlled pilot

Choose a test Mac that receives the same management policies as the target production group, or document each difference that could affect the result. Use a representative managed app and a task that genuinely requires its intended Accessibility access. Keep the old and new policy behavior distinguishable so you can identify which configuration produced the observed outcome.

Verify the full path: the device is in the expected assignment, the new declaration is present, the app identity matches the intended application, and the task succeeds under the intended user context. Also test what happens when the app is updated or reinstalled if that is a normal part of your application lifecycle. Do not infer success from a green deployment indicator alone.

A useful test record separates three outcomes: configuration delivered, authorization effective, and application task completed. A pass in one category does not automatically prove a pass in the others.

Finally, plan rollout and recovery

Move from the pilot to a limited production group only after the team agrees on the success criteria and the recovery path. Expand by device group according to your own upgrade schedule. There is no universal cutover date in the cited Apple documentation that should override your fleet’s readiness or your organization’s change controls.

Before expanding, decide how you will stop a rollout if the replacement fails, how you will restore the prior working state where that remains available, and how you will handle devices that miss the deployment or report ambiguous status. A rollback plan is not a claim that the legacy grant will remain valid on future systems; it is a controlled response for the systems and states where your test confirms it is available.

What administrators should validate before migration

Use this acceptance list in your change review:

  • The inventory identifies every profile that configures the PPPC Accessibility service and the app identity targeted by each entry.
  • The affected device groups and their current or planned macOS versions are recorded.
  • The management owner has confirmed support for the declarative management app-settings Privacy path, or marked it unverified.
  • A test device receives the intended declaration through the same assignment process planned for production.
  • The intended application performs its required task after deployment; a profile-delivery status is not accepted as a substitute.
  • The team has tested the failure response, user impact, and recovery procedure.
  • The rollout plan checks Apple’s documentation again before the macOS 27.0 removal checkpoint.

For teams validating the experience away from a user’s daily workstation, a separate Mac test environment can help isolate the deployment workflow from ordinary work. Keep the distinction clear: a remote Mac can provide a place to run a test, but it does not prove that your MDM configuration or app identity is correct. For a hands-on explanation of user-level permission checks, see the SSHMac Help Center; keep that workflow separate from MDM authorization validation. If you are assessing whether a temporary remote Mac is suitable for this kind of isolated testing, review SSHMac’s remote Mac environment, then verify the MDM behavior against your own managed fleet.

A staged plan is safer than a fleet-wide switch

The migration sequence is straightforward: inventory the old policy, confirm the management platform’s replacement support, pilot the declaration, verify app behavior, and expand only when the recovery procedure is understood. The key decision is not whether to keep or discard every PPPC profile. It is whether each Accessibility grant has a documented path that remains appropriate for the target system version.

If your present test setup depends on a shared workstation, inconsistent system versions, or policies you cannot safely change, it can make results harder to reproduce. A temporary real-Mac test environment may give you a separate place to evaluate the workflow. Keep your managed production fleet as the source of truth, though: teams that need a permanent, tightly controlled fleet or direct access to physical peripherals should validate on their own managed hardware rather than treating a temporary test Mac as a substitute.