Microsoft redirects Teams agent creation June 30

Microsoft is changing where Teams users build certain Copilot Studio agents at the end of June. Microsoft Learn documentation says that after June 30, 2026, “it will no longer be possible” to use the Copilot Studio for Teams app to create classic chatbots, and that the app will redirect makers to the Copilot Studio web app instead. The change was flagged publicly on May 19 by Microsoft MVP Yamada Yamasaki in a post on X, which pointed users to the documentation. The move affects a specific slice of the Microsoft agent-building workflow: creation inside the Teams app itself. Microsoft’s documentation does not say Teams deployment is ending. Separate Microsoft Learn pages say makers can still publish agents to Teams and Microsoft 365 Copilot after building and publishing them in Copilot Studio. ### What exactly stops working on June 30? Microsoft Learn says the cutoff applies to creating “classic chatbots” in the Copilot Studio for Teams app. After the end of June 2026, that app redirects users to the Copilot Studio web app instead. The same quickstart says users on a Teams plan are limited to creating agents that use classic orchestration in Copilot Studio and can publish those agents only to Microsoft Teams. That means the in-Teams creation path is being removed, while the broader authoring experience shifts to the browser-based Copilot Studio product. ### Does this mean Teams agents are going away? Microsoft’s Teams channel documentation says no. A Microsoft Learn page published this year says users can connect an agent to the Teams and Microsoft 365 Copilot channels after publishing it at least once, and can install it for themselves, share installation links, or show it in the Teams app store. A separate deployment guide says Microsoft Teams remains a supported channel for Copilot Studio agents and outlines Teams-specific issues such as persistent sessions, debugging and version control. The change, as documented, is about where the agent is created, not whether it can run in Teams. ### Why are some users talking about lost generative features? Microsoft’s own product split helps explain that concern. The Teams-specific quickstart says makers with a Teams plan are limited to classic orchestration. By contrast, Microsoft’s release-plan documentation for Copilot Studio says agents optimized for Microsoft 365 and Microsoft 365 Copilot can use newer capabilities including people, Teams messages, Exchange inboxes, Visual Creator and Code Interpreter. Microsoft’s overview page for Copilot Studio also says the Teams app will no longer be used to create classic chatbots after June. Read together, those documents indicate that the richer, newer feature set sits in the broader Copilot Studio and Microsoft 365 Copilot stack rather than in the older in-Teams creation flow. ### Where does Dataverse for Teams fit into this? Microsoft says Dataverse for Teams is the built-in data platform inside Teams for apps, agents and flows. A Microsoft Learn administration page says it lets users build custom apps, agents and flows in Teams by using Power Apps, Copilot Studio and Power Automate. Microsoft’s Copilot Studio administration guidance adds that when a user creates a bot in Microsoft Teams using the Copilot Studio for Teams app, a Dataverse for Teams environment is created for the selected team. That is why some Microsoft ecosystem users, including Yamasaki, describe Dataverse for Teams as the remaining way to preserve a more Teams-native workflow. ### What should existing Teams-based makers do now? Microsoft’s documentation points makers to the Copilot Studio web app for future creation work. Users who still need Teams as the delivery surface can publish agents to the Teams and Microsoft 365 Copilot channels after building and publishing them in Copilot Studio. June 30, 2026 is the date to watch. Microsoft’s next-step documents are the Copilot Studio quickstart for Teams users, the Teams publishing guide, and the Dataverse for Teams environment documentation.