Business Central Roadmap 2027: Version 29, the AI at Work Roadmap, and the New Automation Stack

Microsoft released Dynamics 365 Business Central version 29 on October 1, 2026. That one release changes how every Business Central roadmap 2027 plan should be written. Release plans are gone, replaced by the always-on AI at Work roadmap. Three built-in agents (Sales Order, Payables, and Expense) now run real work with a price tag per document. And the Business Central MCP server lets AI tools query ERP data directly.

This guide explains what changed, what it costs, where the built-in agents stop, and how an SMB finance or operations leader should sequence automation spending for 2027. Everything here is based on Microsoft's own documentation.

The Business Central roadmap 2027 is the set of features, update dates, and AI capabilities Microsoft has published or committed to for Dynamics 365 Business Central between now and the end of 2027. It starts from version 29, released on October 1, 2026, and runs through version 30 in spring 2027.

Three things make this year's roadmap different from any year before it:

• No more release plans. Microsoft stopped publishing the twice-yearly release plan documents in September 2026. New features now appear on the AI at Work roadmap, a live feed that changes month to month.
• Agents are real and priced. The Sales Order Agent and Payables Agent are generally available. The Expense Agent is a production-ready preview. Each one bills per use in Copilot Credits.
• AI can query the ERP directly. The Business Central MCP server is generally available for data queries. Any compliant AI client can read ERP data under a user's identity and permissions.

For an SMB finance or operations leader setting an automation budget for 2027, the questions change. The question is no longer "does Business Central have AI?" It is "which work do the built-in agents cover, what does each one cost per transaction, and where does cross-system automation still need its own layer?"

This guide answers those questions in plain language: version 29, the roadmap change, the built-in agents and their cost, the extension surface, and a practical 2027 plan.

Update 29.0 opened 2026 release wave 2 on October 1, 2026. New online customers get it automatically. Existing customers receive a notification and can schedule the update to any date inside the five-month period that ends in February 2027. On-premises deployments on version 24 or earlier must move to version 25 first.

The release notes on Microsoft Learn list roughly eighty items. The ones that matter for automation planning fall into four groups.

Copilot and agents

The Microsoft Copilot chat experience inside Business Central ships as a public preview. It replaces the older Chat with Copilot pane with the same Copilot surface the rest of a Microsoft 365 tenant uses.

Around it, Microsoft made several agent management features generally available:

• A dedicated task pane for every agent
• Review of agent-generated content directly on the page where it lands
• Simpler agent permissions
• Review notifications on lists
• An updated agent UI

The Payables Agent also gained improved purchase order matching, which is generally available.

Data access for AI

Running data queries through the MCP server is generally available. AI clients can now define, validate, and run custom queries against Business Central tables, including data that no existing API page exposes.

This is the single most important platform change in the release for anyone building AI agents around the ERP. It means an AI tool no longer has to wait for a developer to publish an API page before it can read a table.

Expense Agent

Microsoft added a cluster of preview capabilities to the Expense Agent: mileage calculation with date ranges and vehicle types, AI-driven approvals, VAT and withholding tax on expense reports, better duplicate prevention, and more countries and languages.

All of these carry the preview label. Treat them as not yet ready for a production rollout plan.

Documents, commerce, and reporting

EDI document exchange through E-Documents enters public preview. Shopify B2B companies, catalogs, pricing, exchanges, and refunds are generally available. Report outputs can now be automated, and multiple financial reports can run into a single PDF.

Two platform changes deserve a line in every integration review:

• SOAP web services on Microsoft UI pages are now disabled as a mandatory feature. Any middleware still calling page-based SOAP endpoints breaks on update.
• Table extension fields are now stored in the base table. This speeds up data loading but changes how custom indexes behave.

The table below groups the version 29 features that matter most for automation by their availability status.

For years, Business Central planning ran on a rhythm. A release plan arrived each January and July. Partners built roadmaps from it. Projects were slotted between waves. That rhythm ended in September 2026.

