All articles

Business Central

The Business Central and Microsoft 365 Copilot Bundle: What the Licence Settles, and What It Does Not

At Directions EMEA 2026, Microsoft announced a bundle of Business Central and Microsoft 365 Copilot Business. The licence decides who may use Copilot. It does not prepare your processes, your data or your extensions, and the coming Edit with Copilot turns custom fields and permissions into part of the AI's surface.

On a pale grey studio floor, two dark navy glass cubes bound by a glowing teal band like one package, next to a stacked structure of navy glass modules of different shapes, some joints glowing teal and one module glowing amber where it does not quite align.

The Business Central and Microsoft 365 Copilot Bundle: What the Licence Settles, and What It Does Not

At Directions EMEA 2026, the Business Central partner conference held in Paris at the end of October, Microsoft announced a bundle of Business Central and Microsoft 365 Copilot Business, on sale from 1 January 2027. The licence settles one question: who in the company may use Copilot. It does not prepare the processes, the data or the custom code Copilot will work on. And the Edit with Copilot capability Microsoft announced alongside it means your extensions, their fields and their permissions become part of what the AI reads and acts on.

What exactly did Microsoft announce?

The terms below are announcements, to be confirmed in Microsoft’s price list:

  • On sale from 1 January 2027, with the price list previewed in December 2026.
  • Business Central Essentials with Copilot at $95 per user per month, and Business Central Premium with Copilot at $125 per user per month.
  • Included in the user licence: Copilot Chat in Business Central and the coming “Edit with Copilot”, which lets Copilot change data rather than only read it.
  • Billed in Copilot Credits, outside the licence: agents, Cowork and future skill calls.

Microsoft Learn already documents Microsoft 365 Copilot Business on its own: an add-on for organisations with up to 300 users on eligible Microsoft 365 Business plans, with an annual commitment, capped at 300 licensed users per tenant. Larger organisations are pointed to the enterprise Copilot plans. Whether the bundle carries the same cap is a point to check in the price list, and it matters for a group whose companies share one tenant.

What does the bundle include, and what still costs extra?

The split follows a line Microsoft Learn already draws. Copilot features inside Business Central pages are included with the licence, with the caveat that fair-use policies or quotas may come later. Microsoft Copilot in Business Central, the conversational experience, needs an account eligible for Copilot Chat, and a Microsoft Copilot licence adds work data from emails, files and meetings. Learn is explicit that this licence does not give access to more Business Central data: what Copilot can read stays governed by Business Central permissions.

Agents are a separate budget. The Payables Agent, the Sales Order Agent and the Expense Agent bill per document in Copilot Credits, bundle or not. We worked through those rates, and what they mean for a group, in our article on the real cost of Business Central agents.

So the bundle simplifies the per-user line. It does not cap the AI bill, because the part that grows with volume sits outside it.

What changes when Copilot can edit Business Central?

Today, Microsoft Learn describes Microsoft Copilot in Business Central as a production-ready preview with read-only access to Business Central data: it retrieves, summarises and explains, but cannot create, modify or delete records.

Edit with Copilot, announced at Directions EMEA 2026, is the step from reading to acting, and Microsoft presented it as working on partner extensions too. That follows from what Learn already documents: Copilot works on the signed-in user’s behalf, within that user’s Business Central permissions, and it already reads the pages, tables and fields that extensions add. Once it can edit, it can act on whatever that user can change, standard or custom.

Microsoft’s own responsible AI documentation for Copilot in Business Central anticipates that step. It asks administrators to re-evaluate controls, permissions and confirmation mechanisms before enabling capabilities that create, modify or delete data. A group should treat the switch to Edit with Copilot as a governance change, not as a feature toggle.

Why do your extensions become part of the AI’s surface?

Because Copilot reads them like a user does. Microsoft Learn states that all extensions installed in an environment can influence the output of Copilot and agents, and that Copilot Chat can query the pages and tables your extensions add without any action from you.

Learn also lists what Copilot cannot use. Copilot Chat does not support fields without a tooltip, or fields whose AllowInCustomizations property is set to false. And it tells developers what improves the result: captions, tooltips and teaching tips that are concise and unambiguous, alternate search terms for pages, role-tailored pages, and permissions that give users, Copilot and agents only the data they need.

