Email this post as a PDFAI and agents · 31 October 2026 · 10 min read

Agentic AI in Business Central: What It Is, What Works Today, and Where It's Going

Agentic AI is now part of Business Central. Microsoft ships agents that draft sales orders, process supplier invoices and handle expenses, and since April 2026 any compliant AI agent can connect to BC through Microsoft's MCP server. What agentic AI is in plain terms, what BC can do with it today, what it means for developers, how to get your system ready, and where it is heading.

Contents
  1. What agentic AI actually is
  2. What Business Central can do today
  3. The MCP server: opening Business Central to any agent
  4. What it means for AL developers
  5. Getting your Business Central ready for agents
  6. Where it's heading
  7. Where to start
  8. Sources

Agentic AI is now part of Business Central. Microsoft ships agents that draft sales orders, process supplier invoices and handle expenses, and since April 2026 any compliant AI agent can connect to BC through Microsoft's MCP server.

For the last couple of years, "AI in ERP" mostly meant a chat box: you asked Copilot something, and it answered or drafted some text. That is useful, but it still leaves a person doing the work. Agents change that. They take a task, carry it out across several steps, and come back to you only when they need a decision.

This article explains what agentic AI is in plain terms, what Business Central can actually do with it today, what it means for developers, how to get your system ready, and where I think it's heading. I'm writing as an independent BC consultant who spends a lot of time on implementations, NAV upgrades and project rescues, so the focus is practical.

What agentic AI actually is

Agentic AI is software that pursues a goal by deciding and taking its own next steps, rather than producing one answer to one prompt.

A chatbot works in a single exchange: question in, answer out. An agent works in a loop. It reads the goal, plans a step, acts, checks what came back, and decides what to do next. It keeps doing this until the job is done or it reaches a point where a person needs to decide.

The loop repeats without anyone stepping in. The person comes in at the start, with the goal, and at the end, to approve the work.

Think of a capable new starter in your accounts team. You don't tell them which buttons to press. You say "process this week's supplier invoices", and they open the inbox, match each invoice to a purchase order, ask you about the odd one that doesn't fit, and leave the rest ready for you to approve.

Agentic systems are built from four parts:

  • A reasoning model that can plan, cope with surprises and explain what it did.
  • Tools that let it act, such as reading email, querying data, creating documents and calling APIs.
  • Context and memory so it knows what it has already done and what your rules are.
  • Guardrails that limit what it may touch, and set out what needs human sign-off and how every action is logged.

The last part matters most in an ERP. An agent that can post to the general ledger needs the same level of control you would give a person with that access, or more.

What Business Central can do today

Business Central has three Microsoft-built agents in use today, plus a common set of controls for supervising them. Version 29 (the 2026 release wave 2, rolled out in October) mostly improved these agents and their controls rather than adding new ones.

AgentWhat it handlesWhere it stands in BC29
Sales Order AgentWatches a sales mailbox, reads customer requests for quotes and orders, checks item availability, and drafts the quote or order with a reply for a person to reviewAvailable; started from the Role Center
Payables AgentReads supplier invoices from an AP inbox, handles PO and non-PO invoices, and learns from the mapping corrections users makeGenerally available; BC29 improves purchase order matching using line amounts and expected receipt dates
Expense AgentProcesses employee expense claims, including mileage, VAT, withholding tax, duplicate checks and approvalsPublic preview; BC29 adds AI-driven approvals and more countries and languages

The controls around them matter as much as the agents. BC29 made these generally available:

  • A dedicated task pane that shows what every agent is working on.
  • Review on the page, so you can check agent-generated content where it sits before it's used.
  • Review notifications on lists, so records waiting for a human are easy to spot.
  • Simpler agent permissions, so an agent can be limited to the data and actions its job needs.

The pattern is human-in-the-loop. Agents prepare the work and people approve it. That is the right starting point for financial data, and it is how I would introduce agents to any client.

On cost, Copilot's assistive features come with Business Central. The task agents are charged on consumption (Copilot Credits) rather than included in the licence. Check Microsoft's current licensing before you estimate a business case, because the pricing details are still changing. (We worked through some numbers in the real cost of AI agents.)

The MCP server: opening Business Central to any agent

The Business Central MCP server lets AI agents built outside BC read and act on your data through a standard, secured connection. It has been generally available since April 2026.

MCP (Model Context Protocol) is an open standard that defines how AI agents discover and use tools. Before it, every AI integration needed its own custom connector. With MCP, an agent connects to BC's endpoint, sees which actions and data it is allowed to use, and works with them, much as a person uses the menus their permission set allows.

What Microsoft has shipped:

  • A dedicated endpoint (mcp.businesscentral.dynamics.com) using the latest MCP specification and OAuth 2.1.
  • Pre-authorised access from Copilot Studio and Visual Studio Code, plus third-party MCP clients registered in Microsoft Entra ID.
  • Configurations you control: you choose which API pages are exposed, and static validation catches mistakes before runtime.
  • Auditability: MCP calls are logged with success or failure, and configuration changes are audited through Microsoft Purview.
  • Large datasets: structured data can be passed to code-execution tools as file references.
  • Data queries (new in BC29): you can define, validate and run custom data queries through MCP tools.

This is the change I find most significant. Microsoft's own agents cover common scenarios. MCP lets you build agents for your own: an agent in Copilot Studio that chases overdue customers, a tool that answers "what's our stock exposure on this range?" from Teams, or an assistant such as Claude working through a month-end checklist against live data. Because the security model is BC's own permissions, it doesn't open a new hole in your system. (See permissions in Business Central.)

What it means for AL developers

