Skip to main content

v2026.08

· 5 min read
Marius Nergård
Marius Nergård
Product owner Breeze @ Sotera

Breeze now connects to AI assistants. You sign in with your own account, approve what the assistant may reach, and then ask it about users, Tenants, Credentials and orders instead of clicking through the portal to find them. The release also lets administrators reopen Duo ID requests that closed too early, and fixes two cases where a search returned the wrong results.

What this release gives you​

Ask Breeze a question instead of navigating to the answer. Breeze has a built-in MCP server, so Claude and other MCP-compatible assistants can look things up on your behalf. The connection runs as you: your sign-in, your roles, read-only. Employees who work across a Tenant tree notice it first — "what's the status of order 2426?" is a complete question, with no need to know which Tenant the order sits under. Nothing connects until your organization allows it: assistant access is off for every Domain and Tenant until an administrator switches it on.

Duo ID requests you can recover. A request that closed too early or was rejected by mistake can be reopened, and it keeps its original link. Links already sent out keep working, so nothing has to be reissued.

Summary of Changes​

New Features​

Improvements​

Bug fixes​

New Features​

Connect AI Assistants to Breeze​

Breeze includes a built-in MCP server, so Claude — or any other MCP-compatible assistant — can be connected to your Breeze account and answer questions about your data.

Highlights:

  • You sign in with your own Breeze account and approve access on a consent screen that names the application asking and where your access will be sent.
  • Read-only, and limited to what your roles already allow: users, Tenants, Credentials, orders and products.
  • One question finds a user, Tenant or order anywhere in your Tenant tree. You don't have to say which Tenant it sits under.
  • Off until your organization turns it on, in two deliberate steps: a Domain administrator enables MCP access for the Domain, then a Tenant administrator with the Super Administrator role turns it on for their own Tenant under Tenant settings → Security. While the Domain is off, the Tenant setting stays hidden rather than showing a switch that can't take effect.
  • Revoke access at any time from Connected apps on your account page. Every change to either organization-level switch is recorded in the Tenant's or Domain's audit history.

Because both switches start off, no assistant can reach Breeze until an administrator turns them on — connections that already existed included. Turning a Tenant back on revives its connections and nobody has to approve access again, though an assistant that dropped the connection meanwhile may ask you to reconnect.

One thing to know before your organization adopts this: data an assistant reads through the connection is shared with the assistant and its provider. That sharing sits under your organization's agreement with the provider — it is not covered by the Breeze data processing agreement. The consent screen states this before anyone approves, and connecting is each organization's own decision.

Why it matters:

Employees answer routine "where is this order?" questions without opening the portal, and nobody reaches data through an assistant that they couldn't already open themselves.

Learn more: Connect an AI assistant to Breeze

Security details: Compliance & Data Protection and Authentication & Access Control

Improvements​

Reopening Closed Duo ID Requests​

Administrators can reopen a Duo ID request that was closed too early or rejected by mistake. A reopened request keeps its original link, so links already sent out keep working and don't have to be reissued. The credential list also shows and filters on a Duo ID expired status, which makes the requests waiting for this attention easy to find.

Learn more: Credential Statuses

Bug fixes​

Duo ID Requests Expiring Too Early​

Duo ID requests created without an explicit expiration date and without an email notification could expire after about two days, instead of the retention period configured on the Credential Template. These requests now follow the template's configured cleanup period.

Filtering Credentials by Order​

Filtering credentials by order returned every credential on the Tenant instead of only that order's — the filter was accepted but never applied, so results looked complete while being wrong. Filtering by order now returns exactly the credentials belonging to that order.