Skip to content
Administration

Tiered enforcement for External Sites

External Sites policies now apply a first tier of managed-account blocking once activated, with no network header needed. Network-header enforcement stays available for broader coverage. It has been generally available on Atlassian Cloud since 27 Oct 2026.

  • Generally available since 27 Oct 2026
  • Medium impact
  • Admin review: api change

What it is

Improvement

This covers web, mobile apps, API tokens, and MCP access where supported. Network-header enforcement is still an option when an organization needs wider coverage.

Written from Atlassian's release note and checked against it automatically. Atlassian's original stays the source of truth.

What to do now

  1. Review existing External Sites policies and confirm their access rules are current.
  2. Keep policies deactivated if enforcement should not begin yet.
  3. Activate a policy when ready to apply the initial tier of protection.
  4. Decide whether network-header enforcement is needed for extra coverage.

Where the rollout is

  1. First published Done
  2. Rollout starts Done
  3. Generally available Done

What changed

  1. First published by Atlassian

Atlas Bench began tracking Atlassian Cloud on 29 Oct 2026. Changes before that date are not in this history.

Find out who can reach what.

Fixed scope. The assessment starts at the identity layer: human and non-human access, the accounts nobody owns, and what has to be true before an agent gets one. You get the findings, the ownership gaps, and the order to close them in.