Running Semantic Kernel or AutoGen in production?Plan your move to Microsoft Agent Framework

Microsoft Teams Bots & Microsoft 365 Copilot Agents

We build agents that people use in Microsoft Teams and Microsoft 365 Copilot, with the Microsoft 365 Agents SDK, Teams SDK or Copilot Studio, and we move existing Bot Framework bots onto Microsoft’s current SDKs.

Book a free discovery call (opens in a new tab)Contact us

What we build for Teams and Microsoft 365 Copilot

Agents in Teams chats, channels and meetings

Typical examples are IT and HR helpdesks that answer questions and raise tickets. For an agent built only for Teams, we usually use Teams SDK.

Custom engine agents in Microsoft 365 Copilot

When an agent needs its own orchestration, models or complex workflows, we build a custom engine agent in code, hosted outside Microsoft 365, typically on Azure.

Declarative agents

When Microsoft 365 Copilot’s own orchestrator and models are enough, a declarative agent configures it for a specific task with your instructions, knowledge and actions. There is no model or orchestrator to host; any APIs its actions call are hosted separately.

Microsoft’s comparison of declarative and custom engine agents (opens in a new tab)

One agent for Teams, Microsoft 365 Copilot and your website

With the Microsoft 365 Agents SDK, which Microsoft positions for multichannel agents, one agent can serve Teams, Microsoft 365 Copilot, your website and other apps. For a website assistant on its own, see our AI chatbot development service.

Microsoft Agent Framework for the AI logic

We use Agent Framework as the orchestrator inside an Agents SDK agent: the Agents SDK handles channels and conversation state, and Agent Framework handles the AI logic. Microsoft documents this pattern, with an official .NET sample of this pattern (opens in a new tab) and Python sample of this pattern (opens in a new tab) on GitHub.

Microsoft Agent Framework development

Agents SDK, Teams SDK or Copilot Studio?

We build with all three. If you are unsure which fits, book a free discovery call (opens in a new tab) and we will tell you plainly, including when Copilot Studio is enough.

Agents SDK, Teams SDK and Copilot Studio compared, as of October 2026
OptionWhat it isUse it when
Microsoft 365 Agents SDKMicrosoft’s framework for conversational agents, generally available in C#, JavaScript and Python.The agent must also reach your website, custom apps or non-Microsoft platforms, not only Teams and Microsoft 365 Copilot.
Teams SDKMicrosoft’s SDK for agents and apps on Teams, formerly the Teams AI Library, generally available in C#, TypeScript/JavaScript and Python. Its agents can also reach Microsoft 365 Copilot. It has deprecated its own AI libraries, so we pair it with Microsoft Agent Framework or another AI framework.The agent is built specifically for Teams, such as a collaborative agent in channels and meetings. It can later be extended to other channels with the Agents SDK.
Copilot StudioMicrosoft’s graphical, low-code studio for building and managing agents, fully managed by Microsoft.A low-code tool covers the job, and you want to build quickly without heavy development work.

The options can be combined: an Agents SDK agent can call Copilot Studio agents, currently only those on Copilot Studio’s standard harness.

For agents on Foundry Agent Service, publishing from Microsoft Foundry to Teams and Microsoft 365 Copilot is generally available. Microsoft lists limitations, including no streaming responses or citations in published agents, so we check them against your needs first.

Moving off the Bot Framework SDK

The Bot Framework SDK and Bot Framework Emulator are archived on GitHub and no longer updated, and Microsoft stopped servicing Bot Framework SDK support tickets on 31 December 2025. Microsoft says existing bots continue to function, but bots that depend on LUIS, QnA Maker or Orchestrator must move to other tooling because those online services are already disabled.

The retirement also covers developer tools such as Bot Framework Composer and the Bot Framework CLI. It does not cover Azure Bot Service: Microsoft’s current documentation still uses it to connect Microsoft 365 Agents SDK agents to Teams and Microsoft 365 Copilot. Since 31 July 2025, Microsoft no longer supports creating new multi-tenant Azure bots; new bots should use a single-tenant app registration or a user-assigned managed identity, and existing multi-tenant bots continue to function.

Microsoft’s migration path is to update the bot to the Agents SDK, which it calls the evolution of the Bot Framework SDK, or to Teams SDK for bots that only target Teams. For a SaaS platform instead, it suggests Copilot Studio.

Microsoft’s Bot Framework SDK to Agents SDK migration guidance (opens in a new tab) lists features that do not carry over, including Adaptive Dialogs, Composer artefacts and LUIS and QnA Maker tooling. For local testing, Microsoft 365 Agents Playground replaces the Bot Framework Emulator.

