Skip to content

Brief Connect v2.6 Release Notes

Release date - 4th May, 2026

Package version: 2.6

This release is a platform upgrade release, focused on stability and scalability improvements. Please note, that Brief Connect instances must running the latest infrastructure (MongoDB as Primary DB) to be able to upgrade to 2.6.

New features

Proxy Management: Proxies are now managed within Brief Connect, and no longer as a separate list in SharePoint.

  • Admins can control the full proxy list from the admin panel
  • Configurable options for end-users to be able to self-manage their own proxy assignments
  • Improved email notifications surrounding proxy access

Notifications:

  • Users can configure their settings to receive a notification when record documents are signed
  • Admins can completely control the default notification settings, with the same level of granularity end-users can

Record importing: We've improved our support for importing records from other systems into Brief Connect, particularly closed/inactive records

  • Dedicated Web API's to support importing closed records
  • Better scaling options to support large sets of document+record imports.

Changes and improvements

  • Key Dates on Record Details screen has improved UX, no longer highlights reason field unless there are changes
  • Improvements to how SP libraries are generated and records allocated, increasing the total number of records that a single SharePoint site can hold
  • BriefConnect backend (Azure Function) no authenticates to storage and cache services via Entra ID as well as connection string
  • Support for Azure Managed Redis service
  • Removed support for legacy storage services (SP Search/TS Data/Azure Cosmos DB Table API)

Bug fixes

  • Moving documents between sections more stable and reliable
  • User Groups assigned Decision Maker role can now record decisions
  • Improvements to formatting/consistency of Activity log

Upgrade instructions

Use these instructions to deploy package version 2.6.

Note

If you are upgrading from a version earlier than v2.5.x and haven't migrated to running MongoDB/Azure Document DB for the primary operational db, please refer to the Brief Connect team for specific release notes for additional pre-deployment steps.

Manual pre-deployment steps

Review release pipeline variables

Apply any changes to pipeline variables before you create a release, because every release creates a snapshot of pipeline variables at the moment of creation. To redeploy the application with updated variables, you must create a new release.

  1. Go to Azure DevOps and open your Brief Connect project.
  2. In the left panel, go to Pipelines → Library → Variable groups.
  3. Review variables for all environments included in this release and update values where required.
  4. Save your changes.

Create a new release

  1. Go to Azure DevOps and open your Brief Connect project.
  2. Go to Pipelines → Releases.
  3. Open the Deploy Brief Connect Application release pipeline.
  4. If there is no release with version 2.5.4, click Create Release.
  5. Set the Package Version variable to 2.5.4.
  6. Add a description (optional).
  7. Click Create.
  8. After you refresh the page, confirm the release v2.5.4 (n) appears in the list.

Pipeline deployment steps

  1. Deploy release v2.5.4 (n) (where (n) is the latest number available) from the Deploy Brief Connect Application release pipeline in Azure DevOps to the target environment.

Manual post-deployment steps

Clear the server cache

Role required: Brief Connect Administrator

  1. Log in to the target Brief Connect environment as the Brief Connect Admin user.
  2. Open the Admin Panel (https://[WEB_APP_URL]/#/adminPanel).
  3. Open your browser's Developer Tools, go to the Console tab, and run this command.

javascript window.clearCache();

  1. Confirm this message appears: Cache cleared. Server Result: true

Smoke tests

Follow the baseline guide after this release: Basic testing of Brief Connect