Atlassian Connect private apps enter end of support on January 31, 2027

Atlassian Connect private apps enter end of support on January 31, 2027. Audit legacy apps and migrate or retire them before then.

CriticalEnd of supportAction requiredIn 159 daysVerified

Product

Atlassian Connect / Forge apps

Announced

3 August 2026

Effective from

31 January 2027

Who is affected

Organizations with private or custom Atlassian Connect apps installed in Jira, Confluence, Jira Service Management, or other Atlassian Cloud sites.

Admin roles to involve: Atlassian organization admin, App admin, Internal app owner

What administrators should do

Use the Connected Apps admin page to identify LEGACY private/custom Connect apps, confirm what business workflow each app supports, decide whether to retire it, and work with the app developer or Solution Partner to migrate required functionality to Forge before January 31, 2027.

What happens if this is ignored

After Connect end of support, private apps may stop working properly and will not remain a stable, fully supported platform beyond critical security handling.

Why this is rated critical: severity comes from a fixed rubric — this entry is a end of support that requires administrator action. Time-to-deadline is shown separately and never changes the rating.

Official source

Connect End of Support: What it means for private/custom apps

Published by Atlassian · Source dated 10 August 2026 · Checked 24 August 2026

Last verified 24 August 2026

Related changes

Atlassian Data Center is being retired — new sales ended March 30, 2026 (30 March 2026)
Atlassian Server products reached end of support on February 15, 2024 (15 February 2024)
Confluence Cloud legacy editor is fully deprecated from April 2026 (21 January 2026)

Keep planning

Back to the full change calendar All Atlassian changes Track your own vendors and renewals