Microsoft now publishes new Dynamics 365, Power Platform, and Dataverse capabilities to the AI at Work roadmap, which is the renamed Microsoft 365 roadmap. Existing release plans stay online for historical reference. The Release Planner tool retires on November 15, 2026. The version 29 release notes already point to roadmap IDs instead of release plan pages.

The update cadence itself has not changed. Microsoft still ships two major updates a year, in April and October, each with a five-month update window. What changed is disclosure. Features now appear on the roadmap when Microsoft decides to share them, not in a fixed twice-yearly document. Expect version 30 (2027 release wave 1) in spring 2027, and read its scope from the roadmap rather than a plan.

How to read the roadmap for planning purposes

• Filter by product. Set the product filter to Dynamics 365 Business Central and save the URL. Every roadmap item has a numeric ID (for example, 573312 for MCP data queries). Cite that ID in internal documents.
• Read the status before the title. "In development" means Microsoft has committed to the idea, not a date. "Rolling out" means tenants are receiving it. "Launched" means it is done.
• Separate release type from status. An item can be Launched as a preview. Preview features are not production commitments, and Microsoft can change or remove them.
• Note the GA month, not the day. Roadmap entries state a calendar month, such as October CY2026. Build project plans around the update window, not the roadmap month.
• Review monthly. The roadmap changes all the time. A 30-minute monthly scan replaces the two-day release plan review most partners used to run.

A roadmap row tells you what, not why. Pair it with the Microsoft Learn "what's new" pages for implementation detail, and with your partner's upgrade assessment.

Microsoft describes the shift as moving Business Central from a system of record to an active participant in daily work. The vehicle is a set of built-in agents that run defined flows end to end, with a human reviewing before anything posts.

All three agents share the same model. Each one:

• Is set up as its own user with scoped permissions
• Watches an intake point (a Microsoft 365 mailbox or an upload)
• Works through a multi-step task
• Shows its output in the agent task pane for review

Supervisors can inspect every step, correct data, pause or resume the agent, and track KPIs such as documents created. Copilot and agents run on Business Central online only.

Sales Order Agent. Watches a designated mailbox for customer requests, identifies the customer, matches items, checks availability (optionally using capable-to-promise logic), and drafts a sales quote or order for review. It handles the front end of order-to-cash for email-driven B2B demand.

Payables Agent. Receives vendor invoices as PDF attachments in a mailbox, extracts header and line data, matches lines against history and, since version 29, against purchase orders, and prepares draft purchase invoices for review. It processes up to 500 invoices a day.

Expense Agent. Takes uploaded receipts, extracts and categorizes the data, itemizes lines, and groups them into expense reports for approval. It is a production-ready preview, aimed at employees who never otherwise log in to the ERP.

What the built-in agents cost

Copilot in Business Central is included in the license at no extra cost, on Business Central online. The task agents are different. Selected agent capabilities use consumption-based billing in Copilot Credits, purchased against an Azure subscription and set up per environment in the admin center. Microsoft publishes the meter:

• Sales Order Agent: 5 Copilot Credits per agent action (for example, creating or updating a quote) and 2 per generative answer. Microsoft's own example assumes 100 requests a month, half with a usable attachment, and comes to 1,650 credits.
• Payables Agent: 50 Copilot Credits per invoice processed plus 5 per invoice line. Microsoft's worked example, 100 three-line invoices a month, comes to 6,500 credits.
• Expense Agent: 50 Copilot Credits per receipt, regardless of line count.

At Microsoft's published pay-as-you-go rate (roughly one US cent per credit at the time of writing; confirm on the Copilot Studio pricing page), a mid-sized distributor running all three agents at modest volumes spends a low three-figure monthly amount. Cost scales with document volume, not with user seats.

An illustrative example. Picture a distributor that receives 300 vendor invoices a month, averaging four lines each, and 150 emailed customer orders. Using Microsoft's published meters, the Payables Agent would consume about 21,000 credits (300 x 50, plus 1,200 lines x 5) and the Sales Order Agent roughly 2,500 credits. At one cent per credit, that is about 235 US dollars a month before any margin for exceptions. This is a planning example built from Microsoft's meters, not a customer result, but it shows why budgeting by document count is the right method.

