# Beyond the song

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

- [Microsoft: roadmap announcement](https://www.microsoft.com/en-us/dynamics-365/blog/business-leader/2026/08/25/one-always-on-roadmap-dynamics-365-power-platform-and-dataverse-join-the-ai-at-work-roadmap/)
- [Microsoft Learn: MCP configuration](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/ai/configure-mcp-server)
- [Microsoft Learn: platform deprecations](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/deprecated-features-platform)