Copilot in Business Central and UNI4C Controller: what each one answers

Copilot in Business Central and UNI4C Controller are not alternatives. They do different work, and most companies that use one also use the other. Copilot helps a person who works inside a Business Central page. Controller answers a question that crosses tables, systems and companies, and it verifies each figure before you read it.

This page compares the two. Every statement about Copilot comes from Microsoft Learn, with the source and the date at the foot of the page. Microsoft moves feature states between release waves, so check the source before you make a decision from it.

What is Copilot in Business Central?

Copilot is the AI assistant that Microsoft builds into Business Central. It is included with your Business Central licence at no extra cost. Microsoft states that fair-use policies, quotas or pricing might be introduced later.

Copilot works in the page you have open. It drafts marketing text, it suggests sales lines, it helps with bank account reconciliation, it summarises records, and it fills fields. Business Central also includes agents that run without a person: the Sales Order Agent, the Payables Agent and the Expense Agent.

Check the state of each one before you plan around it. In the 2026 release wave 1 plan, Sales Order Agent and Payables Agent improvements reached general availability during the wave, while the Expense Agent entries were in public preview.

Three limits apply to all of it:

1. Copilot is exclusive to Business Central online. It is not available for on-premises or private cloud deployments.
2. Copilot is not available to customers who run ISV Embed apps, because of technical limitations.
3. Each Copilot capability defines its own supported regions and languages. Many features start in English.

Copilot inherits your data permissions. Microsoft states that it cannot read more data than you already have access to. For customers within the EU Data Boundary, Microsoft states that data does not move outside that boundary.

What is UNI4C Controller?

Controller is an assistant that reads your live business data and answers in plain language. It runs in the UNI4C portal, not inside a Business Central page.

Controller reads customer and vendor ledger entries, sales and purchase documents, items and value entries, and projects and posted time. It reads through your own connection, so Business Central decides what you can see. It also reaches other systems in the same conversation: Outlook, Uniconta, Microsoft Fabric and Application Insights.

In analysis mode, the platform checks each figure in the reply against the rows that the query returned. A figure with no row behind it does not reach you.

How do the two compare?

Where does Copilot do the work better?

Copilot is better wherever its output lands in a record that a person approves before it counts.

• Drafting inside a document. Marketing text, suggested sales lines and number series appear on the record in front of you. You read them before you save.
• Bank account reconciliation. Copilot proposes matches. You approve each one against the statement.
• Document handling by agents. The Sales Order Agent and the Payables Agent prepare transactions, and a person approves them.

One thing connects all three. A person sees the proposal in context and approves it, so the approval is the verification. A wrong suggestion costs a moment of attention and does not reach the ledger on its own.

If the work has that shape, use Copilot. It is in the licence you already pay for, and it is in the page where the work happens.

Where the same question applies to both

Copilot does not only propose into records. It also chats, and it assists analysis on lists. As soon as an AI writes a sentence that contains a figure, the approval step is gone, and one question applies to every product in this category including ours: did that number come from a row?

Microsoft documents that Copilot inherits your data permissions and cannot read more than you can. It does not document a figure-level check. Microsoft also states that the accuracy of these features might vary based on the apps that you installed.

That is a statement about what is documented, not an accusation. The point is that permission inheritance and figure verification are different mechanisms. The second one is the one that matters once the output is a sentence instead of a proposal, and it is the reason we built one.

Where does Controller do the work better?

Controller is better wherever the question crosses a boundary.

• Across tables. "Which customers are over their credit limit, and what did each one buy last quarter?" needs several tables and one answer.
• Across systems. A question that starts in the ledger and ends in a mailbox or in telemetry needs one assistant with several connectors.
• Across time. A report built from the query that answered the question refetches each time you open it, so the number is current.
• Where a wrong figure is expensive. Analysis mode verifies each figure against the rows that were read.

Can you use both?

Yes, and most customers do. The two do not conflict. They use different permission paths, and neither one blocks the other.

Split the work by what happens to the output, not by job title:

• Copilot for work that ends in an approval. Drafting on a document, reconciling a bank account, checking what an agent prepared.
• Controller for work that ends in a figure somebody acts on. A question across tables, a monthly report, a number that reaches a board pack, a bank or a customer.

The line is not finance against sales, and it is not junior against senior. It is whether a person approves the output in context before it counts. A consultant uses both, often in the same hour.

What is not true about either?

Some claims about both products appear often and are wrong.

"Copilot costs extra." It does not. Microsoft states that Copilot is included with the Business Central licence at no extra cost.

"The 30 minutes of Azure AI time is a Copilot limit." It is not. Microsoft states that this quota applies to non-Copilot features such as sales and inventory forecasting. Consumption of Azure AI time has no effect on Copilot in Business Central.

"Copilot in Business Central can see my Microsoft 365 data." It cannot. Microsoft states that there is currently no direct connection between Copilot in Business Central and Microsoft Copilot, and that Copilot features inside Business Central are unaware of your Microsoft 365 data.

"An AI assistant with your permissions cannot state a wrong figure." Permission control and figure verification are different problems. Permissions decide which rows a query can read. Verification decides whether the sentence you read contains a number that a query returned.

How do you decide?

Answer three questions about the work you want to improve.

1. Does a person approve the output before it counts? If yes, Copilot is enough, and the approval does the checking.
2. Does the answer have to cross tables, systems or time? If yes, you need an assistant that reads across them.
3. What does a wrong figure cost? If a wrong figure reaches a board pack, a bank or a customer, you need a system that checks each figure against the rows behind it.

There is one more test, and it is the only one that settles the argument. Ask both tools the same question about your own data, and then ask each one where the number came from.

What changed recently, and where to look next

Microsoft stopped publishing release plans in September 2026. New Dynamics 365, Power Platform and Dataverse capabilities now appear on the AI at Work roadmap. Existing release plans stay available for historical reference. If you track Business Central AI features, change your bookmark.