Michael S. Collier

Microsoft Build is always packed with big announcements, but my favorite part is bringing those ideas back home and figuring out what actually helps teams ship better software. On June 20th, we did exactly that at Microsoft Build \\localhost:columbus.

When you build Azure Functions apps with Aspire, the best experience is usually the one where the AppHost reflects intent instead of infrastructure plumbing.

That matters a lot with Durable Task Scheduler. In a local dev loop, I want an emulator. In Azure, I want the real resource. The recent Aspire integration makes that split much cleaner than the older manual approach.

Aspire 13.3 introduced support for Durable Task Scheduler as part of the Azure Functions integration.

I try to keep my Docker Desktop (on my personal dev machine) up-to-date. It updates frequently and I’m generally a fan of keeping my dev software on the latest version. So when I noticed an available update for Docker Desktop, I didn’t hesitate to update. That was a mistake - 4.75.0 broke my WSL integration.

Microsoft Build is a two-day event this year (after being three days in prior years). That’s in line with the overall smaller Build - fewer attendees, smaller venue, and fewer days. There was no day 2 keynote either. For me, day 2 was full of breakout sessions, a hands-on lab, and great conversations with Microsoft and GitHub employees.

I attended Microsoft Build in person on June 2, 2026. Below are my observations from day one. I’ll post a day-two update, as well as a wrap-up after the event.