Skip to main content
Transform your Microsoft Teams workspace into a cloud operations command center. Interact with CloudThinker agents, receive alerts, and run operations without leaving Teams.

​
Setup

1

Navigate to Integrations

Open the workspace selector in the sidebar, click Workspace Settings, then navigate to Integrations and find Microsoft Teams
2

Connect with Teams

Click Connect with Teams and authenticate via Microsoft OAuth. An Azure AD admin may need to grant consent for your organization.
3

Install the Bot

Select which Teams to add the CloudThinker bot to and confirm the installation
4

Map Teams to Workspaces

Map your Microsoft Teams to CloudThinker workspaces so agents know which cloud accounts to operate on
5

Configure Notifications

Optionally select channels for each notification type (cost alerts, security findings, incident updates)
6

Test

Try @CloudThinker alex show AWS costs in a channel to verify the connection

​
Syntax

In Teams, prefix all commands with @CloudThinker: 
@CloudThinker alex analyze EC2 spending trends
@CloudThinker oliver audit security groups for public access
@CloudThinker tony check database performance
@CloudThinker kai review EKS cluster health
All CloudThinker Language syntax works in Teams — just add the @CloudThinker prefix.

​
Examples

​
Quick Queries

@CloudThinker alex what's our AWS spending this week?
@CloudThinker oliver any critical security findings?
@CloudThinker tony why are queries slow on production?
@CloudThinker kai check pod status in payment namespace

​
With Tools

@CloudThinker alex #dashboard cost trends by service
@CloudThinker oliver #report weekly security summary
@CloudThinker tony #recommend index optimizations
@CloudThinker kai #alert on pod OOMKilled events

​
Multi-Agent

@CloudThinker anna coordinate investigation of latency spike
@CloudThinker alex and tony analyze database infrastructure costs

​
Alerts

Configure agents to send alerts to Teams channels: 
@CloudThinker alex #alert daily spend exceeds $5,000 → #cloud-ops
@CloudThinker oliver #alert security group changes → #security
@CloudThinker kai #alert pod failures in production → #k8s-alerts

​
Channel Patterns

ChannelUse Case
#cloud-opsGeneral infrastructure operations and cost alerts
#securitySecurity findings and compliance updates
#incidentsActive incident investigation and coordination
#reportsScheduled reports and summaries

​
Differences from Slack

Microsoft TeamsSlack
Admin consentAzure AD admin consent required for org-wide installSlack workspace admin approval
Rich messagesAdaptive Cards for structured responsesBlock Kit for structured responses
Workspace mappingTeam-to-workspace mappingChannel-to-workspace mapping
AuthenticationMicrosoft OAuth / Azure ADSlack OAuth

​
Troubleshooting

  • Check if the CloudThinker bot is installed in the team
  • Verify you’re using @CloudThinker agent syntax (not just agent)
  • Confirm agents are configured in the CloudThinker console
  • Check Azure AD admin consent status
  • Check alert configuration in CloudThinker Settings
  • Verify Teams channel notification settings
  • Ensure the bot has permission to post in the target channel
  • Ask your Azure AD admin to re-grant consent for the CloudThinker app
  • Check workspace admin permissions in CloudThinker
  • Remove and re-add the bot to the team

​
Permissions

CloudThinker in Teams uses your workspace’s CloudThinker permissions. Users can only access agents and connections their CloudThinker account permits.

CloudThinker Language

Complete syntax reference for all commands

Slack Integration

Set up CloudThinker in Slack