Agents work the same way. Learn’s description of the Payables Agent says it uses captions, tooltips and other UI metadata to decide each step, and can discover and use custom fields and actions.

In practice, three things in your custom code now carry weight they never had before:

  • Permission sets. An over-broad permission set was a risk for one user. With an assistant acting on that user’s behalf, it is the scope of what the AI can touch.
  • Captions and tooltips on custom fields. A field called “Status 2” with no tooltip is ambiguous for a person and invisible or misleading for Copilot.
  • Fields hidden from customization. Whatever is excluded through AllowInCustomizations is also out of Copilot Chat’s reach, which may be what you want, or not.

What should a group with custom code prepare before 2027?

  1. List the extensions per company. In a group, companies often run different sets of apps. Copilot will behave differently in each, and Microsoft’s application card recommends testing against representative scenarios for exactly that reason.
  2. Review permission sets with AI in mind. Start with the users who will get the bundle first. What they can see is what Copilot can see; once Edit with Copilot arrives, what they can change is what Copilot can change.
  3. Fix captions and tooltips on custom fields. It is unglamorous work, done in AL, and it is the cheapest way to make Copilot useful on your own processes. Since the 2024 release wave 1, a tooltip can be defined once on the table field and every page that shows the field inherits it, and the CodeCop rule AA0234 flags table fields without one. Turning that rule on in the build is the quickest way to find the gaps.
  4. Decide which fields stay out of reach. Use the documented mechanisms deliberately rather than by accident.
  5. Budget agents separately. The licence line and the credit line are two budgets, owned by different people.

The question of which AI option fits which task does not go away with a bundle either. We cover that grid in our article on Copilot alternatives for Business Central.

Is the bundle the right licence for a group?

It depends on three things the price list will settle. The user cap, if the 300-user limit of Copilot Business applies. The mix of users, since not everyone who needs Business Central needs Microsoft 365 Copilot. And the terms for groups with several tenants or several Business Central environments. We do not comment on the price itself until Microsoft publishes the grid.

What does not depend on the price list is the preparation. A group that buys the bundle without reviewing its extensions gets a licence on top of the same ambiguities, now read by an assistant.

The Asio Services way

We look at Copilot readiness from the code up: permission sets, captions, tooltips and the custom pages Copilot will read, company by company. It is the same discipline we apply to any Business Central development work, with one more reader in mind. If your group runs custom extensions on Business Central and is weighing the bundle for 2027, start with a clarity session.

FAQ

When can you buy Business Central with Microsoft 365 Copilot Business?

Microsoft announced at Directions EMEA 2026 that the bundle goes on sale on 1 January 2027, with the price list previewed in December 2026. The announced prices are $95 per user per month with Essentials and $125 with Premium.

Are Business Central agents included in the bundle?

No, according to Microsoft’s announcements. Copilot Chat and the coming Edit with Copilot are included; agents, Cowork and future skill calls are billed in Copilot Credits. Microsoft Learn documents the agents’ credit rates separately.

Can Copilot change data in Business Central today?

Not in the experience Microsoft Learn documents for Microsoft Copilot in Business Central, which has read-only access. Edit with Copilot, announced at Directions EMEA 2026, is the step that lets Copilot act, and Microsoft presented it as working on partner extensions too.

Does Copilot see fields added by our extensions?

Yes, in most cases. Learn states that Copilot Chat can query pages and tables added by extensions without extra work. It does not support fields without a tooltip or fields with AllowInCustomizations set to false.

Is Microsoft 365 Copilot Business limited in number of users?

Microsoft Learn documents Microsoft 365 Copilot Business as an add-on for organisations with up to 300 users, capped at 300 licensed users per tenant. Whether the Business Central bundle carries the same limit is to be confirmed in Microsoft’s price list.

Is your Business Central the problem, or the symptom?

We audit what you actually run, name what is worth keeping, and kill the rest. One conversation is usually enough to tell which one you are dealing with.

Start with clarity