Connect warnings are about to reach your admin console: what the banner means and what it does not

[#1]

Sometime in the next days, a yellow warning will start appearing under some of the apps in your Atlassian Administration console. I checked the Connected apps page on a production Enterprise org this morning, 25 August: no warnings yet. That matches Atlassian's timeline, the messaging is moving from canary to production instances right about now, which is exactly why this is the week to look at that page, while it is still quiet. For a lot of admins, the banner will be their first introduction to Connect end of support. A user forwards a screenshot, a manager asks "is this app about to break?", and suddenly a platform migration that has been running quietly since 2025 is your Tuesday morning..

Better to meet the banner here first. Here is what it means, what it does not mean, and the three checks worth running before it shows up.

What is actually happening

Connect, the app framework that predates Forge, reaches end of support on 31 January 2027. Atlassian recently extended the date from December 2026 to give vendors and developers more runway. After that date, Connect receives critical security fixes only, and Atlassian states plainly that Connect feature deprecations will happen with little notice.

This is the final phase of a process that has been underway for a while: new Connect apps stopped being listed on the Marketplace back in September 2025, new Connect private app installs were closed off after that, and end of support is the last step.

The part that concerns you as an admin is the messaging. Per Atlassian's developer changelog of 18 August, the admin facing migration messaging is moving from canary to production instances roughly two weeks from that announcement, which points at the first week of September. The exact date is not published, so treat it as imminent. Some instances may see it sooner.

What the banner actually means 🔍

The warning appears in Atlassian Administration, under Connected apps, as a yellow section under the app's name, with wording along the lines of: this app is running on a platform that will be unsupported after January 2027.

Here is the detail that will save you an escalation: the banner comes in variants, and the variant tells you something useful about the vendor.

1. The vendor has declared a migration plan. Vendors can declare a migration commitment in their app descriptor, including a link to their own migration guide. If you see a banner with an app specific migration link and a commitment status, the vendor is engaged. That is the good version.
2. The vendor has declared, but is undecided. The declaration supports an explicit undecided status. Honest, and worth a follow up question to the vendor, but still a sign someone is at the wheel.
3. The generic banner. No declaration at all. The banner points you to the Marketplace listing for public apps, or to Atlassian's general guidance for private apps. This is the one that needs your attention, and even here, generic does not automatically mean abandoned. It may simply mean the vendor has not declared yet.

For private and custom apps, the Connected apps page marks affected apps as LEGACY. These are the apps nobody markets, nobody documents, and in my experience of inheriting enterprise sites, occasionally nobody remembers writing. They deserve the most attention, because there is no Marketplace vendor behind them, only whoever built them, possibly years ago.

What the banner does not mean 🙅

Three things worth saying out loud, because banner driven panic tickets are coming either way:

• The app does not stop working when the banner appears. Atlassian has committed to maintaining the stability of Connect based apps through the migration period. The banner is a deadline notice, not an outage notice.
• It is not a security incident. Nothing about the app changed the day the banner appeared. The platform underneath it has a retirement date, which is a different kind of problem, the plannable kind.
• 31 January 2027 is not a magic switch off date for your specific app. It is the date support ends and the little notice deprecation era begins. Apps may keep functioning after it, but you would be running them on a platform where things can be turned off without much warning. That is not a place to keep anything business critical.

Three checks to run before the banner lands ✅

1. Open Connected apps today and take inventory. Atlassian Administration, Connected apps. Know before the banners arrive which of your installed apps run on Connect, and separate them into Marketplace apps and private or custom apps. The second list is the one that will cost you time, so find out now whether it is empty, short, or a problem.

2. For every flagged app, locate the migration intent. For Marketplace apps: the banner's own migration link if the vendor declared one, otherwise the app's Marketplace listing and the vendor's channels. For private apps: find the original developer and point them at Atlassian's migration guidance for custom apps. And if the developer left the company in 2021 and the app is a mystery box, Atlassian's documented route is engaging a Solution Partner to assess what the app does and propose a path, whether that is migration to Forge, a Marketplace alternative, or retirement.

3. Calendar the decisions and brief your service desk. Every flagged app needs an owner and a decision date that respects 31 January 2027, working backwards through your own change windows and testing cycles. And give your service desk a one paragraph answer for the "is this app safe?" tickets now, because it is much cheaper to write that paragraph today than to answer it forty times in September.

The honest close

Platform migrations like this one reward the boring virtues: an inventory, a named owner per app, and a calendar. The banner is genuinely helpful, it does the discovery work for you, but only if the first time you see it is not the first time you think about it.

So, a question for the comments: open your Connected apps page right now. Zero flags, a handful, or a problem? And for the private apps on the list, do you still know who wrote them? 👇

Sources, verified 25 August 2026: Forge changelog (18 August entry and the EOS extension), Connect End of Support: what it means for private and custom apps, Connect to Forge migration module, Announcing Connect End of Support.