“This app might stop working soon”: Atlassian Connect apps

On 9 October an admin wrote on Figma's forum that they had "received a notification indicating that your app may stop working after January 2027", and asked what it meant for their site. Connect end of support begins on 31 January 2027, 106 days from the day I'm writing this. On our own test site the admin screen gave two different dates for it.

Figma answered the next day. They assumed the admin meant Figma for Jira and said they plan to move it to Forge "by the end of the year". I liked that answer, because for most apps only the vendor can give it.

If you've seen "This app might stop working soon", or one of its cousins, on a Jira or Confluence app, Atlassian is telling you the app still has Connect parts. On our test site the Connected apps page tagged 4 of its 57 entries Legacy. Its banner said January 2027, and the tooltip on the Legacy tag said December 2026. Same page. Weird, I know.

Finding the affected apps takes a few clicks per site, and most of what's left after that is emails to vendors. If you want the background on why Atlassian is retiring Connect, Mihai covered it in Atlassian Connect end of support: 31 January 2027. This one is the admin's to-do list.

Our Connected apps page: 4 Legacy tags, two dates, no Connect column

We opened Connected apps on our wolfaenpak test site on 16 October 2026 and clicked through its three pages and the details screens. We read Atlassian's documentation the same day.

1. No column, tag or filter says Connect or Forge. The list has the columns App, Edition, Installed by, Connections and Actions. The end-of-support signal is a yellow "Legacy" tag, on 4 of 57 entries. The word Connect only shows up inside a Legacy app's details, as a link to Atlassian's post.
2. One page, two dates. The banner says "unsupported after January 2027". The tooltip on the Legacy tag says "This app may stop working after December 2026". The tooltip is a month earlier.
3. The colour of the panel tells you the vendor's plan. Blue means the vendor has told Atlassian it will migrate before end of support. Yellow means the vendor said no, is undecided or said nothing, or that a newer version of the app is waiting for you.
4. Atlassian's own Connect integrations aren't tagged. 12 of them are on our site, all with versions ending in -AC, and we found nothing that says whether end of support applies to them.
5. Two shortcuts for spotting Connect didn't help. The details URL looked the same for the Legacy apps and our Forge app, and the old app-management API doesn't list Forge apps at all.

What “This app might stop working soon” means, and why a Forge app can still show it

The wording you see depends on when and where you saw it. "This app might stop working soon" is the title of a developer-community thread from 20 May 2026 that's had 2,382 views, about a banner that appeared inside apps. Atlassian staff said in that thread the message was meant only for non-Marketplace apps, rolled it back the same day, and later said it had been "scoped to canary tenants only". yasoon titled a support page after it, and that page still gives December 2026.

What admins see now is quieter. Atlassian documents the current copy on What admins see on the Connected Apps page, last updated 10 September 2026: "This app is running on a platform that will be unsupported after January 2027." Exalate quoted a third version in its support post, "This app may stop working after January 2027", and admins on Lucid's and Figma's forums repeat the same words. All three are the same warning about the same thing.

A Forge app can still get it, too. That one surprises people. Atlassian set the rule in its March 2025 timeline post. In its words, "an app that has a Forge manifest and a mix of Connect and Forge modules will be considered a Connect app until all Connect modules are removed." Exalate said exactly that about its own app in September: its package "still includes a Connect component alongside its Forge implementation", so the warning shows. A vendor telling you "we're on Forge already" and the warning are both true at the same time, until the last Connect piece is gone.

Connect end of support: December 2026 or 31 January 2027?

It's 31 January 2027. Atlassian moved it on 3 August 2026, in Getting Ready for Connect End of Support: "we're extending the end of support date from December 2026 to January 31, 2027." The developer changelog repeats it on 7 August. The pages updated after that use the new date too. They include the private-apps page and the migration-module page (both 10 August), what admins see (10 September) and the app migration page (23 September). The last one even says the date "was extended from December 2026".

December survives in older pages nobody went back to edit (the March 2025 timeline post says "Q4 CY2026", the August 2025 post on custom apps "the end of 2026"), on some vendor pages, and in our tooltip.

So plan for 31 January 2027. If someone in your company has December in a slide, they're probably reading the tooltip or a 2025 post, and it's an easy mistake when the product says it too.

How to identify if an app is Forge or Connect: four checks

Atlassian's own knowledge-base article for this question tells you to open each app's Marketplace listing and look for a descriptor link. It was last updated in September 2025, before the admin labels existed, and it's slow with more than a handful of apps. These are the checks I'd run instead, in this order.

Check 1: open Connected apps and look for the Legacy tag

