ITratorsBusiness Central Briefing / Episode 01
The Dynamic Shift in Business Central
Roadmap changes, AI agents, and integration deadlines—with a bonus song version.
Spoken version uses the supplied script. Bonus track: Legacy Protocol Sunset.
Audio could not be played. Try downloading the episode.
Bonus track
Legacy Protocol Sunset
The song version.
Transcript
Intro: The Dynamic Shift in Business Central
Welcome back to the pod, everyone! If you’ve been living in Business Central land lately, you know things are moving at breakneck speed. Today, we’re diving into the absolute latest roadmap updates, changes, and shift-in-thinking coming down the pipeline from Microsoft. And honestly... some of these changes are massive.
Yeah, absolutely, Alex. And let’s start right out of the gate with the biggest administrative shake-up: Microsoft is officially retiring traditional, static release plans in favor of the continuous, always-on AI at Work roadmap.
Wait, say that again for the people in the back—static release plans are gone? No more waiting for those massive, twice-a-year wave drops?
Well, the core six-month release rhythm is still ticking, but the way they disclose and push features has completely changed. Continuous publishing means capability updates drop as soon as they're ready. It keeps us on our toes, that's for sure.
AI, Copilot, and the New Era of Agents
Alright, let's talk about the fun stuff—AI and Copilot. We’ve moved past the phase where it's just a neat little chatbot sidebar. What are we seeing now, Emma?
Agents, Alex. Autonomous agents. We're talking advanced Sales and Payables Agents that don't just suggest text—they actively parse business documents, handle incoming B2B order automation across channels like email and Shopify, and streamline line-matching for accounts payable.
Okay, as someone who has stared at mismatched invoice lines until my eyes crossed, that's a game-changer. But what about for us developers and architects listening in?
Oh, they didn't forget us. Model Context Protocol (MCP) Server Integration is fully here. This is massive—you can now configure Business Central as an MCP server, giving external AI clients and custom agents direct, secure tool access to your API pages. The custom automation doors this blows wide open are wild.
The SOAP Deadline and Developer Realities
Speaking of developer updates—we have to talk about the elephant in the room. The SOAP retirement deadline is hitting hard.
Oh, absolutely. If you've been putting off migrating your legacy integrations, time's up. SOAP web service endpoints for UI pages are permanently dropped in version 29. Everything needs to be on OData v4 REST APIs.
That's going to wake a few IT departments up from a dead sleep. If you've got an old EDI feed or custom reporting tool still clinging to SOAP, it’s going to go dark.
Exactly. On the bright side, though, AL development tooling is getting some sweet quality-of-life bumps—like better support for mocking outbound HttpClient calls during testing, which makes writing robust unit tests infinitely less painful.
Wrap-Up & Action Items
Well, there you have it. The roadmap is moving faster, the AI is agentic, and technical debt like SOAP is finally getting purged. As always, get into your sandbox environments early, audit those integrations, and keep your eyes peeled on that rolling AI at Work roadmap.
Thanks for tuning in, everyone—catch you on the next episode!
Beyond the song
What this means in practice
Additional editorial discussion, checked on 24 September 2026. These notes expand the episode themes; they are not spoken in the audio or a transcription of the song.
The roadmap changes discovery, not your release calendar
Microsoft’s move to continuous roadmap publication changes when teams hear about planned capabilities. It does not mean every announcement is immediately available in a customer’s production environment, or that the established release cadence has disappeared.
For a consultant, the useful question is whether an announcement changes a design decision already being made. For a key user, it is whether the feature changes the process, permissions or testing needed. A warehouse team does not need another feature list; it needs to know whether next month’s rollout should be handled differently.
Agents need a clear boundary between preparing and committing
Consider an invoice that resembles a purchase order but contains a disputed charge. Matching the document is useful work. Deciding whether the charge is acceptable belongs to a different responsibility. Our recommendation is to test the exception path as carefully as the successful match: who notices the discrepancy, who can resolve it, and what happens if nobody responds?
The same principle applies to incoming orders. A convincing demonstration with one clean order does not establish how a customer’s unusual units, missing references or duplicate messages will be handled. Those are example acceptance scenarios, not claims that every agent supports every channel or exception today.
MCP: choose the operations, not just the connection
Business Central online’s MCP configuration can expose API operations to AI clients. Microsoft documents read-only access by default; enabling changes requires configuration of permitted operations. Creating or modifying a record and invoking a bound action are distinct capabilities.
A useful first scenario might be investigating an order discrepancy. Start by deciding what information the assistant should read. If it should also change the order, decide which changes are appropriate and how the user reviews the result. Successful authentication alone is not an acceptance test for the business process.
The SOAP deadline needs a more precise explanation
The supplied spoken script uses broad language here. The documented BC29 removal concerns exposing Microsoft-published UI pages as SOAP endpoints. It does not establish that every SOAP endpoint or every existing EDI integration disappears in BC29. Microsoft also documents removal of Microsoft-published page OData exposure in BC30, so simply changing the protocol on the same Microsoft UI page is not a durable migration strategy.
Inventory the actual endpoint, its owning app and its consumers before choosing a replacement. Compare standard or dedicated APIs against the fields and behavior the integration needs. Test a complete business exchange, including failures and retries—not just a successful request. A copied page in an extension is a documented alternative, but brings maintenance ownership; it should be a deliberate decision.
Sources & context
This version uses a user-supplied script and song. The transcript covers the spoken version; it is not a transcription of the song.
Microsoft: roadmap announcement