Sazabi in Microsoft Teams: issue cards and agent chat for Teams channels

Last verified on Nov 8, 2026.

Teams is where plenty of engineering orgs already keep their incident conversation, especially when the rest of the company runs on Microsoft 365. The gap is the same as anywhere else: the issue is in one tool, the people are in another.

Sazabi is AI-native observability and security. Its Microsoft Teams integration lets people ask the agent about production from a channel, and puts issue notifications where the on-call team is already reading.

What the Sazabi agent can do with Microsoft Teams

Microsoft Teams is a chat integration and a shared notification channel. The connection runs both ways.

Out of Sazabi. Issue notifications arrive as Adaptive Cards in Teams channels. Which channel gets which event is decided by delivery rules on the project's notification settings. Teams can receive Issue triggered, Issue resolved, Issue ignored, Issue rejected, Issue updated, Issue reopened, Issue still open and Automation run failed. In Teams, Issue updated appears as a reply under the issue's alert, and Issue reopened as a new message.

Into Sazabi. Mention the agent in a channel or chat and it investigates, then answers in the channel with a View in Sazabi link back to the dashboard thread. The conversation is a normal Sazabi thread, with the same messages and tool calls.

Who can ask. Sazabi can add a Teams member who mentions the agent to your organization as a standard member. That check needs a one-time admin consent from a Microsoft tenant admin, which Sazabi can open right after authorization or later from the connection page.

Connecting Teams also hands the agent Teams' MCP tools. You can add your personal Microsoft account under connected accounts so the agent acts as you.

What it helps with

• Asking "show me recent errors in the orders service" without leaving the channel where the team is already talking.
• Sending issues owned by one team to that team's Teams channel and nobody else's.
• Getting a reminder in the channel while an issue is still open.
• Onboarding a colleague who tags the bot before they have a Sazabi login.
• Following a conversation from Teams into the dashboard for the full evidence trail.

A worked example: first mention from a new teammate

Your platform team has the Sazabi bot in a standard channel called Payments On-Call. A newer engineer has no Sazabi account yet, and posts this. The names are fictional.

Payments On-Call
Jordan Lee    @Sazabi show me recent errors in the orders service
Sazabi        Here is what the orders service logged in the last hour...
              View in Sazabi

Because the tenant admin approved consent earlier, Sazabi can verify Jordan belongs to your Microsoft tenant and add them as a standard member. The reply lands in the same channel, and View in Sazabi opens the thread in the dashboard.

Teams' own rules explain the shape of this. A Teams agent in a channel receives messages only when it is directly @mentioned. Replying to one of its messages without a mention doesn't reach it, and @everyone mentions are not supported. So each follow-up question should name @Sazabi again. The Sazabi docs also list the setup that has to be in place first: the app package uploaded from the connection page, the bot added to a standard channel, and a delivery rule if you want cards.

If nothing posts, check the rule first. It must name both the event type and the exact channel, and the app must be in that channel.

How it fits with other integrations

Teams and Slack fill the same chat slot, and a project can use both. For paging, PagerDuty and incident.io take issues as alerts, and Jira holds follow-up tickets. For other tools in this group, browse the integrations index or read about pricing.