Atlassian Connect end of support on January 31, 2027: how to check which Confluence apps you use are affected

Last updated: 16 October 2026 · By Quicksloth

Atlassian ends support for Connect, the older way of building cloud apps, on 31 January 2027. If your Confluence Cloud site uses Marketplace apps, some of them may still run on Connect. A site admin can see which ones in a few minutes, on one page of Atlassian Administration, without installing anything.

Short version: in Atlassian Administration open Connected apps for your site. Apps that still use Connect show a yellow or blue warning saying they run on a platform that will be unsupported after January 2027. A Forge app that uses no Connect features shows no warning. For each app with a warning, read the developer's migration plan or ask them, and write down what your team keeps in that app.

What changes, with dates

Atlassian's blog post Getting ready for Connect end of support of 3 August 2026 (read on 16 October 2026) lists the steps so far:

September 2025: Atlassian "stopped accepting new Connect apps on Marketplace".
March 2026: "Apps with a Connect descriptor can no longer receive updates."
31 January 2027: "Connect end of support begins". The date was moved from December 2026 (also announced in the developer community, read on 16 October 2026).

What end of support means, in Atlassian's words: after that date it "will only address critical security patches", Connect features can be removed with much less notice, and some platform changes may make apps stop working without advance notice. Atlassian's page for private apps (Connect end of support: private apps, updated 10 August 2026, read on 16 October 2026) adds that "Connect will not remain in a steady state after end of support".

It is not a date on which every Connect app switches off. It is the date after which an app that is still on Connect can break and may not be fixed. Many developers have already moved their apps to Forge, Atlassian's newer platform, often on the same Marketplace listing: Atlassian's blog post says customers should not see the change directly, though they may need to update the app or approve new permissions.

Step 1: open the Connected apps page

You need to be a site admin. These steps are from Atlassian's help page Manage your apps (read on 16 October 2026):

Go to admin.atlassian.com and select your organization if you have more than one.
Select Apps (or Admin, depending on how your organization is set up), then Site settings, then Connected apps. If you have more than one site, pick your Confluence site first.
From Confluence itself you get to the same page with Apps in the navigation, then Manage your apps.

The list shows every app installed on the site. Apps that need an action from you, such as an update, are listed first.

Step 2: read the warnings

Atlassian's page What admins see (updated 10 September 2026, read on 16 October 2026) describes the warnings on the Connected apps page. Atlassian writes that they were "rolled out in staged cohorts over approximately 3 months, starting mid-July 2026", the last group in September 2026:

What you see on the app	What it means	What to do
No warning	A Forge app that uses no Connect features	Nothing for this date
Yellow: "This app version is running on a platform that will be unsupported soon."	A newer Forge version of the app exists, but your site still has the old one	Update the app
Blue: "This app is running on a platform that will be unsupported after January 2027. Learn more about the vendor's plans…"	The developer has said it will move the app to Forge before the end of support	Read the developer's plan behind Learn more
Yellow, with the same text and link	The developer has said it is undecided, or that it will not move the app	Read the plan and ask the developer (Step 4)
Yellow: "This app is running on a platform that will be unsupported after January 2027."	A Marketplace app whose developer has declared no plan	Contact the developer through the Marketplace listing

Apps built by your own company or a contractor (private apps) get the same yellow warning, and Atlassian's private apps page says apps running on Connect are marked LEGACY there. For Marketplace apps, the same page says admins need no action "at this stage": moving the app is the developer's job. What you can do is know early which apps are at risk and what your team keeps in them.

Write the list down: app name, colour of the warning, what your team uses it for, and roughly how much content is in it (questions, pages, macros, settings).

Step 3: check the Marketplace listing

Open each app with a warning on the Atlassian Marketplace and look for:

The "Runs on Atlassian" badge. Atlassian's page Runs on Atlassian (updated 24 August 2026, read on 16 October 2026) describes it as a program for "Forge apps" that keep data on Atlassian's own compute and storage, and says you can filter apps by it. An app with the badge is on Forge. An app without it may still be on Forge (some Forge apps send data to their own servers), so no badge does not prove Connect.
The date of the latest cloud version in the listing's version history. Since March 2026 a Connect app cannot be updated, so a recent cloud release is a good sign that the developer is active.
A note from the developer about Forge or the end of Connect, in the listing or its documentation.

Step 4: ask the developer

Use the support link on the app's Marketplace listing. A short message gets a clearer answer:

Hello, our Confluence Cloud site shows a Connect end of support warning for your app [app name] on the Connected apps page. Atlassian ends support for Connect on January 31, 2027. Will your app move to Forge before that date, will it stay on the same Marketplace listing, and will our existing content and settings carry over? Is there anything we need to do?

While you wait, keep the app installed and save a copy of anything important that lives only in it, if the app lets you export it. Before you uninstall an app, ask the developer what happens to its content: some apps keep their data in your Confluence site, others in their own storage.

If one of your apps is a Q&A app

Questions-and-answers apps are one of the places where this matters, because the content in them is your team's knowledge. Of the four Q&A apps for Confluence Cloud we compared, one runs on Connect in the cloud: Questions & Answers by EliteSoft, according to the Marketplace data for its latest cloud version. We do not know EliteSoft's plans; if they move the app to Forge, its users may not need to do anything.

Q&A apps for Confluence Cloud compared puts four apps side by side, with prices, reviews, platform and what each one lacks.
Moving from Questions & Answers (EliteSoft) explains your options if you use that app, including staying.

Our own app, Quicksloth Q&A for Confluence, is built on Forge only, with no Connect modules. It is coming soon to the Atlassian Marketplace; the overview will link to the listing as soon as it is live.

Questions and answers

Will my Connect apps stop working on 31 January 2027?: Not necessarily on that day. Atlassian says that after that date it will only fix critical security problems and that some changes may break apps without notice. An app still on Connect can keep working for a while, or stop, and you may not get a warning first.
Is Confluence Data Center affected?: No. Connect is a cloud platform. Data Center has its own dates, which this page does not cover.
An app has a blue warning. Do I need to do anything?: Read the developer's plan behind Learn more. When the Forge version arrives, you may have to update the app or approve new permissions; the Connected apps page will show it.
Is "Connect on Forge" the same as Forge?: Not for this date. On Atlassian's page for admins, the only case with no warning is a Forge app with "no Connect features remaining". An app that runs on Forge but still uses some Connect features can still get one of the warnings.
Can I see the platform before I install a new app?: Since September 2025 Atlassian has not accepted new Connect apps on the Marketplace, so any app listed after that date is on Forge. For older listings, look for the "Runs on Atlassian" badge or ask the developer.

Dates and quotes come from Atlassian's blog post of 3 August 2026, its developer community announcement, its developer pages "What admins see" (10 September 2026), "Connect end of support: private apps" (10 August 2026) and "Runs on Atlassian" (24 August 2026), and the help page "Manage your apps", all read on 16 October 2026. Atlassian can rename menus and change the warnings: if something looks different on your site, Atlassian's pages have the current names. Written with AI tools and checked by Quicksloth. Quicksloth is an independent developer and is not affiliated with Atlassian or EliteSoft. Atlassian and Confluence are trademarks of Atlassian.