Skip to content

Brief Connect v2.5.10 Release Notes

Release date - Thursday, June 25th, 2026

Package version: 2.5.10

This is a patch release with bug fixes focused on user/group handling, SQL replica behavior and performance, workflow editor transition retention, and UserSetting migration.

Bug fixes

  • Prevent User Groups Service failure when deleted Entra ID users are present in group members/owners

    Brief Connect now handles departed staff more gracefully. If a deleted Entra ID account remains in a group, user group pages and activity history continue to load instead of showing blank pages, GUIDs, or missing names.

    Related support tickets: #17470

  • Improve SQL replication performance

    SQL replica (used for PowerBI Reporting) processing is faster and more reliable for large environments, especially during bulk updates and deletes. SQL replica data now keeps a consistent field format, reducing the required complexity of PowerBI models that previously needed to handle mixed-case for Field names/keys.

  • Improve records loading performance

    Dashboards, records, search, and record lists now load more efficiently in environments with many user and role fields due to improved caching. We expect this to reduce CPU consumption considerably. In our testing of loading a record page, server response time was up to 6x faster (Down from ~3sec to open a record to ~0.5sec)

    Related support tickets: #16935, #16933

  • Migrate UserSetting table data from CosmosDB to MongoDB correctly

    User notification preferences now migrate correctly when moving from Cosmos DB to MongoDB. Related support tickets: #17012

Upgrade instructions (from v2.5.x)

The following instructions apply to environments already running Brief Connect v2.5.x.

Note

If you are upgrading from a version earlier than v2.5, please refer to the Brief Connect team for specific release notes for additional pre-deployment steps (including pipeline setup and environment variable updates).

Manual pre-deployment steps

Review release pipeline variables

Apply any changes to pipeline variables before you create a release. Each release snapshots variable values at creation time, and you must create a new release to redeploy with updated variables.

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

Create a new release

  1. Go to Azure DevOps, open your Brief Connect project, and go to Pipelines -> Releases.
  2. Open the Deploy Brief Connect Application release pipeline.
  3. If there is no release with version 2.5.10, click Create Release.
  4. Set the Package Version variable to 2.5.10.
  5. Add a description (optional).
  6. Click Create.
  7. The release v2.5.10 (n) is created and appears in the release list after refresh.

Pipeline deployment steps

  1. Deploy release v2.5.10 (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

N/A

Smoke tests

We recommend following our basic testing guide after this release: Basic testing of Brief Connect

Release-specific tests for v2.5.10

  • Verify UserGroup operations continue to work when deleted Entra ID users exist.
  • Verify workflow editor save operations retain dependent transitions.
  • Verify UserSetting migration from Cosmos DB to MongoDB includes expected records.