What's New: Business Central Integration with Microsoft Copilot Studio (2026 release wave 1)
Business Central integration with Microsoft Copilot Studio (2026 release wave 1): building a no-code agent that reaches Business Central through the Power Platform connector or the MCP server, publishing it to Teams and Microsoft 365 Copilot chat, and how Copilot credits apply to licensing.
- Introduction to Copilot Studio and Agent Building
- Agent Architecture and Components
- MCP Server Technology and Business Central Integration
- Demo: Building a Laptop Agent in Copilot Studio
- Agent Tools and Channel Publishing
- Demo: Laptop Agent in Microsoft 365 Copilot Chat
- Licensing and Resources
Overview
The video explains how Copilot Studio is used to build agents without coding and how those agents connect to Business Central. It covers agent architecture, the Business Central Power Platform connector, and MCP server technology, which was added to Business Central in a previous wave as preview.
A demo builds a laptop agent in Copilot Studio and then uses it in Microsoft 365 Copilot Chat. The video also covers agent tools, knowledge sources, publishing channels, and licensing based on Copilot credits.
Key points
- Copilot Studio is used to build agents without coding; agents are configured with natural language instructions, business documentation, and web knowledge sources.
- Agents can use several tool types: connector tools, custom prompts, Power Automate flows, and MCP. The agent decides which tool to use based on the request.
- Business Central has a special Power Platform connector that lets agents call Business Central APIs, with extra functionality for agent interaction.
- The MCP server lets agents work with Business Central data more easily; it was added in a previous wave as preview.
- An agent is published to a channel. The video covers Teams and Microsoft 365 Copilot chat, and also lists WhatsApp, Facebook Messenger, email, and text messaging.
- Copilot Studio is licensed differently from the rest of Power Platform: Power Platform usage rights are included in the Business Central license, but Copilot Studio usage needs Copilot credits.
- Copilot credits are shared across all agents in Power Platform.
Features
| Feature | Status | At |
|---|---|---|
| Copilot Studio Agent Building | status not stated, demoed | 0:07 |
| MCP Server for Business Central | status not stated, demoed | 2:42 |
| Business Central Power Platform Connector | status not stated, demoed | 2:27 |
| Copilot Studio Agent Knowledge Sources | status not stated, demoed | 3:53 |
| Copilot Studio Multi-Tool Support | status not stated, demoed | 5:10 |
| Publishing Agents to Multiple Channels | status not stated, demoed | 1:46 |
| Copilot Studio Licensing Model | status not stated | 7:48 |
Quotes
- 0:22 “Copilot Studio is perfect for building agents without actually coding experience.”
- 1:46 “Copilot Studio agent is actually published to a specific channel. And we will be talking about publishing to Teams and Microsoft 365 Copilot chat.”
- 2:27 “It is connected to Business Central through a Power Platform connector. We have a special connector for Business Central.”
- 2:57 “we added to Business Central in a previous wave as preview”
- 7:48 “Copilot Studio is licensed slightly differently than the rest of Power Platform. Power Platform usage rights are included in Business Central license. Copilot Studio”
- 8:11 “Copilot credits. And that is common um value or currency for all agents across Power Platform in Business Central.”
Disclaimers in the video
- 2:57 preview: we added to Business Central in a previous wave as preview
Presenters (as heard): Błażej Kotełko.