Go to Atlassian Administration, select Apps, then Sites, pick your site, and select Connected apps in the left navigation (Atlassian's Manage an installed app page has the same path). From the organization's Atlassian apps page there's also a link, "Looking for your Marketplace and third-party apps?", which opens a site picker and lands you in the same place. You need to be an organization admin or a site admin.

Inside a product, the old Manage apps screen is gone. On our site both Jira and Confluence now say "App management has moved to Administration", with a "Take me there" button. The Jira sidebar item is still called "Manage apps", while the message says "Apps > Manage your apps". A bit confusing, but both take you to the same page.

Then page through the list. All of it. Our test site needed three pages for 57 entries, and 16 of those were Rovo MCP connectors that the system installed. The four Legacy tags were all third-party Marketplace apps:

App on our test site	Vendor	Tag	Details panel
ScriptRunner for Jira	The Adaptavist Group	Legacy	blue, links the vendor's Forge plan
Navigation Menus for Confluence (quick & easy orientation)	Seibert	Legacy	blue
STAGIL Navigation Menus and Themes for Confluence	STAGIL by catworkx	Legacy	not opened
User Management for Confluence (bulk & timed inactive users)	TechTime Initiative Group	Legacy	not opened

Keep in mind the tag is a pointer. It tells you nothing about how far along the vendor is. An Atlassian staff member called the "at risk" signal "complicated and conservative" in a September thread and said to expect "false positives", many with simple fixes. So a Legacy tag means "look at this one": the app has Connect parts, and the vendor may already be most of the way off them.

Check 2: open View app details and read the panel colour

A Legacy app's details page has a panel at the top. Atlassian's banner table says the wording is the same whatever the vendor declared, and the colour carries the meaning: blue when the vendor declared willMigrateToForgeBeforeEOS: YES, yellow when it declared no or undecided, and yellow by default when it declared nothing. A vendor whose app has no Forge manifest yet can't declare anything, so it always gets the generic yellow message. Both Legacy apps we opened, ScriptRunner and Seibert's Navigation Menus, were blue. We didn't see a yellow one on our site.

If the panel is blue, click "Learn more", because it goes to the vendor's own migration page (for ScriptRunner that's Adaptavist's "moving to Atlassian Forge" page). If it's yellow and has a Learn more link, that's the vendor's plan, and the plan may well be "no". If it only points you to the Marketplace listing, the vendor hasn't declared anything, so contact them there.

There's also a yellow "Update your app now" variant. It appears when your version is older than one with a Forge manifest. Updating removes that message, and if the new version still has Connect parts you'll get the regular panel instead.

Check 3: look at the Authorization tab

This one's for when you want to see the difference with your own eyes. On our site, ScriptRunner's Authorization tab mixes plain-English permissions with old Connect-style ones in capitals: ACT_AS_USER, ADMIN, DELETE, PROJECT_ADMIN and READ. Our own Forge app, Sentinel Vault, lists only plain permissions such as "Read Confluence detailed content" and "App Storage scope".

I wouldn't use this as a test by itself. It's a hint. I find it most useful when you're talking to a vendor and want to ask which of those permissions will change after the move.

Check 4: find Atlassian's own Connect apps

The Legacy tag skips Atlassian's own apps. I didn't expect that. On our list, six entries have a details link containing /user-connected-apps/connect/jira/ and an app key: Atlassian Assist, Atlassian Home for Jira Cloud, Automation for Jira, Jira Service Management Widget, Opsgenie and Statuspage for Jira. Opsgenie's details page shows version 2.0.3-AC and a "Descriptor URL" link. Connect apps have a descriptor; Forge apps have a manifest.

Six more are easy to miss. Confluence Cloud for Microsoft Teams, Confluence Cloud for Slack, and Jira Cloud for Microsoft Teams, Outlook, Slack and Spreadsheets sit at the top of our list with no details link at all, so the URL trick can't see them, but the Marketplace lists all six as Connect. So for Atlassian's own integrations, I'd simply note down every row that says "by Atlassian".

I couldn't find an Atlassian statement on whether these are in scope for end of support, are exempt, or are being migrated. A developer asked "Why hasn't Atlassian migrated its own apps?" on 21 August, and nobody from Atlassian answered in the thread. I'm not going to guess. If your teams depend on one of them, Automation for Jira especially, ask your Atlassian account team or open a support ticket and get the answer in writing.

Two shortcuts that didn't help on our site

Atlassian's August 2025 post on custom apps said you could tell Connect from Forge by the details URL: Connect apps had /connect/<product>/<app-key>/ in it and Forge apps an opaque ID. On our site only Atlassian's own Connect apps had /connect/ in the URL. All four Legacy apps had the same opaque ID format as our Forge app, Sentinel Vault. (The two we opened had blue panels, which need a Forge manifest, so they're probably Connect apps partway to Forge. The test may still work for a pure Connect app. We didn't have one to try.)

The other shortcut is the old app-management REST API (/rest/plugins/1.0/), which older inventory scripts call. We called it on our site: Jira returned 206 entries, 10 of them flagged as Connect, all of them Atlassian integrations with an -AC version. Confluence returned 211 entries with 2 Connect ones. None of our own four Forge apps appeared, and neither did the other third-party apps, Legacy ones included. It looks like an inventory and it isn't one, so I'd stick to the Connected apps page and page through it by hand.

What admins see on the Connected apps page: end-of-support warnings and LEGACY apps since July 2026

Atlassian rolled the admin messages out in stages from mid-July 2026: apps with no declaration, a "no" or "undecided" in late July, and apps whose vendor declared "yes" in September. Some apps are blocked on a missing Forge feature that Atlassian accepted as a blocker. Those are left out of the messages for now, and get them a month after the blocker is resolved.

One Atlassian page still reads as if none of this has happened. The overview page for adopting Forge, last updated in March 2025, says the migration-intent feature is "only available to a canary cohort of developers" and that "the messaging will not be visible to all users yet". The page about what admins see is newer (10 September) and says the messages rolled out to all customers, which matches what we saw on our site.

For private apps, the ones your company built itself or had built and installed by link, Atlassian's guidance uses the same "LEGACY" status and the same Connected apps page. Atlassian's March 2025 timeline said installing new private Connect apps would stop from March 2026, so most private Connect apps you find will be older than that.

What to ask each vendor about its Connect to Forge migration

For Marketplace Connect apps, Atlassian's FAQ says "No action is required at this stage from you as an admin". It tells you to contact the vendor through the app's listing. I'd do that now rather than in January, because a vendor's support queue in the last weeks before a deadline is not a fun place to be. These are the questions that get you a usable answer:

1. When will a version with no Connect modules be out? Ask for a month, and ask whether it's "Forge" or "Forge with remaining Connect modules", since Atlassian still counts the second as Connect.
2. Will the move need my approval? A Forge update that changes permissions, adds outside connections or changes remote backends is usually a major version, and major versions wait for an admin to consent. Atlassian's Limitations and differences page for apps adopting Forge says the first Forge version may or may not need approval. If it does, find the "Update" tag on Connected apps, open View app details, review the new permissions and select Update. Mihai wrote up the 11 changes that force a Forge major version from the vendor's side, if you want to know what to expect.
3. Will my data and configuration come across? Atlassian staff confirmed in September that data migration only works within the same Marketplace listing. If you're thinking of swapping to a different vendor's Forge app, there's no built-in way to bring your data along.
4. Where will my data live afterwards, and does the app send anything outside Atlassian? Atlassian's data residency glossary says Connect app data "may be stored outside of the Atlassian cloud environment by a third-party app vendor". An app can also qualify for the Runs on Atlassian badge, which needs Atlassian-hosted compute and storage, matching data residency and admin control over data egress. Others keep their own servers. Either can be fine, as long as you know which one you're getting.
5. Will the Runs on Atlassian badge change? Atlassian's Manage an installed app page warns that an update can gain or lose eligibility. Its absence doesn't prove an app is still on Connect, because the badge has extra requirements on top of Forge. We went through what the badge does and doesn't promise in our post about Sentinel Vault's AI review.

A good vendor answer looks like K15t's Forge transition page, which lists each app with a dated status ("Migration done (July 2026)", "Migration in progress. Target: end of October 2026"). A worrying one is no answer, or a date that still says "late 2026" without saying what happens in January.

Here's the email I'd send, adjusted for the app:

Hi, we run <app name> on <site>.atlassian.net. Our Connected apps page tags it
Legacy ahead of Connect end of support on 31 January 2027.
1. In which month will you release a version with no Connect modules left?
2. Will that update need admin approval, and which permissions change?
3. Will our data and configuration carry over automatically?
4. Where will our data be stored afterwards, and does the app send data outside Atlassian?
Thanks, <name>

If the vendor says no, or never answers

Give it two weeks, then ask once more through the support link on the Marketplace listing. If the answer is "no plan" or silence, treat the app like one of your own private apps (that section is below): find out who uses it, look for a native feature or another app that does the job, and plan the switch before January. Keep in mind Atlassian's data migration only works within the same Marketplace listing, so with a different vendor's app your data comes across only if that vendor offers an import, and otherwise you start fresh. A blue panel needs less of this. I'd still send the email, mostly to get the approval and data questions answered.

What stops working after 31 January 2027, and what keeps running

Nothing in Atlassian's pages says your Connect apps switch off on 31 January. The March 2025 post says customers "won't lose access to the app". The August 2026 post says Atlassian will "share more detail on timelines and next steps for Connect beyond end of support". There's no shutdown, block or uninstall date published anywhere I looked.

What does change, from the August 2026 post: "Atlassian will only address critical security patches. Support SLAs will be relaxed, and Connect will no longer evolve alongside the Atlassian platform." Connect capabilities can be removed "with significantly less notice". And the sentence I'd put in front of anyone who wants to wait it out: some platform changes "will cause apps to stop functioning without advance notice". The 2025 post put it more bluntly, that end of support means "use at your own risk".

Is that a reason to panic about each Legacy tag? I don't think so. Atlassian says "over 95% of paid app seats have been migrated to Forge", counted in paid seats rather than apps. It doesn't say whether apps that still have Connect parts count as migrated, and ScriptRunner, one of the biggest paid apps, still carries the Legacy tag on our site. So I'd expect the gaps to sit mostly with small apps, free apps and private ones, but check the big ones too.

There's also an audit angle. An Atlassian staff member wrote in June that for enterprise customers with SOC 2 and ISO 27001 obligations, an unsupported framework is "a material risk". Those customers were already asking how to find their Connect apps. If your auditors ask, the Connected apps page and the vendor answers are your evidence.

Private Connect apps you built yourselves: rebuild, replace or uninstall

I think private apps are where admins have most of the work. There's no vendor to email. Atlassian says it "won't directly update or rewrite installed apps" and won't support apps left on Connect after 31 January 2027. Its private-apps guidance boils down to a short audit for each LEGACY private app. Work out what business problem it solves and who uses it. Check whether a native Jira or Confluence feature, or a simpler workflow, could replace it. Then rebuild it on Forge, replace it, or uninstall it.

Atlassian's August 2025 post lists the signs of a private app. It was installed by link or in developer mode and isn't in Marketplace search. You hold its source code, and it has no licensing information. On the Connected apps page, a Marketplace app has a related-links sidebar and a private one doesn't.

If nobody knows who built it, Atlassian's advice is to bring in a Solution Partner. Any team with Forge experience and access to the code can do the rebuild. It's work we do too, and our Forge app development page is the place to start, but please check the uninstall option first. A private app nobody can name an owner for is often an app nobody uses.

An admin checklist for the 106 days before 31 January 2027

This is the order I'd work in, starting this week:

1. Open Connected apps for each site you own and write down the apps with a Legacy tag or an Update tag, plus every row that says "by Atlassian".
2. Open View app details for each Legacy app and note whether the panel is blue or yellow, and the "Learn more" link if there is one.
3. Apply pending updates on apps that show the "Update your app now" message, after reading the new permissions.
4. Email the vendor of each Legacy app with the questions above, yellow ones first. Keep their answers with your audit evidence.
5. Ask your Atlassian account team about the "by Atlassian" rows from step 1 that your teams rely on.
6. Decide on each private app: rebuild, replace or uninstall, with an owner and a date before January.
7. Check again in December. The tags and panels change as vendors declare and ship, and Atlassian said it will eventually show migration notices inside the apps themselves, with advance notice and a testing period first. I couldn't confirm whether those in-app notices are live yet.

Planning a migration around the same January date? Mihai's post on why Cloud Fortified keeps probing an old Connect URL shows what a vendor's half-finished move can look like from the inside.

Where we stand, and where I could be wrong

We're a vendor too, so you should know where we sit: our four apps (CogniRunner, Sentinel Vault, LeanZero Management and Cost Slasher) have no Connect modules, and the Marketplace marks their current versions as not Connect.

This is one test site on one morning. Keep that in mind. Our list is full of development installs and test apps, so the 4-of-57 figure says nothing about a normal company's site, where I'd expect more Marketplace apps and more tags. I didn't open the details panels for STAGIL or TechTime. I didn't see an end-user banner inside an app either. And the wording has varied a lot this year, so yours might read differently. If you see a version I haven't quoted here, send a screenshot to [e-mail] and I'll add it.

My recommendation: do steps 1 to 4 of the checklist before the end of October, so the vendors have had three months to answer before January. Then spend whatever time is left on your private apps, because nobody else is going to fix those for you.

---

Originally published on leanzero.net. More Atlassian, Forge and local-AI write-ups at leanzero.net/blog, and if you're planning a migration or a Forge app, that's what we do: leanzero.net/services.