This is not a roadmap item. It is not a pilot program. At the opening keynote, Microsoft stated clearly that Business Central is ready for agentic engineering — meaning AI-assisted development is now a first-class part of how BC software gets built.
What that looks like in practice: AI agents can now build database queries on the fly inside BC rather than relying on pre-written queries. All Microsoft BC source code is in one public GitHub repository, completed after a multi-year project — giving the entire partner community real visibility into how the platform is built. Developer tooling has been extended so that practitioners can work flexibly, and stay productive, without being tied to a single environment.
Microsoft is moving fast on the tooling layer and carefully on the application layer. Those are not contradictions. The tooling can iterate quickly because that is where experimentation is safe. The application moves carefully because customer data and accounting integrity demand it. Both are deliberate, and both are the right call.
A year ago, "Copilot-free session" got applause at events like this one. Practitioners were skeptical, and rightly so. The tooling was immature, the quality story was incomplete, and the hype significantly outpaced the reality.
BC TechDays 2026 felt different. When Microsoft made its agentic development announcement, the room leaned in. Not cautiously. Not politely. It leaned in.
The conversations happening in the hallways reflected the same shift. Practitioners were not debating whether to use AI. They were asking how to make it production-grade — how to build test coverage that can hold a system together when an agent is writing code, how to set up governance that lets teams move quickly without breaking client environments, how to explain the velocity gain to a client in terms they trust.
Those are serious, specific, hard questions. They are not the questions of a community still debating the premise. The debate is over.
One of the most important signals from this week came from a session on testing, according to Jeremy Vyska, MVP. The phrase that will stay with us: "Tests are the system."
During a Microsoft session traditional development and testing was discussed. In traditional development, tests are a layer you add around the system after the fact. In agentic development, that model breaks down. If an AI agent is generating code, it will generate code that passes tests written after the fact — because it has seen enough code to do that. The tests become the specification. They are what you are telling the agent to build toward.
The BCQuality initiative — which BrightCom is part of — is built on this thinking. Quality is not a review step at the end. It is built into the workflow from the start, through GitHub, AL-Go, and structured agent pipelines. This is where the difference between a working prototype and a production-grade system actually lives.
Among the specific announcements from the conference, one deserves more attention than it has received outside the developer community.
Microsoft confirmed that companion tables are going away. Table extensions will merge onto the main table in SQL. AL keys will span both the main table and its extensions. Read and write operations will be faster.
For anyone who has built in Business central for more than a year, this is significant. Companion tables have been a source of architectural complexity — extra joins, performance considerations, and a recurring explanation to every developer new to the codebase. That complexity is being removed.
It is also part of a broader signal from Microsoft: the platform is getting cleaner, not more complicated. That is the right direction for partners who are building on it for the long term, and for clients who want implementations that are maintainable years from now.
This will enable us to improve performance for BrightCom’s customers in a way that was previously not possible.
This one is harder to put a number on, but it was one of the clearest signals from the week.
Practitioners who had invested in training and preparation earlier in 2026 showed up at BC TechDays measurably ahead of where the rest of the room was. They could follow the technical sessions without needing to fill in gaps. They had already started working through the questions that others were encountering for the first time. Multiple people said some version of this independently, without prompting.
The window to build an early lead in agentic business central development is still open. It is not as wide as it was twelve months ago. The community has moved, and the practitioners who are not yet investing in this capability will find the gap harder to close as the year goes on.
BC TechDays 2026 was not a conference about what is coming. It was a conference about what is here. The platform is ready. The tooling is real. The community has accepted the direction.
The work that remains — building production-grade agentic systems, establishing quality frameworks, developing the in-house knowledge to use these tools reliably — is not something that happens automatically. It requires deliberate investment.
BrightCom has been building in this direction for a while. If you want to understand what that looks like in practice, or where to start, get in touch!