Build an Agent in Microsoft Copilot Studio for Business Central (2025)
Building an agent in Microsoft Copilot Studio that reads Business Central data through an MCP server, using the MCP Configurations page in Business Central. It covers publishing the agent to Teams and Microsoft 365 Copilot, and the credit-based Copilot Studio licensing.
- Introduction to Copilot Studio and Agent Architecture
- Model Context Protocol and API Connectivity
- Building an Agent: Demo Setup and Data Configuration
- MCP Configuration and Agent Publishing
- Testing and Using the Agent in Microsoft 365 Copilot
- Licensing and Credits Model
Overview
The video, published 2025-12-03 and about 6 minutes long, explains that Copilot Studio is part of Power Platform and is used to build conversational experiences and agents connected to data. It describes the Model Context Protocol (MCP) as an open protocol for AI systems to talk to business applications, and as an alternative to Power Platform connectors for reaching Business Central APIs.
The demo sets up data, configures MCP in Business Central, publishes the agent, and tests it in Microsoft 365 Copilot. It ends with licensing: Copilot Studio is bought separately from Business Central, through credit packs or pay-as-you-go.
Key points
- Copilot Studio is part of Power Platform and builds agents connected to data, including Business Central data via Power Platform connectors and APIs.
- An MCP server is an alternative to Power Platform connectors for giving an agent access to Business Central APIs.
- Business Central has an MCP Configurations page where you define a configuration that exposes an API (for example items) in read-only mode.
- The demo publishes the agent to channels including Teams and Microsoft 365 Copilot, and tests it in Microsoft 365 Copilot.
- Copilot Studio needs credit packs or a pay-as-you-go subscription, purchased separately and not included in Business Central licensing.
- Users the agent is shared with consume the credits and do not need additional paid user licenses.
Features
| Feature | Status | At |
|---|---|---|
| Copilot Studio agents for Business Central | status not stated, demoed | 0:12 |
| Model Context Protocol (MCP) server for Business Central | status not stated, demoed | 1:17 |
| MCP Configurations page in Business Central | status not stated, demoed | 2:52 |
| Agent publication to multiple channels | status not stated, demoed | 3:46 |
| Copilot Studio credit-based licensing | status not stated | 5:04 |
AL objects mentioned
As heard in the captions. A name that matches one object page by exact type and name links to it; the others stay as named.
- page “MCP Configurations” at 2:52
Not found in BC28-30: page “MCP Configurations”.
Quotes
- 0:12 “Copilot Studio is a part of Power Platform, a product that allows you to build conversational experiences and agents connected to various data.”
- 1:17 “Model context protocol or MCP is an open protocol that allows all AI systems to communicate with the various business applications in a standard”
- 2:52 “there is a new page in called MCP configurations where I define a specific configurations exposing this API with items in a read only”
- 5:21 “for Copilot Studio, you need to buy specific um credits, credit uh packs or pay as you go uh subscription because Copilot Studio um”
- 5:31 “you don’t need to have any additional paid user licenses because your users that that you share the agent with will use and and”
Presenters (as heard): Buko.
