As Connect End of Support (EOS) approaches on 31 January 2027, Atlassian is rolling out customer-facing messaging to inform admins and end users about apps running on Connect. This page explains the messaging that appears on the Connected Apps admin page, how your app's configuration determines which message is shown, and when each cohort of apps will be affected.
Connect end of support begins on 31 January 2027. This date was extended from December 2026 to give partners and developers additional time to prepare.
After this date, Atlassian will only address critical security vulnerabilities in Connect, and Connect feature deprecations will happen with little notice. Connect will not remain in a steady state after end of support.
For the full timeline, read Getting Ready for Connect End of Support.
Atlassian is rolling out customer-facing messaging for Connect end-of-support across the Connected Apps admin page. Messaging is rolled out in staged cohorts over approximately 3 months, starting mid-July 2026. Atlassian provides a 2-week advance notice via the Forge changelog before starting rollout for each messaging type and cohort.
Your app falls into a cohort based on its connectToForgeMigration module declaration in the app manifest:
| Cohort | Definition |
|---|---|
| Blocked by Atlassian | Apps reliant on a feature accepted as part of the Connect EOS Submission process. These apps are excluded from messaging via an allowlist, which is removed 1 month after the blocking issue is resolved.
Atlassian still encourages app developers to adopt the connectToForgeMigration module and declare a migration intent so that when the app is removed from the exception list, customers see vendor-specific messaging rather than the default Connect EOS notice. |
| YES | Apps that have declared willMigrateToForgeBeforeEOS as YES. |
| UNDECIDED | Apps that have declared willMigrateToForgeBeforeEOS as UNDECIDED. |
| NO | Apps that have declared willMigrateToForgeBeforeEOS as NO. |
| Undeclared | Apps that have not declared a connectToForgeMigration module. |
| Connect-only | Apps with only a Connect descriptor and no Forge manifest. |
Messaging appears on the Connected Apps management page in Atlassian Administration, informing admins which of their installed apps are running on Connect and what their options are.
| Timing | Cohorts included | Notes |
|---|---|---|
| Late July 2026 | Undeclared, NO, UNDECIDED, and Connect-only | Rolled out to all customers with apps in these cohorts. Partners notified via changelog two weeks prior. |
| Mid-August 2026 | YES | Partners notified via changelog two weeks prior. Rolled out to all customers with apps in this cohort. |
Ensure your connectToForgeMigration module is declared in your app manifest before your cohort's go-live date. This declaration determines which cohort your app falls into and what messaging your customers see. Declaring this module gives you control over the message shown and lets you link to your own migration plan.
The message that admins see for a given app depends on the following:
The table below summarizes all scenarios at a glance. Detailed descriptions follow.
| Scenario | App configuration | Banner type | Admin action |
|---|---|---|---|
| Forge app (no Connect) | Forge manifest, no Connect features | None | No action required |
| Newer Forge version available | Installed version is older; a newer version with a Forge manifest exists | Yellow warning | Update the app |
| Default — public app | Public Marketplace app on Connect, no migration intent declared | Yellow warning | Contact vendor via Marketplace listing |
| Default — private app | Private app on Connect, no migration intent declared | Yellow warning | Read Atlassian guidance |
| Migration intent declared — YES | Forge manifest with connectToForgeMigration module, willMigrateToForgeBeforeEOS: YES | Blue info | Read vendor migration plan |
| Migration intent declared — UNDECIDED or NO | Forge manifest with connectToForgeMigration module, willMigrateToForgeBeforeEOS: UNDECIDED or NO | Yellow warning | Read vendor migration plan |
App configuration: Forge manifest with no Connect features remaining.
What admins see: Nothing — no banner appears under the app name.
What to do: No action required.
App configuration: The installed version runs on Connect, but a newer version of the app with a Forge manifest has been published.
What admins see: A yellow warning banner prompting them to update the app to the latest version.
What to do: Encourage admins to update to the latest version. If you have also declared a migration intent on that newer version, admins see your app-specific migration banner instead of this generic one after updating.
This app version is running on a platform that will be unsupported soon. Update your app now, as the latest version could provide better support options or a migration path.
For more details, read Connect End of Support: What it means for private/custom apps.
App configuration: Public Marketplace app running on Connect, with no connectToForgeMigration module declared.
What admins see: A yellow warning banner directing them to the app's Marketplace listing to contact the vendor.
This app is running on a platform that will be unsupported after January 2027.
For migration plans or other available options, contact the vendor directly through the app's Marketplace listing.
App configuration: Private or custom app running on Connect, with no connectToForgeMigration module declared.
What admins see: A yellow warning banner directing them to Atlassian's public guidance.
This app is running on a platform that will be unsupported after January 2027.
For more details about this change, read Connect End of Support: What it means for private/custom apps.
App configuration: Forge manifest with Connect modules and a valid migrationGuideUrl declared via the connectToForgeMigration module, with willMigrateToForgeBeforeEOS set to YES.
What admins see: A blue information banner that links to your migration plan.
What to do: Keep your migrationGuideUrl up to date so admins always land on current migration guidance.
This app is running on a platform that will be unsupported after January 2027. Learn more about the vendor's plans to migrate app users (including you).
For more details about this change, read Connect End of Support: What it means for private/custom apps.
App configuration: Forge manifest with Connect modules and a valid migrationGuideUrl declared via the connectToForgeMigration module, with willMigrateToForgeBeforeEOS set to UNDECIDED or NO.
What admins see: A yellow warning banner that links to your migration plan. The copy is the same as the YES scenario — only the banner appearance changes from blue (information) to yellow (warning) to signal the unresolved or negative migration status.
What to do: Keep your migrationGuideUrl up to date so admins always land on current migration guidance.
This app is running on a platform that will be unsupported after January 2027. Learn more about the vendor's plans to migrate app users (including you).
For more details about this change, read Connect End of Support: What it means for private/custom apps.
Rate this page: