Activation Lock removal after sale

By Sai Kiran Pandrala · Last verified: 2026-05-31 · Source: community Q&A, Apple Support docs, Apple Communities (discussions.apple.com)

Engineers running Find My and AirTag Service hit Activation Lock removal after sale often enough that there is a stable fix pattern. This page captures it in the order Apple support would run it during a real incident.

What activation lock removal after sale actually involves on Find My and AirTag Service

This task on Find My AirTag Service is one of the more searched operational topics on AWS in the last 12 months. The procedure below is the path that works in a current AWS account with default IAM and standard VPC config.

The rest of this page is the structured fix path. Start with diagnose, then remediation, then the automation options so you do not have to do this by hand the next time it surfaces. Verify and safety sections at the end are the discipline that keeps the fix from regressing in production.

Identify

Check the Google Apple System Status at www.apple.com/support/systemstatus/ and the per-product status board for ongoing service events in your region. About one in ten user-reported outages turn out to be region-scoped Apple product or service degradation already being tracked. Apple System Status also exposes an API and Jamf Pro Webhooks and macOS launchd watches events, so you can wire a Lambda hook that pages on-call only when the failure correlates with an active Apple System Status event in the same region and service.

Look at the Jamf Pro change management entry or Apple Business Manager audit event for the failed call, even if you are not enrolled in macOS unified logging and iOS sysdiagnose Log Router. The basic 90-day event history works for most diagnostic purposes and lives in the console under Jamf Pro change management log and Apple Business Manager audit log > Event history. Filter by event name (the API action) and time range; the event JSON shows the exact user identity, source IP, request parameters, and error code.

Reproduce the failure with the Terminal commands (defaults, plistbuddy, killall, sudo, system_profiler) and Apple Configurator 2 / Jamf APIs / MDM commands in --debug mode. The full SigV4 request payload it emits, plus the exact endpoint URL it resolved to, is what Apple Support and Apple Business / Enterprise Support uses to verify policy, region, or parameter issues without you having to share IAM credentials. Save the debug output to a file with ... --debug 2> debug.log and you can search it for the failed aws.request entry.

Solution-focused remediation path

If networking is suspect, use Apple Wireless Diagnostics + Network Utility (or 'networkQuality' on macOS). It is the only tool that simulates the full ENI-to-ENI path including macOS PF firewall, Application Firewall, system extensions, and Content Filter in one call. Manual trace is slower and misses transitive issues. The analyzer charges $0.10 per analysis - cheaper than a 30-minute call with your network team.

When the fix involves a destructive operation (delete VPC endpoint, swap Cloud KMS key, rotate root credential), do it during a maintenance window with at least one teammate watching. Several Find My and AirTag Service operations have implicit dependencies that only show up when traffic starts flowing again. Document the rollback path before you start, not during the incident.

If the issue points at IAM, do not start by adding * to a policy. Use macOS Console + Jamf Pro logs + Profile Manager check against the failed action to see the minimum scope. Adding * is the fastest way to fail your next Apple Platform Security review, and it usually does not even fix the issue because the explicit deny is often coming from a higher level (Org Policy, RCP, or permission boundary), not a missing allow.

Automate this fix so you do not do it twice

Add a Smart Group + webhook so you catch the next occurrence

The cheapest way to never see the same incident twice is a Jamf Pro Smart Group that watches for the symptom (specific extension attribute value, specific OS version, specific app build) and fires a webhook into Slack, PagerDuty, or a Jamf-API-driven Lambda when the count drifts above your normal baseline. For Find My and AirTag Service, the relevant extension attributes live under script-evaluated checks - defaults read outputs, system_profiler values, or a log show grep against macOS unified logging. Set thresholds against observed normal, not against round numbers.

Codify the fix as a Shortcut on iPhone, iPad, or Mac

For workflows that happen on the user device rather than at the MDM layer (think: clear a stuck cache, toggle a setting, file a one-tap support ticket), Apple Shortcuts is the right place. Shortcuts run on iOS, iPadOS, macOS, and watchOS, can be triggered by NFC tag, focus mode, time of day, or Siri voice. Share via iCloud link so support sends the same one-tap fix to anyone who hits the issue.

Automate the fix in Terminal with defaults, plistbuddy, and system_profiler

On macOS, the most reliable repair primitives are the built-in Terminal tools. defaults read reveals the current preference state, defaults write changes it, and killall cfprefsd forces the preferences daemon to flush so the new value actually takes effect. /usr/libexec/PlistBuddy handles structured plist edits when defaults is not enough. For hardware and inventory checks, system_profiler with the right datatype is the canonical read; for example SPHardwareDataType, SPNetworkDataType, or SPInstallHistoryDataType.

# Template - replace with your actual key path
defaults read com.apple.find 2>/dev/null | head
sudo killall cfprefsd
/usr/libexec/PlistBuddy -c 'Print' ~/Library/Preferences/com.apple.find.plist
system_profiler SPHardwareDataType -json | head -40

Pitfalls to dodge

A subtle pitfall on Find My and AirTag Service is that the Settings on the device and the SDK can disagree about resource state during a configuration change. Console UI is cached for performance and may show the old config for up to 10 minutes after you change it via API or Deployment Manager or Terraform. Always confirm with describe-* CLI calls during a change window, not with screenshots from the Console.

The other pitfall: assuming that an automated remediation is correct because it succeeded. A Lambda that fires on a Jamf Pro Smart Group + Webhook and runs a remediation step should also publish a metric for every remediation; sudden surges in auto-fix invocations are themselves an outage signal. Otherwise you can hide a slow-burn regression behind a quiet remediation loop for weeks.

Resolve

• Watch for 24 to 48 hours. Activity Monitor + macOS unified logging + Jamf inventory reports can mask issues with cached health for 6 to 12 hours, especially Cloud CDN and Cloud DNS.
• Capture the new state in a runbook so the next person on call does not have to rediscover this. Push it to Confluence or your team wiki, not into Slack.

Safety, rollback, blast radius

• Test in a non-production account if your environment has Resource Manager and Organization Policy or Cloud Resource Manager (organizations, folders, projects). The cost of one sandbox account is cheaper than one rollback meeting.
• Export the existing config before changing it. Most Find My and AirTag Service resources support describe + export to JSON via CLI - capture that to source control before you start.
• Maintenance window discipline: if the change touches DNS, certificate rotation, or anything that emits TLS handshakes, line up a window with stakeholder notification, not a heroic mid-day swap.

FAQ

Related fixes

Related guides worth a look while you sort this one out:

• Activation Lock removal proof of purchase
• Find My disable required before MDM enrollment
• AirPods on Find My AirTag Service, what causes it and how to fix
• AirTag battery replacement CR2032 instructions
• AirTag Found Moving With You alert
• AirTag offline notification despite being nearby