# M365 Agents Toolkit: Great tech but lacks developer empathy The M365 ATK shows promise with flexible build toolchains & Bicep deployments, but Microsoft's poor communication & sloppy releases sabotage dev experience. by Andrew Connell Last updated November 11, 2025 9 minutes read --- ## TL;DR M365 ATK has great tech (YAML pipelines, Bicep, flexible architecture) but the execution is maddeningly frustrating. Microsoft resets all project templates without warning, removes features without migration paths, scatters docs everywhere, and treats developer workflow stability as an afterthought. --- ## Understanding the M365 Agents Toolkit The [Microsoft 365 Agents Toolkit](https://marketplace.visualstudio.com/items?itemName=TeamsDevApp.ms-teams-vscode-extension) is simply the next iteration of what we called the Teams Toolkit for VS Code. Microsoft renamed it at the Build conference in May 2025, but under the hood, it’s the exact same tool… just with a fresh name. The M365 ATK consists of two main components: - an extension for both VS Code and Visual Studio - a command-line interface (CLI) Its primary purpose is enabling developers to create Teams apps and agents for Microsoft 365 Copilot using a specific project structure. Projects include an **m365agents[.*].yaml** file in the root that defines the build toolchain and manages provisioning in local, development, production environments. You’ll also find an **appPackage** folder containing everything that gets packaged into the Teams app ZIP file, an **infra** folder with Bicep files for Azure resource provisioning, and an **env** folder storing environment-specific variables. ## The evolution from community solutions to Microsoft’s toolkit The journey here tells an interesting story about Microsoft’s approach to developer tools. Originally, Microsoft provided zero developer tools for Teams apps. The community filled this gap with [Yo Teams](https://pnp.github.io/generator-teams/), a Yeoman generator created by [Wictor Wilen](https://www.linkedin.com/in/wictorwilen/), then a Microsoft MVP and now a Microsoft employee. Microsoft’s first attempt came in July 2020 with Teams Toolkit v1 for VS Code. It was rough, unpopular, and largely ignored. Version 2 arrived in May 2021 with similar reception. Even v3 in November 2021 failed to match developer expectations. Yo Teams remained the dominant choice. ## What the Agents Toolkit gets right The **m365agents.yaml** files are genuinely excellent. They provide granular control over the build toolchain, from Azure provisioning to Teams app creation, dependency validation, and manifest checking. If you’re familiar with GitHub Actions or Azure DevOps Pipelines, you’ll feel right at home. The environment concept works well too. You get separate environments for provisioning (creating resources), deployment (handling things like `npm install`), and publishing (production scenarios). These building blocks, called actions, let you assemble custom pipelines with impressive flexibility. ## Where Microsoft fails developers Despite these technical strengths, the Agents Toolkit demonstrates a fundamental lack of developer empathy that undermines Teams development as a whole. ### Project templates: A masterclass in poor execution Microsoft bakes project templates directly into extension releases, meaning any template issues require waiting for a full toolkit update. There’s no separate versioning, no changelog explaining changes to the templates, and no warning when templates undergo complete overhauls. The September 2025 releases exemplified this problem perfectly. Microsoft completely reset all templates for Teams apps… tabs, bots, message extensions… everything. They introduced brand-new SDKs, the Teams SDK (formerly the Teams AI v2) that developers weren’t familiar with, backed by documentation that remains inaccurate, incomplete, and scattered across multiple sites. ## Documentation scattered like breadcrumbs Finding documentation requires a treasure hunt across learn.microsoft.com, various wikis in GitHub, and source code repositories. Changelogs exist but hide deep in subfolder structures. Pre-release announcements? Practically non-existent. ## The real cost of poor developer experience Microsoft’s approach to the Agents Toolkit reveals a deeper problem: they don’t understand or prioritize developer workflow stability. The drastic project template resets, breaking changes without warning, and documentation that never matches reality create a hostile development environment. ## Conclusion The Microsoft 365 Agents Toolkit embodies a frustrating paradox. Technically, it’s well-architected with powerful features that streamline Teams and Copilot development. Practically, project templates are sloppy. Microsoft needs to prioritize stability, communication, and developer experience over change.