I did a thing .. again 
.
You know the drill. Microsoft drops the Business Central 2026 release wave 2 launch event. 38 videos. 7 hours and 9 minutes of “What’s new in ..”. And somewhere in there are the 12 minutes that actually matter to you.
Which 12 minutes? Well .. that’s the fun part. Nobody tells you.
And this wave, there are no per-feature release plans anymore either 
. There is a “feature details” page in the docs, and that’s about it. So if you want to know what was actually announced, what is preview, what is GA and what is “in the future, stay tuned” .. you watch. All of it ..
Yeah. No. 
Confession time: I hate videos
Don’t get me wrong .. the people in those videos do a great job. It’s not them. It’s the format.
I can read a page in a minute. I can search it. I can Ctrl+F my way to the one sentence I need. A video? A video makes me sit there. At its pace. And when I come back two weeks later because I vaguely remember someone saying something about interfaces .. which video was it? Where in the video? So I scroll. And scrub. And overshoot. And go back. And land in the middle of a sentence about something completely different. And scrub again.
Every. Single. Time. 
I don’t want to watch 35 minutes to find the 40 seconds I need. I want to search, click, and land on the exact second.
So this thing is basically me, being too lazy to scroll through videos, and spending way more effort on not having to do that.
So .. what did I do?
I let a bunch of agents watch the whole thing for me.
The result is here: https://waldo1001.github.io/msdyn365-2026-release-wave-2/
Let me be very clear about what this is: it is a way to navigate the videos. Not a replacement.
Not a summary you should trust blindly.
Not “the release notes”.
Think of it as a table of contents for 7 hours of video. An index. A map. Every single thing on the site exists to get you to the right video, at the right second, as fast as possible .. and then Microsoft’s own people tell you the story. Not me.
It is also unofficial. It is not a Microsoft thing, it is a waldo thing, which means: nobody asked for it, and it might be wrong in places (more on that below).
The map
The home page is one big zoomable wheel. The Business Central icon sits in the middle, the 10 functional areas go around it, and all the features sit on the outer ring.
The trick: size is airtime. Not importance, not story points .. just how long they talked about it. Click an area, it zooms in. Click a feature, you get a panel with a summary, the quotes, and little timestamp chips that jump to YouTube at that exact second.
That last bit is THE point. The summaries are just signposts. I don’t want you to trust my summary. I want you to click and hear them say it.
Same on every other page, by the way. Each video has a timeline strip you can click anywhere on. Each quote has a chip. Each search result has a chip. If there is no link to a second in a video, it doesn’t belong on the site.
Some numbers ()
Ok .. so .. the agents found 319 features in those 38 videos. A few things that made me smile:
- Developer tools got the most airtime: 89 minutes. We are loved after all
. - Expense Agent got 74 minutes, spread over 8 videos. EIGHT.
- The word “agent” was said 150 times. “Copilot” 89 times. “MCP” 56 times. I guess it’s mostly about AI
- The word “seamless” was said .. 0 times. Zero! I had it on my bingo card and everything. Honestly, respect. Is nothing seamless?
- The feature with the most airtime of the whole event is Transfer WIP item and WIP ledger entry in subcontracting. More than 15 minutes. And as far as my matching goes, it is nowhere in the docs . But that could be me doing a bad job..
“What they didn’t say”
This is my favorite page, and probably the one that gets me in trouble .
I took the features Microsoft documented (81 of them, from the feature details page, the update 29.0 overview and the AI at Work roadmap) and put them next to the features they showed. And then you get three piles:
- Documented and shown: 59. Nice.
- Documented but not shown: 22. So it’s in the docs, but nobody demoed it on the videos.
- Shown but not documented: 178. Hmm
Now, before you grab the pitchforks: that 178 is inflated. The docs have big, coarse entries. The videos have lots of small “oh and we also did this” moments. So a lot of those are sub-features of something that IS documented. I know this. Now you too.
And then there are the status conflicts: 46 cases where the video and the docs don’t tell the same story. Like the new Copilot chat: on stage it comes “to all our users with this release”, and the docs entry says public preview. Who is right? Honestly? I don’t know. That’s exactly why every one of them links to the second in the video AND to the docs entry. You decide.
One more honest thing: most presenters never say “this is GA” out loud. So the rule on the site is GA unless they said otherwise. Only 17 features were actually called GA on stage. The rest is GA “by launch event convention”. It’s marked, with a footnote. Don’t sue me.
The fun pages
- Bingo: a heatmap of who said which buzzword in which video, and a printable 5×5 card for the next event. You’re welcome.
- Airtime: who got the minutes. Copilot and agents: 25% of the footage.
- Digests: “the minutes that matter”, for developers, consultants, admins and decision makers. The developer oneis 108 minutes instead of 429. That’s a movie instead of a work day.
- Ask the event: search the transcripts. It feels like grep, not like a chatbot. On purpose. But the is a tip if you want to use your AI agent and point to this repo :-).
How (the short version)
Think about it .. this is 68,000 words of auto-generated YouTube captions. No human is going to structure that for fun. (Hi 
)
So: captions in, a pipeline of Claude calls to extract features and quotes per video, a merge step to make one feature graph, a matching step against the docs, and a static site on GitHub Pages. Every quote is validated against the transcript. If a quote isn’t literally in there, it gets dropped, not “fixed”.
58 LLM calls later: https://waldo1001.github.io/msdyn365-2026-release-wave-2/
And the repo (with an llms.txt) is built to be read by agents as well as by humans, so you can point your own AI at it and ask “what changed for AL developers?” and get answers with timestamps.
so .. is it correct?
Mostly. Probably. It is built on auto-captions, which think “AL query” is “EL query” and that we have “dependent species” in our apps (I wish). The features are extracted by an LLM. The merge is conservative, so some things show up twice under slightly different names.
So use it for what it is: a way to find your way around the videos. A map, not a contract. The videos (and the docs) are the source. This just gets you there without the scrolling.
If something matters to you: click the chip, listen to the 30 seconds, and check the docs.
If you find something that’s wrong .. you know where to find me .
Enjoy your weekend!