Release Notes — August 17–21, 2026

Release Notes — August 17–21, 2026

New Features

Official Support for Incident Response in Microsoft Teams

In addition to Slack, you can now respond to incidents from Microsoft Teams as well. In the organization settings, you can choose from three Teams message monitoring modes.

- Threads (default): The bot monitors only threads in which it is @mentioned.

- Monitor All Channels: Monitors all messages in authorized channels. It also temporarily caches messages from threads not linked to incidents to detect potential incidents.

- Emoji Reaction Mode: By default, messages are not read; only messages with triggered reactions in the specified channel are sent to Incident Lake.

You can use Advanced Mode (all-channel monitoring and emoji reactions) on only one of Slack or Teams; if you switch to one, the other will automatically revert to Thread Mode.

Teams' past Commands

In a Teams thread linked to an incident, @bot past When you send this, the system will search for similar past incidents and return the results in the same thread. If the thread is unlinked, then go or link You'll receive a message prompting you to do so.

AI-Driven Progress Recommendations for Incident Response Checklists

AI now periodically reviews Slack and Teams conversations as well as incident notes and suggests "steps that appear to be complete."

- Proposals are always subject to human review; the AI will not automatically complete the step (select "Approve" or "Reject").

- The proposal will include supporting evidence, such as “A message from [Name] on Slack at 2:32 PM stated that the deployment was complete.”

- When you complete a step, you can leave a note explaining your reasoning.

- When a proposal is submitted, a single notification is sent to the Slack or Teams thread where the incident occurred, and you can open it directly by clicking the "Open Checklist" button.

- In the workflow settings, you can now click the phase badge for an SOP step to assign a color to it.

Improvement

Security audit logs are easy to read

Audit log operation names are now displayed as human-readable names rather than internal identifiers. Even older operation names that do not exist in the catalog are automatically formatted and displayed to the extent possible.

Tooltip for Tenant Name

In the tenant switching menu, you can now hover over long, truncated tenant names to view the full name.

Correction

- Teams: Fixed an issue where, as the thread ID associated with an incident, the ID of a reply—rather than the ID of the first post in the thread—might sometimes be saved.

- Teams: Immediately after setting up a monitoring channel, confirmation replies and incident suggestions now arrive without the administrator having to manually @mention the bot.

- Teams: The space immediately after a mention is   cases where it arrives as, orpast. We fixed an issue where commands weren't recognized when a symbol was appended to the end, as shown here.