Working with the Ciroos AI SRE Teammate in Microsoft Teams
This guide explains how to install, connect, and use Ciroos inside Microsoft Teams. Ciroos brings an AI SRE Teammate into your channels so on-call engineers, DevOps, and operations teams can investigate incidents faster, correlate signals across systems, and move toward more autonomous operations — without leaving Teams.
1. About Ciroos in Microsoft Teams
Ciroos is an AI SRE Teammate that helps reduce toil and shorten incident investigations. Once connected to Microsoft Teams, you can ask Ciroos questions directly in a channel, and it will pull from your connected data sources, correlate signals, and reason about the likely root cause of an incident.
During active incidents, Ciroos can create and manage dedicated war-room channels so responders have a focused space to collaborate. It assists with AI-generated analysis and recommendations, while engineers stay in control and review its output before acting.
Who this guide is for
- End users — engineers, on-call responders, and operators who use Ciroos day to day in Teams.
- Administrators — Ciroos org admins and Microsoft 365 admins who perform the one-time setup (Sections 3 and 4).
What you need an account for
To use this app you need an active Ciroos account. Contact support@ciroos.ai if you don’t have one yet.
2. Key concepts
A few terms appear throughout this guide:
- Cluster URL — the address of your organization’s Ciroos environment, for example jaw1-5539.ciroos.ai. Your Ciroos org admin connects this once.
- Project — a logical grouping of services or workloads in Ciroos. Channels can be linked to a specific project.
- Cluster — a Kubernetes cluster visible to Ciroos. Channels can be linked to a specific cluster.
- Default channel — the channel Ciroos treats as your organization’s primary workspace for updates.
- AI Assistant — mention the bot with a plain-language question and Ciroos responds with analysis and recommendations.
3. Before you begin
Make sure the following are in place before installing the app:
- An active Ciroos account and your organization’s Ciroos Cluster URL (for example, jaw1-5539.ciroos.ai).
- Permission to add apps in Microsoft Teams, plus a target channel to host the bot.
- A Microsoft 365 administrator available to grant one-time organization consent.
- A Ciroos org admin to complete the cluster connection step.
4. Installation and initial setup
This one-time setup connects your Teams environment to Ciroos. Steps 4.3 and 4.6 require an administrator; the rest can be completed by any team member.
4.1 Add the Ciroos app to Teams
In Microsoft Teams, open the Apps panel and search for Ciroos. Open the listing to review the overview and requested permissions, then click Add to install it.
The Ciroos app listing with the Add button.
4.2 Choose where to use the app
Teams asks where you would like to use the app. Select the channel that will act as your team’s default Ciroos workspace and click Go.
Selecting a channel to host the Ciroos bot.
4.3 Connect your Ciroos cluster (admin)
The bot posts a Ciroos welcome card in the channel. A Ciroos org admin enters the organization’s Cluster URL in the field and clicks Connect to Ciroos to begin linking Teams to your Ciroos environment.
The Ciroos welcome card, where an org admin enters the Cluster URL.
4.4 Log in to Ciroos
Once the Cluster URL is verified, the card confirms the cluster and shows an Admin Login button. The org admin clicks it to authenticate; Teams confirms with ‘Your response was sent to the app’ while login completes.
The verified card — an org admin clicks Admin Login to authenticate.
4.5 Confirm the connection
After a successful login, the bot replaces the setup card with a Ciroos Connected confirmation showing your Organization ID. Team members can now mention @ciroos to log in and access their workspace.
Ciroos Connected confirmation with the organization details.
4.6 Approve Microsoft 365 permissions (admin)
Ciroos needs organization-level permissions to discover teams and channels. The setup card shows an App Permission Required notice with an Approve App Permissions button — a Microsoft 365 admin clicks it, or shares the card with an admin who can.
The setup card prompting for Microsoft 365 admin approval.
The button opens Microsoft’s consent dialog. The administrator reviews the requested permissions and clicks Accept to grant them for the whole organization. This is a one-time step.
Granting organization consent in the Microsoft dialog.
Setup complete
Once consent is granted, Ciroos can discover your teams and channels and the integration is fully provisioned. Everyday use is covered in the sections that follow.
5. Linking your personal account
Each team member links their own Ciroos account the first time they use the bot. In a channel where Ciroos is installed, mention the bot and use the login command:
@ciroos login Links your account to Ciroos.
Follow the prompt to authenticate. Once linked, you can run commands and chat with the AI assistant from any channel where Ciroos is present.
6. Command reference
Interact with Ciroos by mentioning the bot followed by a command, for example
@ciroos help . The bot recognizes the following commands, grouped by category.
General
| Command | What it does |
|---|---|
| help | Show the help message with all available commands. |
| status | Check your connection status and linked account. |
| login | Link your account to Ciroos. |
Channel setup
| Command | What it does |
|---|---|
| set-default-channel | Set the current channel as the organization default. |
| set-project-channel <id> | Link the current channel to a specific project. |
| set-cluster-channel <id> | Link the current channel to a specific cluster. |
Discovery
| Command | What it does |
|---|---|
| list-projects | List the projects you can access. |
| list-clusters | List your Kubernetes clusters. |
AI assistant
| Command | What it does |
|---|---|
| <message> | Ask the AI assistant a question in plain language. |
You can always view this list inside Teams by mentioning the bot with the help command:
The Ciroos bot command reference, shown by @ciroos help.
7. Common workflows
7.1 Set up your channels
Linking channels helps Ciroos route updates and scope its context. Run these commands from the channel you want to configure:
- Make a channel the org default: @ciroos set-default-channel
- Link a channel to a project: @ciroos set-project-channel <id>
- Link a channel to a cluster: @ciroos set-cluster-channel <id>
Tip
Not sure which ID to use? Run list-projects or list-clusters first to find the right identifier.
7.2 Discover projects and clusters
Use the discovery commands to see what Ciroos can access:
- @ciroos list-projects — shows the projects available to you.
- @ciroos list-clusters — shows your Kubernetes clusters.
The IDs returned by these commands are what you pass to the channel-setup commands above.
7.3 Chat with the AI assistant
To ask the assistant anything, mention the bot followed by your question in plain language. For example:
@ciroos why is checkout latency spiking in the payments service?
Ciroos responds with analysis and recommendations drawn from your connected data sources. You stay in control — review its findings before taking action.
7.4 Investigate an incident
During an active incident, Ciroos helps responders move quickly:
- Ask in-channel. Pose questions to Ciroos as the incident unfolds; it correlates signals across your systems to surface likely causes.
- Use a war-room. Ciroos can create and manage a dedicated war-room channel so responders have a focused space to collaborate.
- Review and act. Ciroos provides AI-generated analysis and recommendations; engineers review the output and decide what to do next.
- Confirm scope. Linking the channel to the relevant project or cluster (Section 7.1) helps Ciroos focus on the right environment.
8. Verify your connection
Any team member can confirm their link at any time by mentioning the bot with the status command:
@ciroos status
The bot returns a Connection Status card showing whether you are connected, along with the linked account email and organization.
Checking connection status with @ciroos status.
9. Troubleshooting & FAQ
The bot says I’m not connected
Run @ciroos login to link your account, then @ciroos status to confirm. If the problem persists, your organization may not have completed setup (Section 4).
Commands aren’t recognized
Make sure you mention the bot first (for example, @ciroos help) and that you are in a channel where Ciroos is installed.
“App Permission Required” keeps appearing
Team and channel discovery needs Microsoft 365 admin consent. Share the setup card with a Microsoft 365 admin so they can click Approve App Permissions (Section 4.6).
I can’t connect the cluster
Confirm you are using the correct Cluster URL (for example, jaw1-5539.ciroos.ai) and that a Ciroos org admin is performing the step. Contact support if the URL won’t verify.
10. Support & resources
Need a hand? The Ciroos team is happy to help.
Email support@ciroos.ai with your organization name and a description of the issue. Including the output of @ciroos status helps us assist you faster.