To ensure apps built for Atlassian products keep pace with modern web standards, we are retiring our legacy app development framework, Connect, in December 2026.

If your site has private apps running on Connect, you'll start to see warnings on the Administration and in-app screens. Private apps, sometimes referred to as custom apps, are typically developed by customers themselves or a Solution Partner. They are not purchased from the Marketplace, and are often used for internal custom solutions and workflows.

This page explains:

what the warnings mean
what actions you, as an admin or end user, should take
what Atlassian will and won't support during this change

Why am I seeing warnings?

In Atlassian Administration or Connected Apps experience, you might see banners or warnings for specific private apps. If you see these messages, it means the app is running on Connect, which will soon be retired.

Why do I need to address this?

When Connect is retired, it will no longer receive security updates or support. Private apps that still run on Connect might stop working properly, and over time they might become unsafe to run in your environment.

What do I need to do?

Identify all LEGACY private apps

Admins will begin to see warnings in Atlassian Administration (especially in the Connected Apps page) for any private apps that still use Connect. These apps will be marked with the LEGACY status.

Audit LEGACY private apps and reassess your workflows

For each private app with the LEGACY status:

Review what the app does by identifying:
- what business problem or workflow it supports
- who uses it, and how often
Check if you still need the app. Determine if:
- there's a native Jira or Confluence feature that can replace it
- you could simplify or retire the workflow it supports

After auditing each LEGACY app, decide whether to keep or remove it. If the app is no longer critical, uninstall it from your site.

If needed: identify the LEGACY app's vendor or developer

If you still need the app's functionality, contact its developer. The developer may be someone inside your company, or a developer who was hired to create the app for your organisation. Select the app's View app details link on the Connected Apps page to find this information.

Notify the developer that the app is running on Connect. Share the following blog with them so they understand what needs to happen next: Connect End of Support: What it means for custom apps and how to migrate to Forge

This blog explains, in more technical terms, how developers can move private apps to Atlassian's supported platform.

If needed: engage a Solution Partner

If you can't identify/contact the original app owner or no longer have in-house development capacity to update the app, you can engage an Atlassian Solution Partner. They may be able to help you understand what an app does, propose alternatives, or migrate the app onto a supported platform.

You can find partners in the Atlassian Partner Directory.

What Atlassian will and won't support

To make this transition as smooth as possible, Atlassian will:

maintain stability of Connect-based apps during the migration period, so app vendors and developers have time to move their apps.
provide clear in-app warnings when an app is running on legacy technology that will become unsupported.
offer documentation and guidance to app owners so they can update their apps in line with our latest recommendations and releases.

However, Atlassian:

won't directly update or rewrite installed apps.
won't provide long-term support for apps that remain on Connect after December 2026.

If a private app remains on Connect after support ends, it will no longer be supported and may stop working properly.

FAQ

Q: Do I need to take any action if I've installed Connect apps purchased from the Marketplace?

No action is required at this stage from you as an admin.

Marketplace apps are supported and maintained by our partners.
Many partners are already updating their apps to our modern platform.
Connect will be supported until December 2026, giving partners time to complete their migrations.

If you have a question about a specific Marketplace app's migration status, go to the app's listing in the Atlassian Marketplace and reach out to the partner directly using the contact details provided there.

Q: What if I do nothing about a private app that shows a LEGACY warning?

If you take no action and the app is not updated:

The app may eventually stop working once legacy support ends
You may lose access to any custom functionality it provides
Atlassian Support will not be able to fix issues caused by that legacy technology

For that reason, we strongly recommend either:

working with the app's owner or developer to migrate it to a supported platform, or
notifying site users of the app's deprecation and scheduling its removal before support ends in December 2026.