Jamf Security Cloud - Delay in Data Policy Change Propagation

Data Policies are now fully synchronized across all edge regions, and policy updates in the Radar/JSC Web Console have been re-enabled.

The CSV import feature will remain temporarily disabled while improvements are implemented.

The fix has been applied to the affected service, and the root cause has been resolved. The policies need to be replicated to all edge regions, which should take a few hours. The page will be updated once replication is complete and the issue is fixed.

We are continuing to monitor for any further issues.
The previous update is still relevant.

Update — additional impact identified: Devices that change network context (roaming ↔ domestic) during this incident will not receive the corresponding Data Policy update. The Data Policy in effect prior to the network change remains applied until the fix is in place. Access Policies and Threat Prevention Policy are not affected by this. We are still working on a resolution and will continue to post updates here as they're available.

We are continuing to monitor for any further issues.

Jamf engineering has identified the issue and affecting Data Policy updates. Data Policy changes cannot be saved in any region right now while we put a fix in place.

Workaround/Customer Action: While the fix is in flight, we are asking customers with large policy sets to hold off on bulk or repeated Data Policy changes — particularly rule imports applied at a parent org unit, which regenerate policy across every org unit beneath it.

Two things worth knowing:
- Your existing policies remain fully enforced. There is no gap in protection on your devices.
- Access Policies, Threat Prevention Policy are unaffected.

We are continuing to investigate the issue.

Current Status: Jamf Security Cloud Policy Updates are unable to be saved. Previously changed configurations continue to see a propagation delay.

We are currently investigating an issue with Jamf Security Cloud that results in a delayed propagation of policy changes. Current configurations are working. If a policy change is made the updated configuration may not take effect immediately.