Where the built-in agents stop

Each agent runs one flow inside one system. That boundary matters:

• The Sales Order Agent reads email. It does not read an EDI feed, a marketplace, or a web store.
• The Payables Agent drafts an invoice. It does not reconcile the payment with the bank or update a 3PL.
• The Expense Agent builds a report. It does not push the approved amounts into a payroll or payment system.
• None of the three carries data to a CRM, an e-commerce platform, a warehouse system, or a second Business Central company without additional tooling.

Think about a typical B2B order. The Sales Order Agent drafts it from an email. From that point, the order still has to reach the warehouse for picking, the carrier for shipping, the web store for a status update, the CRM for the account record, and the customer for a confirmation. Five systems, one order, and the built-in agent touched only the first step.

That is the gap an orchestration layer fills. A workflow layer outside Business Central watches for events (a posted invoice, a new order, a stock change), reads and writes through the APIs, webhooks, and MCP server, checks and maps the data, retries when a system is down, and sends exceptions to a person for approval. Business Central stays the system of record. The orchestration layer owns the flow across everything the ERP cannot see.

How appse ai fits this picture

appse ai is the AI and automation orchestration layer, which has spent more than a decade integrating ERPs such as Business Central with e-commerce, CRM, and logistics systems. It is built for the second column in your manual-work map: the processes that cross two or more systems.

A few things it brings to a Business Central 2027 plan:

• Pre-built connectors. A catalog of 100+ connectors covers Business Central alongside Shopify, Salesforce, HubSpot, Amazon, 3PLs, and payment providers, so the cross-system flow does not start from a blank page.
• Workflow templates for order-to-cash and procure-to-pay. Ready-made Business Central templates pick up where the Sales Order Agent and Payables Agent hand off: sending the drafted order to the warehouse and web store, or carrying the approved purchase invoice through to payment and reconciliation.
• AI agents that work across systems. appse ai’s agent suite covers order-to-cash, procure-to-pay, finance, inventory, and sales. The agents reason over data from several systems at once, which is the part Business Central’s single-system agents are not designed to do.
• A builder the business team can change. The Autonomous Workflow Builder lets operations and finance staff adjust a flow without waiting for a partner AL build. That matters for the ownership question raised later in this post.
• Visibility and control. Every run is logged, exceptions route to a human, and nothing posts without the approval gates you define. The governance rules you write for Microsoft’s agents extend to the cross-system layer.

The practical split is simple. Use Microsoft’s built-in agents for intake that arrives by email and stays inside the ERP. Use appse ai for everything the order or invoice has to touch after that.

If you want to see what sits on the other side of the boundary, browse the appse ai Template Library for ready-made Business Central workflow templates that start where the built-in agents stop.

Business Central has four ways to let automation reach in or out. Version 29 upgrades one of them substantially.

APIs and webhooks. The standard API v2.0 endpoints and custom API pages remain the reliable way to read and write Business Central data from outside. Webhook subscriptions push change notifications, so an external system can react to a new order or a posted invoice without polling. Integration platforms and AI layers both use this surface.

The Business Central MCP server. Model Context Protocol (MCP) is an open standard that lets AI clients discover and call tools exposed by an application. Business Central's MCP server is hosted by Microsoft, authenticates through Microsoft Entra ID, and runs every operation under the connecting user's identity and permissions. The audit trail shows who did what. By default it gives read-only access to exposed API pages. Administrators enable write operations per API page. Version 29 adds data query tools: an MCP client can define, validate, and run custom queries against tables that have no API page at all. Supported clients include Visual Studio Code with GitHub Copilot, Copilot Studio, and any client that follows the MCP specification.

Power Platform. Power Automate remains the first stop for triggers, approvals, and simple hand-offs. Version 29 adds the ability to map new Dataverse fields from Business Central, which widens what Dataverse-centric scenarios can see. Copilot Studio can consume the Business Central MCP server, and Microsoft's Agent Designer (preview) lets partners and customers prototype custom agents inside the product.

