API · SDK · runtime · authentication lifecycle intelligence

Last updated · 9 September 2026

SchemaTrace

Breaking changes, enforcement dates and migration requirements.

ST-2026-062 · Runtimes & developer platforms

Atlassian extends Connect end of support to 31 January 2027

Atlassian extended Connect end of support from December 2026 to 31 January 2027 and is contacting affected vendors directly through support tickets.

Atlassian ConnectForge migrationend of supportadmin messaginglinked amendment

Previous state

Atlassian Connect end of support was previously communicated for December 2026.

Current state

The end-of-support date is 31 January 2027, with direct ECOHELP outreach to affected Connect and Forge-with-Connect-modules vendors.

Who needs to care

Atlassian Marketplace and private app vendors that still depend on Connect modules.

What to do

Use the extension as bounded migration time, respond to Atlassian outreach and complete the move to Forge-supported architecture before 31 January 2027.

What the source does not prove

This is a linked date-extension amendment to the existing Connect lifecycle event. It does not reverse the migration direction, restore new Connect extensibility or create a separate product event.

Lifecycle history

Dated event sequence

  1. Production rollout began

    Administrator messaging started for named cohorts.

  2. End-of-support extension confirmed

    Atlassian moved Connect end of support to 31 January 2027 and described direct vendor outreach.

Evidence ledger

First-party sources

  1. 01
    Atlassian Developer — Forge changelog

    Official platform changelog · 2026-07-24

    Open official source ↗
  2. 02
    Atlassian Developer — Atlassian developer changelog

    Official lifecycle amendment and vendor-outreach notice · 2026-08-04

    Open official source ↗
  3. 03
    Atlassian Developer Community — Connect End of Support extended to January 31, 2027

    Official Atlassian developer-community announcement · 2026-08-04

    Open official source ↗