Our write-up on the end of the Bot Framework SDK (opens in a new tab) explains what it means for existing bots. This is how we migrate one.

  1. Inventory and tests first

    We list the bot’s dialogs, channels, integrations, sign-in and Azure Bot registration, record test conversations for the paths people use most, and recommend the target SDK in writing.

  2. Rebuild what does not carry over

    Logic built on Adaptive Dialogs, Composer, LUIS, QnA Maker or Orchestrator is rebuilt in code, or replaced with a language model where that is simpler.

  3. Run side by side

    We test in Agents Playground, then run the new agent alongside the old bot for a small group of users.

  4. Cut over and hand over

    We switch the channels across, register any new Azure Bot as single-tenant, and hand the code and documentation to your team.

Tools we use

  • Microsoft 365 Agents SDK in C#, JavaScript or Python.
  • Teams SDK, with Microsoft Agent Framework or another AI framework for the AI logic.
  • Microsoft 365 Agents Toolkit (formerly Teams Toolkit) in Visual Studio Code, Visual Studio or on the command line.
  • Microsoft 365 Agents Playground (formerly Teams App Test Tool) for local testing.
  • Azure Bot Service, to connect agents to Teams and Microsoft 365 Copilot.
  • Microsoft Entra ID for the agent’s app registration in your tenant, with permissions limited to what it needs.

How we work and what it costs

  1. Discovery call

    A free call about where the agent should run, who will use it and what it must do.

  2. Pilot

    A small agent in a test environment, with success criteria agreed up front and tested on real questions.

  3. Production build

    We deploy into your Microsoft 365 tenant and, where hosting is needed, your Azure subscription, with logging so problems can be traced.

  4. Handover and support

    Code and documentation go to your team. Support runs Monday to Friday, 9 AM to 6 PM IST, as needed or on a monthly retainer.

Consulting
From ₹2,500 (US$40) an hour
Monthly retainer
From ₹2,00,000 (US$4,000) a month
Pilots and fixed-scope projects
Quoted per statement of work

GST is added to Indian invoices. Rate cards by business size and add-ons are on our pricing page.

Sources

Last reviewed by Jagdish Kumawat, Founder & Director

Frequently Asked Questions

Should we build a Teams bot or a Microsoft 365 Copilot agent?

It depends on where people will use it: a Teams bot works in chats, channels and meetings, and a Microsoft 365 Copilot agent works inside Microsoft 365 Copilot. You may not have to choose: agents built with Teams SDK or the Microsoft 365 Agents SDK can reach both.

Our bot uses the Bot Framework SDK — do we have to migrate?

Not immediately: Microsoft says existing bots continue to function, but a bot that depends on LUIS, QnA Maker or Orchestrator must move to other tooling now, because those online services are already disabled. The SDK is archived and no longer updated, and Microsoft stopped servicing its support tickets on 31 December 2025, so we recommend planning a move to the Microsoft 365 Agents SDK or Teams SDK.

Which SDK should we use?

Microsoft positions Teams SDK for agents built specifically for Teams, and the Microsoft 365 Agents SDK for agents that must also reach websites, custom apps or non-Microsoft platforms. Both can reach Microsoft 365 Copilot. If low-code is enough, Copilot Studio may mean you need neither.

Can the agent use our own AI models?

Yes, as a custom engine agent: you bring your own orchestration and models, such as models deployed in Microsoft Foundry. A declarative agent uses Microsoft 365 Copilot’s own orchestrator and models instead.

When is Copilot Studio enough?

When a fully managed, low-code tool covers what the agent must do and your team wants to change it without heavy development work. If you need a fully customised agent, with your own models or orchestration, we recommend the pro-code SDKs.

Do we need Microsoft 365 Copilot licences?

It depends on where the agent runs, such as Teams, Microsoft 365 Copilot or your website, and who will use it. We check the licensing with you, against the subscriptions you already have, before the build starts.

What does an agent for Teams or Microsoft 365 Copilot cost?

Consulting starts at ₹2,500 (US$40) an hour and monthly retainers at ₹2,00,000 (US$4,000); pilots and fixed-scope projects are quoted per statement of work after a free discovery call.

Related services

Free discovery call

Tell us what your agent should do

We'll tell you the simplest approach that will work — Microsoft Agent Framework, Copilot Studio or no agent at all — and what a pilot would involve.

Book a free discovery call (opens in a new tab)Contact us
Mon–Fri, 9 AM–6 PM IST • Reply within 1 business day