What we do
Tools
Industries
Department
How we workLet's talk →
Home/MS Teams/Teams Bot
Microsoft Teams

Building a Teams Bot: Pick the Right Microsoft Tool First

"Teams bot" covers three very different things: a channel that receives alerts, an assistant that answers questions from your documents, and an app that reads and writes your business systems. Microsoft has a different tool for each, and the one most tutorials use, the Bot Framework SDK, is now archived. Start by matching your bot to the tool.

What kind of Teams bot are you building?

The bot needs to Build it with Watch for
Post a message when something happens elsewhere The Workflows app in Teams, which runs on Power Automate. Covered on Teams workflows. It's one-way. Once people need to click a button and have something happen, you're building a real bot.
Answer staff questions from policies, manuals or a knowledge base Copilot Studio, which builds an agent in a browser and publishes it to Teams. Answers are only as good as the documents behind them. Check how Copilot Studio is licensed for your tenant before you build.
Look up or change records in your CRM, ERP or ticketing system A coded bot on the Teams SDK, with Adaptive Cards for the answers. Sign-in. If the bot acts as the user, you need single sign-on, which means an Azure Bot resource.
You already run a Bot Framework bot Leave it running and plan the move to the Teams SDK when you next change it. The Bot Framework SDK no longer gets fixes or support, so new features and security updates won't come.

What a coded Teams bot needs, in order

This is the path for the third row above. Each step is where projects commonly stall.

  1. 1

    Register the bot

    The Teams SDK's CLI or the Teams Developer Portal can create a Teams-managed bot with no Azure subscription. That's fine for a bot that only chats. If it needs single sign-on or OAuth to another service, register an Azure Bot resource instead, which gives you the app ID and secret your code authenticates with.

  2. 2

    Host the code behind an HTTPS endpoint

    Teams sends every message to a URL you give it. The code can run anywhere that endpoint is reachable: Azure, AWS, or your own servers. The Teams SDK is available for JavaScript/TypeScript, C# and Python.

  3. 3

    Write the app manifest

    The manifest names the app, sets its icons and says where the bot can run: personal chat, a team channel, or group chats. A messaging extension, the search or action command in the compose box, is declared here too.

  4. 4

    Design the replies as Adaptive Cards

    Cards carry buttons, dropdowns and inputs that post back to your bot, so a manager can approve a request inside the chat. Plain text replies are fine for answers. Anything people act on belongs in a card.

  5. 5

    Install it in your tenant

    Upload the app package for testing, then publish it to your organization's app catalog. Both depend on your Teams admin allowing custom apps, and an app permission policy can still block it for some users.

    Watch for: a bot that works for its developer and nobody else. That's usually a policy, not a code bug.

Where Teams bots break after launch

It can't message someone who never talked to it

How you'll know: The bot is meant to alert a person first, and nothing arrives.

Fix: A bot needs a conversation reference for each person, saved when they install it or message it. For people who haven't, an admin can install the app for them through Microsoft Graph, which creates the chat and lets the bot save the reference.

Alerts go to people who changed roles

How you'll know: Approvals still reach a manager who moved teams months ago.

Fix: Store who owns what in the system the bot reads from, not in a list inside the bot. Look up the recipient when the alert fires.

Sign-in prompts keep appearing

How you'll know: Users are asked to log in to the bot again and again, or the bot sees their data as someone else.

Fix: Set up single sign-on through an Azure Bot resource and the app's Entra ID registration, so the bot gets a token for the person who's chatting.

The tutorial packages no longer match

How you'll know: Samples reference TeamsFx or Bot Framework packages that throw warnings or won't install.

Fix: Start new bots on the Teams SDK and the Microsoft 365 Agents Toolkit (the renamed Teams Toolkit). Keep the old samples for ideas only.

Questions people ask

Do I need Azure to build a Microsoft Teams bot?

Not always. A Teams-managed bot, created through the Teams SDK CLI or the Developer Portal, needs no Azure subscription. You do need Azure for an Azure Bot resource if the bot uses single sign-on or OAuth to other services. Either way, the bot's code can run wherever you host it.

Can I install a custom Teams bot without publishing it to the app store?

Yes. You can upload the app package for testing, or publish it to your own organization's app catalog so only your staff see it. An admin has to allow custom apps first. The public Teams Store and its review are only for bots you want other companies to install.

Should I still use the Bot Framework SDK for a new Teams bot?

No. Microsoft archived it and ended support at the end of 2025. Existing bots keep running, but new work should start on the Teams SDK, which Microsoft now names as its main toolkit for Teams agents and apps.

What happened to Microsoft Teams Incoming Webhooks?

Microsoft is retiring Office 365 Connectors, including the Incoming Webhook connector, and points people to the Workflows app instead. Workflows can still receive a webhook and post it to a channel. A bot is the better choice when people need to reply or click something, not just read the post.

What are Adaptive Cards in Microsoft Teams?

A message format with buttons, dropdowns and input fields that a bot posts into a chat or channel. When someone fills it in or clicks, the answer goes back to the bot, so approvals and short forms happen right in Teams.

Can a Teams bot message someone who has never interacted with it before?

Only once it has a conversation reference for that person. If they've never installed or messaged the bot, an admin can install the app for them through Microsoft Graph, which opens the chat and gives the bot what it needs to message first.

Copilot Studio or a coded bot: which should we use?

Copilot Studio when the bot mostly answers questions from documents and your team wants to maintain it without developers. A coded bot when it has to read and change records in your own systems with real permissions. Some companies use both, and n-frames builds the coded side.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.