An external AI or workflow layer. When a process spans Business Central plus a web store, a CRM, a bank feed, a 3PL, and email, the orchestration belongs outside any one of them. A workflow platform in this position uses the APIs, webhooks, and the MCP server to read and write. It applies data mapping and validation, handles retries and exceptions, and routes approvals back to people.

The practical read: inside the ERP, use the built-in agents and Power Automate. Across systems, use the API and MCP surface from an orchestration layer that owns the end-to-end flow. The table below compares the five layers.

Microsoft's 2025 Work Trend Index found that 81 percent of leaders expect AI agents to be moderately or extensively integrated into their company's AI strategy within 12 to 18 months, and 46 percent say they already use agents to fully automate workstreams or business processes. For an SMB on Business Central, the question is no longer whether to run agents, but in what order and with what controls.

A seven-step sequence for 2027

1. Book the version 29 update before February 2027. Test every integration that touched SOAP page endpoints, every extension that defines indexes on table extensions, and every Copilot feature your users rely on. Run it in a sandbox first.
2. Map manual work by system boundary. List the processes your team still keys by hand. Split them into two columns: inside Business Central only, or across two or more systems. The split decides the tool, and gives you a costing framework for each line.
3. Switch on one built-in agent where intake is email and the flow stays inside the ERP. For most distributors that is the Payables Agent. For order-heavy B2B teams it is the Sales Order Agent. Assign a supervisor, keep review on for the first ninety days, and track the task pane KPIs.
4. Budget Copilot Credits by volume, not by seat. Multiply monthly document counts by Microsoft's published meter (invoices x 50 plus lines x 5; receipts x 50) and add a margin for exceptions. Confirm the billing setup in the admin center before activation.
5. Choose the cross-system layer deliberately. Use Power Automate for approvals and simple triggers. For flows that cross systems, reshape data, and change often, evaluate a workflow platform against a partner AL build. Compare the approaches on cost, speed, maintenance, and AI capability before you commit.
6. Put governance in writing. Agent permissions, approval gates before posting, MCP write scope per API page, and audit log retention. Treat every preview feature as a trial with an exit.
7. Re-plan at version 30. Review the AI at Work roadmap monthly, and hold a formal re-plan when the spring 2027 update lands.

Two judgment calls worth making early

Decide whether Business Central is the long-term system. If the business is pressing against intercompany, volume, or process limits, automation can buy two to three years. But the stay-or-move comparison with Dynamics 365 Finance and Operations deserves a clear answer before you invest heavily in a Business Central-specific automation stack.

Decide who owns the automation layer. Partner-built AL logic is right for in-app rules. A platform is right when flows cross systems and the business, not the partner, needs to change them weekly. Mixing both without an owner is how automation debt builds up.

Common mistakes to avoid in 2027

• Planning around a preview feature. Preview capabilities can change or disappear. Build the plan on generally available features and treat previews as experiments.
• Budgeting agents by user count. Agents bill per document. A team of five that processes 2,000 invoices a month pays more than a team of fifty that processes 200.
• Skipping the SOAP check. Legacy integrations that call page-based SOAP endpoints stop working on version 29. Find them before the update finds you.
• Expecting a single agent to run order-to-cash. The Sales Order Agent drafts the order. Picking, shipping, invoicing, and syncing to the web store and CRM still need their own automation.
• Treating the roadmap like a release plan. The roadmap is a feed, not a contract. A monthly review habit beats a once-a-year project.

Version 29 settles three things for 2027. The built-in agents are real, priced, and limited to single-system flows. The MCP server and the APIs are the sanctioned way for AI to work with ERP data. And the roadmap is now a feed, not a document, so planning has to become a habit instead of an event.

The work for an SMB is sequencing: update, map, switch on one agent, budget by volume, then choose the layer that carries automation across the systems Business Central does not see. Do that in order and the 2027 plan writes itself.