Skip to main content
Microsoft Teams is a collaboration platform widely used in enterprise environments. Kasava’s Teams integration enables notifications, message syncing, and AI-powered search across your Teams workspace.

Capabilities

FeatureDescription
Notification DeliveryReceive automated notifications about GitHub activity and documentation updates
Message SyncSync channel messages for AI context and searchability
Channel ManagementView and select channels across your Teams workspace
AI SearchSearch and analyze Teams conversations using natural language
OAuth IntegrationSecure authentication via Microsoft identity platform

Connecting Microsoft Teams

Kasava supports two connection methods for Microsoft Teams: OAuth for full workspace access, and Webhooks for simple notifications. OAuth provides full access to channels, messages, and AI features.
1

Navigate to Settings

Go to Settings in the sidebar, then select IntegrationsSettings navigation with Integrations highlighted
2

Find Microsoft Teams

In the Communication section, locate the Microsoft Teams integration cardMicrosoft Teams integration card in Communication section
3

Start Connection

Click the Microsoft Teams card to open the connection page, then click Connect Teams WorkspaceMicrosoft Teams integration page with Connect button
4

Sign in to Microsoft

You’ll be redirected to Microsoft’s sign-in page. Enter your Microsoft 365 credentialsMicrosoft sign-in screen
5

Authorize Access

Review the permissions Kasava is requesting and click AcceptMicrosoft OAuth consent screen
6

Complete Setup

After authorization, you’ll be redirected back to Kasava. The integration status will show as connectedConnected status with green checkmark
Kasava uses Microsoft’s OAuth 2.0 authentication. Your Microsoft credentials are never stored—only an access token for API calls.

Webhook Connection

Webhooks are useful for simple notification delivery without full workspace access.
1

Open Microsoft Teams

Navigate to the channel where you want to receive notifications
2

Access Channel Settings

Click the three-dot menu () next to the channel name
3

Manage Connectors

Select Connectors (or Workflows in newer Teams versions)
4

Add Incoming Webhook

Find Incoming Webhook and click Configure
5

Configure Webhook

  • Give the webhook a name (e.g., “Kasava Notifications”)
  • Optionally upload an image
  • Click Create
6

Copy Webhook URL

Copy the webhook URL (starts with https://outlook.office.com/webhook/...)
7

Configure in Kasava

In Kasava, go to Settings > Integrations > Microsoft Teams, enter a name for the integration, and paste your webhook URL
Each webhook is tied to a specific channel. Create separate webhooks if you need to send notifications to multiple channels.

Managing Your Connection

After connecting via OAuth, click Manage on the Microsoft Teams integration card to access configuration options.

Connection Status

View your workspace details:
  • Connection Status - Whether the integration is active
  • Organization - Your Microsoft 365 organization name
  • Last Sync - When data was last synchronized

Sync Settings

Configure how Kasava syncs your Teams data:
SettingDescription
Historical DataNumber of days to sync (1-90 days, default: 30)
Sync MessagesImport channel messages for AI context and search
Team SelectionChoose specific teams to sync
Channel SelectionChoose specific channels within teams
Click Sync Now to manually trigger a sync of your workspace data.

Token Management

If you experience connection issues, click Refresh Token to renew your OAuth credentials.

Viewing Channels

After connecting via OAuth, you can view all accessible channels:
1

Open Integration Settings

Go to Settings > Integrations and click Manage on Microsoft Teams
2

View Channel List

The Channels section shows all teams and channels you have access to
3

Select Channels

Choose which channels to include in message syncing
Channels are organized by team:
  • Team Name - The parent team
  • Channel Name - Individual channels within the team
  • Membership Type - Standard, Private, or Shared

Notification Channels

Set up Microsoft Teams as a notification destination to receive automated updates from Kasava.

Creating a Notification Channel

1

Go to Notification Settings

Navigate to Settings > Notifications
2

Add Channel

Click Add Channel and select Microsoft Teams as the channel type
3

Configure Channel

  • Channel Name - A friendly name (e.g., “Engineering Updates”)
  • Teams Webhook URL - Paste your webhook URL from Teams
4

Save Channel

Click Create Channel to save. You can toggle channels on/off as needed.

Available Notifications

Configure which events send notifications to Teams:
  • Documentation Updates - When auto-generated documentation is ready
  • Repository Activity - New commits, PRs, and issues
  • Product Updates - Roadmap item status changes
  • AI Digests - Scheduled summary reports

Using Teams in AI Chat

Once connected via OAuth, you can search and interact with Teams using natural language in Kasava’s AI chat:

Example Commands

  • “Find Teams messages about the Q4 roadmap”
  • “Search Teams for discussions about the API migration”
  • “Show me recent messages in the Engineering channel”
  • “Send a message to the Product Updates channel”
The AI assistant uses your synced Teams data to find relevant conversations and can send messages on your behalf.

AI Features

Kasava indexes synced Teams messages to enable semantic search:
  • Natural language queries - Ask questions in plain English
  • Cross-channel search - Find messages across all synced channels
  • Team filtering - Narrow results to specific teams

Context Building

Synced Teams messages provide context for AI features:
  • Include team discussions when generating documentation
  • Reference past decisions in planning documents
  • Build comprehensive project timelines from conversations

Permissions

Kasava requests the following Microsoft Graph permissions during OAuth:
PermissionPurpose
Team.ReadBasic.AllList teams you’re a member of
Channel.ReadBasic.AllList channels in your teams
ChannelMessage.Read.AllRead messages from channels
User.ReadAccess your basic profile information
ChannelMessage.SendSend messages on your behalf
Kasava only accesses teams and channels where you are a member. Admin consent may be required by your organization’s Microsoft 365 administrator.
Some organizations require admin consent for third-party applications. If you see an “Admin approval required” message:
  1. Contact your Microsoft 365 administrator
  2. Share the Kasava application ID for review
  3. Once approved, return to Kasava and try connecting again
If your organization has strict policies, the webhook connection method works without admin approval.

Disconnecting Microsoft Teams

To disconnect your Teams workspace:
  1. Go to SettingsIntegrations
  2. Click on the Microsoft Teams integration
  3. Click Manage
  4. Click Disconnect in the settings
  5. Confirm the disconnection
Disconnecting Microsoft Teams will stop all message syncing and notification delivery. You may also want to remove the Kasava app from your Microsoft 365 account in your Microsoft account settings.

Troubleshooting

Your Microsoft 365 organization may require admin consent for third-party apps. Contact your IT administrator to approve Kasava, or use the webhook connection method which doesn’t require admin approval.
Verify that message syncing is enabled in your integration settings. Click Sync Now to trigger a manual sync. Note that syncing large workspaces may take several minutes.
Check that your webhook URL is correct and hasn’t expired. Teams webhooks can be disabled by workspace administrators. Try creating a new webhook if the current one isn’t working.
Kasava can only access teams and channels where you are a member. For private channels, ensure you’ve been added as a member.
Microsoft OAuth tokens expire periodically. Click the integration card and click Refresh Token to renew your connection. If that fails, disconnect and reconnect the integration.
This typically means the required Microsoft Graph permissions weren’t granted during OAuth. Try disconnecting and reconnecting, ensuring you accept all requested permissions.

Security

  • All OAuth tokens are encrypted at rest
  • Webhook URLs are stored securely and never exposed in logs
  • You can revoke Kasava’s access anytime from your Microsoft account settings
  • Kasava uses Microsoft’s OAuth 2.0 with PKCE for enhanced security
  • Data is transmitted over HTTPS only