Choosing Your Build Tool: Agent Builder, Copilot Studio, or the Agents Toolkit

The previous article established the fork between describing an agent and building one. This article is the practical follow-up: given that choice, which actual tool do you open? Microsoft provides three, and they line up neatly along a single axis, from the fastest and simplest to the most powerful and hands-on.

1 · Agent Builder: describe it, nothing to install

Agent Builder is a feature built directly into Microsoft 365 Copilot. Choosing “new agent” offers three paths: describe your agent using natural language and let Copilot build it for you (the recommended approach), configure it manually through a dedicated tab, or start from a template built for a specific use case.

There is no separate application to open and nothing to install. This makes Agent Builder the fastest possible route to a working declarative agent, ideal for one person solving their own everyday problem without involving a developer or an IT project.

2 · Copilot Studio: managed, drag-and-drop, department-scale

Microsoft Copilot Studio is a fully managed platform with a drag-and-drop interface, real control over business logic and workflow automation, and hundreds of prebuilt connectors for plugging into other services. Because it is fully managed, a business or IT team does not have to think about infrastructure, hosting, or the underlying plumbing — that is handled for them, along with built-in governance through the Power Platform.

Copilot Studio is designed for small-scale deployments such as department-level solutions, and it supports both declarative agents and, for more demanding needs, custom engine agents too. Its strength is a genuinely low-code experience with prebuilt governance already wired in; its trade-off is somewhat less fine-grained developer control than a full pro-code environment offers, and less mature source-control tooling than a dedicated development toolkit provides.

3 · The Agents Toolkit: the professional developer’s workbench

The Microsoft 365 Agents Toolkit is a pro-code extension for Visual Studio or Visual Studio Code. It gives developers full control over their coding environment, source control, and direct application-programming-interface integration, and it supports building both declarative and custom engine agents with advanced features: custom application-programming-interface actions, richly interactive Adaptive Cards, the Microsoft 365 Agents SDK, a local testing playground, and proper continuous integration and continuous delivery pipelines.

This is the professional developer’s workbench, built for teams that need rigorous testing, full customisation, and an integrated project workflow rather than a drag-and-drop canvas.

4 · How to pick

The pattern across all three tools is a single, simple axis: Agent Builder for speed and simplicity when one person needs one agent quickly; Copilot Studio for a department that needs a managed, governed solution without deep coding; and the Agents Toolkit for a professional development team that needs full control, testing rigour, and a real software project around the agent. Pick based on how much control the task genuinely requires, not on which tool sounds most impressive — the fastest correct answer is very often Agent Builder.

5 · Glossary — every short-form term, spelled out

Agent Builder

A feature inside Microsoft 365 Copilot for quickly building a declarative agent by natural-language description, manual configuration, or template.

Microsoft Copilot Studio

A fully managed, low-code platform with a drag-and-drop interface, prebuilt connectors, and built-in governance for building agents at department scale.

Microsoft 365 Agents Toolkit

A pro-code extension for Visual Studio or Visual Studio Code offering full developer control, local testing, and continuous integration and delivery.

API (application programming interface)

A defined way for one piece of software to call another and exchange data or trigger actions.

Adaptive Card

A structured, interactive card format used to render rich responses and data inside chat and productivity apps.

CI/CD (continuous integration and continuous delivery)

Automated pipelines that build, test, and deploy code changes consistently.