AI agents are now a supported part of the AL development toolchain. BC29 includes a set of generally available features that let coding agents work with your extensions directly.

  • AL language intelligence for AI agents and other editors: agents get the same understanding of symbols, objects and dependencies that the AL extension gives VS Code.
  • AL MCP server tooling: workspaces configured dynamically and file logging for diagnosing agent activity.
  • Object ID allocation by agents, which removes a small but common cause of merge conflicts.
  • Debugging recorded failures with an AI agent: give an agent a recorded failing session and it works through it with you.
  • Profiling slow sessions with AI agents, so performance problems are analysed from real traces rather than guesswork.

In practice, the routine parts of AL work get quicker: scaffolding a table extension, writing an API page, tracing an event subscriber chain or reading an unfamiliar ISV codebase. The judgement doesn't change. Someone still has to decide whether a customisation should exist at all, where it belongs, and how it will survive the next upgrade.

For NAV upgrade work, this helps with the slow part: understanding years of C/AL modifications and deciding what becomes an extension, what returns to standard and what is dropped. An agent can map that estate quickly. An experienced consultant still has to decide what to do with it. (See upgrading from NAV: the code side.)

Getting your Business Central ready for agents

Agents perform only as well as the system they work in. Most of the preparation is ordinary good ERP practice that now pays back twice.

  1. Clean master data. An agent matching invoices to purchase orders can't fix duplicate vendors, inconsistent item numbers or wrong unit-of-measure setup. It will either fail or, worse, match confidently to the wrong record.
  2. Clear processes. If your AP process exists only in someone's head, an agent can't follow it. Write down the rules: tolerances, who approves what, and how exceptions are handled.
  3. Tight permissions. Give each agent its own narrow permission set, as you would a new starter. Start read-heavy, add write access one step at a time, and keep posting behind human approval until you trust the results.
  4. Stay current. Agents and MCP features arrive in monthly updates on the SaaS platform. A heavily customised or on-premises system that is several versions behind won't get them.
  5. Governance from day one. Decide who owns each agent, who reviews what it does, how you'll measure its accuracy, and what Copilot Credit spend is acceptable. Use the audit trail that BC and Purview provide.

This is where NAV customers need to plan carefully. Moving a NAV database to BC unchanged, with its old customisations and messy data, gives you a cloud system that agents can't use well. An upgrade is the best opportunity you'll get to bring processes back towards standard and clean up the data. Treat it as preparation for agents as well as a technical migration, and you'll get the benefit for years.

Rescue projects are similar. When I'm brought in to recover a struggling implementation, the problems are nearly always data, setup and process. Those are the same things that decide whether agents will help or just automate the mess.

Where it's heading

AI in Business Central will no longer arrive in two scheduled waves a year. BC29 is the last release announced under the release-wave model. From September 2026, Microsoft publishes new capabilities continuously on its AI at Work roadmap, and the old release planner closes on 15 November 2026.

That shows how quickly Microsoft expects this area to move. Based on what has shipped and the direction of the platform, these are the developments I expect over the next 12 to 24 months. They are my views, not Microsoft commitments.

  • More first-party agents. The natural next areas are inventory replenishment, credit control and collections, and parts of the period-end close. Each is rules-heavy and repetitive, with clear exceptions for people to handle.
  • Custom agents as a normal deliverable. Between Copilot Studio and MCP, building a client-specific agent will become as routine as building a report or an extension. Expect agents to appear in project scopes and AppSource offerings.
  • Agents working with other agents. A sales agent passes a confirmed order to a fulfilment process, which raises a purchase requirement for the payables side to expect. Coordination across BC, Outlook, Teams and Power Platform is where the larger efficiency gains are.
  • More autonomy, earned gradually. Today agents propose and people approve. As accuracy is proven and the controls mature, low-risk, high-volume actions will move to approval by exception.
  • Governance as its own workstream. Agent ownership, permission design, audit, credit budgets and accuracy monitoring will become a standard part of implementations, and something auditors ask about.

What won't change is the need for people who understand both the technology and how the business actually runs. Agents remove the repetitive work. Someone still has to design the processes they follow.

Where to start

Pick one bounded, high-volume process, prepare the data and permissions behind it, and run an agent with a person approving every action until the results earn more trust.

Purchase invoices are usually the best first candidate: high volume, clear rules and a measurable error rate. Sales order intake is a close second if your customers order by email. (See what the Payables Agent actually does.)

If you're on NAV or an older BC version and wondering how agents could fit your business, or you have a BC system that isn't delivering what it should, I'm happy to talk it through. At BBXD I work on Business Central implementations, NAV-to-BC upgrades, rescues, data migration, AL development and integrations, and getting systems ready for what comes next is part of that work. Book a 30-minute call.

Sources

  • What's new or changed in Business Central 2026 release wave 2 (Update 29.0) – Microsoft Learn
  • Create agentic experiences with enhanced MCP server – Microsoft Learn release plan
  • Configure Business Central MCP Server – Microsoft Learn
  • Create agents in Copilot Studio that connect to Business Central – Microsoft Learn
  • What's new in Business Central 2026 release wave 2 – Tensoft
  • Business Central 2026 release wave 2 (BC29) feature guide – Aisling Dynamics
  • How Copilot agents are reshaping Business Central – Top Dynamics Partners
Email this post as a PDF
A branded PDF of this post, sent to your inbox to keep, print or share. Copy in colleagues if you like.
We only use these addresses to send this PDF. Nobody is added to a mailing list. Mike at Business Boxed receives a copy. See our privacy notice.
Email this post
Talk to us
Want this done in your Business Central?
Book a 30 minute callGet the monthly newsletter

Related posts