M365 Tenant Tools

Claude + Teams Bot Configurator

Answer a few questions and get the exact configuration files and deployment guide to run a Claude AI bot inside Microsoft Teams.

manifest.json

Complete Teams app manifest v1.17 with your bot identity, scopes, and valid domains pre-filled.

Bot Config

Structured bot-config.json with Claude model settings, rate limits, and hosting preferences.

.env Template

Ready-to-fill environment file with every variable your bot needs, labelled clearly.

Deployment Guide

Printable step-by-step Azure setup and deployment walkthrough tailored to your choices.

ℹ You'll need an Azure subscription and Anthropic API key before deploying. This tool generates the config — the deployment steps are included in your output.

Bot Identity

How your bot will appear to users in Teams

Bot Name

This is the display name users will see in Teams.

Version

Short Description 0 / 80

Shown in the Teams app store listing. Keep it punchy.

Full Description 0 / 256

Explain what the bot does and who it's for.

Organisation Name

Organisation Domain

Used in the package name and valid domains list.

Accent Colour

Claude Configuration

Choose the model and behaviour for your bot

Claude Model

Claude Opus 4.7

Most capable. Complex reasoning, nuanced responses. Higher cost. Best for legal, strategy, and research bots.

Claude Sonnet 4.6 Recommended

Balanced performance and speed. Ideal for most enterprise bots. Best value.

Claude Haiku 4.5

Fastest response times. Highest volume, lowest cost. Best for high-frequency helpdesk bots.

System Prompt

Max Tokens per Response

1024

Controls maximum response length. 1024 is a good default for most bots.

Conversation Memory

Single message

No history. Fastest, lowest cost. Each message treated independently.

Last 5 messages Recommended

Short-term context. Good for most use cases.

Last 10 messages

Extended context. Better for complex ongoing discussions.

Full session

Complete history until session ends. Highest quality, highest cost.

Teams Scope & Deployment

Where your bot will be available and how it'll be hosted

A — Teams Scope (select at least one)

Personal Chat

Users can chat 1:1 with the bot

Team Channels

Bot can be added to team channels and @mentioned

Group Chats

Bot can be added to group conversations

B — User Access

All users in tenant

Anyone in your Microsoft 365 tenant can add and use the bot.

Admin-managed rollout

IT admin controls which users and groups have access via Teams admin centre.

Specific security group

Only members of a named security group can use the bot (you'll configure this in Azure).

C — Rate Limiting

Enable rate limiting

Prevent API cost spikes by limiting messages per user per hour

Messages per user per hour

60

D — Hosting Platform

Azure App Service Recommended

PaaS hosting, auto-scaling, always-on. Best for production bots.

Azure Container Apps

Containerised deployment. Good if you use Docker or CI pipelines.

Azure Functions

Serverless. Pay per execution. Best for low-volume or bursty usage.

Self-hosted

On-premises or third-party hosting. You manage infrastructure.

E — SDK Language

Node.js / TypeScript Recommended

Most Bot Framework examples and community support.

Python

Good if your team prefers Python.

C# / .NET

Best for Microsoft-heavy engineering teams.

F — CI/CD Workflow

Include GitHub Actions CI/CD workflow

Get a ready-to-use workflow file that deploys on push to main

Building your configuration…

Generating Teams app manifest…
Building bot configuration…
Creating environment template…
Writing deployment guide…
Packaging your files…

Configuration Ready

Claude + Teams Bot Configurator

Bot Identity

Claude Configuration

Teams Scope & Deployment

Building your configuration…

Your Bot Configuration is Ready