Confluence 10.1 release notes

 

Get the latest version

This Confluence release supports only Data Center licenses. If you have a Server license, check out your options for upgrading.



More

Read the full list of issues for important info about the resolved issues in this release.


Thanks for your feedback

More than 314 votes satisfied!

Find and sort most used macros in your site

For: ADMINS

We’ve improved the Macro usage reporting to help you make informed decisions about your macros. Now, you can see which macros are used most often, grouped by app, and easily distinguish between Atlassian and third-party macros. You’ll also find direct links to manage third-party apps in the Universal Plugin Manager (UPM).

These updates make it easier to identify underused apps, plan for cloud migration, and troubleshoot performance issues. You no longer need to run manual database queries or raise support tickets just to understand macro and app usage across your site.

To see how often a macro is used, go to the Administration menu, then General Configuration, then Macro Usage. More about macros

Image of the macro usage page in Confluence

Manage your integrations and automations with service accounts

For: ADMINS

Service accounts are specialized, non-user accounts created for secure and efficient management of automated processes and external integrations. With service accounts, you can securely access REST APIs using the OAuth 2.0 authentication method to execute scripts and run tasks while maintaining full control of permissions. All actions performed by service accounts are tracked, providing visibility into their operations.

To set up a service account:

  1. Go to Administration, then User management, then from the sidebar select Service accounts.

  2. Select Create service account.

  3. Follow the prompts to configure your service account’s details, scopes, and resources.

  4. Generate your OAuth 2.0 credentials.

  5. Review all the details and copy your credentials to a safe place.

Explore how to manage a service account

For: ADMINS

We're introducing OAuth 2.0 support for application links (app links) across Atlassian Data Center products. OAuth 2.0 is an industry-standard authentication protocol that enables secure, modern, and reliable connections between Atlassian products and external applications.

We’re also working on OAuth 2.0-based app links to connect with cloud to allow for secure and efficient integrations of hybrid environments, and will share the timeline soon.

Explore how to link to another application

Upgrade to React 18.3 and latest Atlaskit

For: ADMINS

We're upgrading Confluence Data Center to use React 18.3 and the latest Atlaskit components. This update helps keep your instance secure and compliant by enabling ongoing security updates and bug fixes from Atlaskit and React.

Editor upgrade to TinyMCE 7.9.1

For: ADMINS

We’ve upgraded the Rich Text editor in Confluence to TinyMCE 7.9.1. This update brings the latest security enhancements, bug fixes, and improvements to your editing experience in pages and comments. No action is needed — your content and macros remain fully compatible, and the upgrade is applied automatically.

OpenSearch for Confluence Data Center

As your Confluence site grows, you need a search that keeps up with your team’s pace. That’s why Confluence Data Center now offers OpenSearch as an opt-in alternative to the default Lucene search platform. We recommend switching to OpenSearch because it offers performance, scalability, and reliability improvements over Lucene.

We’re sharing a guide that explains the benefits of using OpenSearch as an alternative to the default Lucene search platform in Confluence Data Center. It includes:

  • Key differences between OpenSearch and Lucene

  • Benchmark results that show OpenSearch delivers faster search and better scalability

  • Guidance on when and why to switch, with further configuration steps

Explore the full documentation for more details and performance test results

Known issues

Application Links page 500 error

If you manage a hosting environment or use custom deployment tooling, you might encounter a 500 error when accessing the Application Links page. This issue is caused by changes in how configuration data is stored. Certain records previously managed in Bandana are now handled in Plugin Settings.

This problem doesn’t affect standard Confluence deployments, it's limited to environments that manage configuration data directly in the database. If you manage a hosting environment or use custom deployment tooling, review your scripts and update them to support the new Plugin Settings structure in Confluence 10.1.0 and later.

Supported platforms changes

There are no platform changes in this version. See the complete list of supported platforms

End of support announcements

There are no advance announcements this time.

For more information on these notices, see End of Support Announcements for Confluence.

App developers

Head to Preparing for Confluence 10.1 to find out more about changes under the hood.

Upgrade steps

Always test the upgrade in a test environment before upgrading in production.

To upgrade Confluence to the latest version:

  1. From the Administration menu , select Manage apps, and then Confluence update check to verify the compatibility of your user-installed apps with the target application version.

  2. From the Administration menu , select General Configuration, and then Plan your upgrade and the version you want to upgrade to. This will run the pre-upgrade checks.
  3.  From the Administration menu , select General Configuration, and then Troubleshooting and support tools to check your license validity, application server, database setup, and more.
  4. If your version of Confluence is more than one version behind, read the release notes and upgrade guides  for all releases between your version and the latest version.
  5. Back up your installation directory, home directory, and database.
  6. Download the latest version of Confluence.
  7. Follow the instructions in the Upgrade Guide.

Update configuration files after upgrading

The contents of configuration files such as server.xml, web.xml , setenv.bat / setenv.sh, and confluence-init.properties change from time to time. 

When upgrading, we recommend manually reapplying any additions to these files (such as proxy configuration, datasource, JVM parameters) rather than simply overwriting the file with the file from your previous installation; otherwise you will miss out on any improvements we have made.

Upgrade instructions

Follow the usual upgrade instructions to upgrade your site.

tip/resting Created with Sketch.

Been a while since your last upgrade? Check out our upgrade matrix for a bird's-eye view of the most important changes since Confluence 9.2 LTS .

Don't forget to renew your software maintenance. Renew now

Resolved issues

For full details of bugs fixed and suggestions resolved, head to our public issues tracker on Jira.

Issues resolved in 10.1.1

Released on 04 November 2025

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

Issues resolved in 10.1.0

Released on 07 October 2025

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

Credits

Our wonderful customers... 

You play an important role in making Confluence better. Thanks to everyone who participated in interviews with us, made suggestions, voted, and reported bugs!

Last modified on Oct 27, 2025

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.