Skip to main content
Use Microsoft Teams to start and continue CloudThinker conversations, route work to specialists, and receive configured notifications.

​
Prerequisites

Setup starts with a CloudThinker organization owner or administrator on a messaging-eligible plan (Team and above). A Global Administrator or Teams Administrator completes Microsoft provider approval and Entra (Azure AD) consent separately. The same person can hold both roles, or they can coordinate the two steps.

​
Required Azure AD permissions

During the OAuth flow, CloudThinker requests the following Microsoft Graph API permissions: Permissions marked Admin consent can only be granted by a Global Administrator or Teams Administrator. During the OAuth flow, admins see a “Consent on behalf of your organization” checkbox:
  • Checked — permissions are granted tenant-wide for all users in the Azure AD tenant. Other admins who connect later won’t need to re-consent.
  • Unchecked — permissions are granted only for the admin’s own account. This is sufficient to complete the setup since the admin personally has the required role to publish the bot.

​
Who should perform each step?

​
Setup

1

Start with a CloudThinker administrator

Sign in as a CloudThinker organization owner or administrator on a messaging-eligible plan.
2

Navigate to integrations

Go to Admin Settings → Integrations and find Microsoft Teams
3

Connect with Teams

Click Connect with Teams and authenticate via Microsoft OAuth.
A Global Administrator or Teams Administrator completes Microsoft provider approval and Entra consent. This provider-side step is separate from CloudThinker organization authorization.
4

Install the bot

Select which Teams to add the CloudThinker bot to and confirm the installation. The bot is published to your organization’s Teams app catalog — this is a one-time action.
5

Map teams to workspaces

Map Microsoft Teams to CloudThinker workspaces. The mapping controls where ordinary Teams messages run.
6

Configure notifications

Configure destinations for each notification type in the notification matrix — the grid that maps each event type to destinations — such as cost alerts, security findings, and incident updates.
7

Test

Start a conversation with @CloudThinker @alex show AWS costs. The @CloudThinker mention starts a CloudThinker thread. Reply in that thread without mentioning @CloudThinker again.

​
Syntax

In Teams, use @CloudThinker to start a CloudThinker thread. Reply in an existing CloudThinker thread without mentioning the bot again. To route a request to a specialist, add the agent’s alias after the bot mention. Talk to agents in plain language. The full pattern is:
  • @agent — who does the work: @alex (cloud), @oliver (security), @tony (database), @kai (Kubernetes), @anna (coordination).
  • #tool (optional) — the output you want: #dashboard, #report, #visualize, #recommend, #alert.
  • Your request — what you need, in your own words. Add any context inline.
See the CloudThinker Language reference for the full syntax.

​
Examples

Quick queries — bot mention, then agent alias, then your question:
Tool tags and multiple agents work the same as in the web app:

​
Alerts

Configure alert notification destinations in the notification matrix. A #alert request and a plain request can raise alerts, but neither can send an alert to a specific channel from within the prompt — destinations come from the notification matrix.

​
Code review notifications

When an AI code review completes, CloudThinker sends a notification to your configured Teams channel as an Adaptive Card, Teams’ interactive card format. The card includes:
  • Severity breakdown — structured table showing counts by severity level (🔴 Critical, 🟠 High, 🟡 Medium, 🟢 Low)
  • Finding details — up to 5 unresolved findings with title, severity label, file path, and line number
  • Resolved count — number of previously identified findings that have been resolved
  • View Review button — direct link to the review dashboard
  • Clean pass — when no issues are found, a simple “No issues found” message
Configure code review destinations and severity thresholds in the notification matrix at Notifications → Review / Pipeline Monitoring. See Notifications Center for details.

​
Troubleshooting

  • Check if the CloudThinker bot is installed in the team
  • Start a new conversation with @CloudThinker and use a literal alias such as @alex for specialist routing
  • Reply in an existing CloudThinker thread without repeating @CloudThinker
  • Confirm agents are configured in the CloudThinker console
  • Check Azure AD admin consent status
  • Check alert configuration in CloudThinker Settings
  • Verify the Teams destination in the notification matrix
  • Ensure the bot has permission to post in the target channel
  • “Missing required permissions” — A Global Administrator or Teams Administrator must complete Microsoft provider approval and Entra consent. This is separate from the CloudThinker organization owner or administrator who starts setup.
  • “Consent on behalf of your organization” — During OAuth, an administrator can select this option to grant permissions tenant-wide. See the Required Azure AD permissions table for the requested scopes.
  • Connection appears successful but bot doesn’t work — Confirm the bot is installed in the team, the team is mapped to the expected workspace, and Microsoft provider approval completed.
  • For any other permission errors, confirm the team-to-workspace mapping or try removing and re-adding the bot to the team.
A CloudThinker organization owner or administrator on a messaging-eligible plan starts setup. A Global Administrator or Teams Administrator completes Microsoft provider approval and Entra consent. These can be different people.
  1. Sign in to CloudThinker as an organization owner or administrator on a messaging-eligible plan
  2. Go to Admin Settings → Integrations → Microsoft Teams
  3. Click Connect with Teams and have a Global Administrator or Teams Administrator complete the Microsoft OAuth flow
  4. The bot is published to your organization’s Teams app catalog
After configuration, start a new CloudThinker thread with @CloudThinker. Replies in that thread do not need another bot mention.

​
Permissions

Global Administrator and Teams Administrator roles govern Microsoft provider approval and Entra consent. They do not replace the CloudThinker organization owner or administrator and messaging-eligible plan required to start setup. During OAuth, the administrator can select “Consent on behalf of your organization” to grant permissions tenant-wide. See the Required Azure AD permissions table above for the requested scopes.

​
CloudThinker permissions

The team-to-workspace mapping selects the workspace a message runs in, and ordinary Teams messages run there regardless of the sender’s CloudThinker role. A sender whose Teams account is not linked to a CloudThinker account runs as the workspace’s owner; when no owner can be resolved, CloudThinker asks the sender to link their account first.

CloudThinker Language

Complete syntax reference for all commands

Slack Integration

Set up CloudThinker in Slack