Blog Post

Healthcare and Life Sciences Blog
2 MIN READ

What We Took Away from Build 2026 as Microsoft Field and Solution Engineers

michaelgoad's avatar
michaelgoad
Icon for Microsoft rankMicrosoft
Jun 10, 2026

I pulled together four Microsoft Solution Engineers for a candid conversation about Build 2026, and I want to be upfront about what this is. No keynote recap, no announcement list. Four people who work with healthcare and enterprise customers every day, talking about what caught our attention and why.

I was joined by Arlie Hartman, a former CISO and now Principal SE with deep expertise in Purview and security; Thor Draper Jr., Senior Security SE covering security and identity; and Adam Hallbeck, a Principle Power Platform Copilot SE. Between the four of us we cover a pretty wide slice of the Microsoft field.

What we actually talked about

Microsoft Scout was one of the first things we got into. It's still frontier private preview, but I've been using it and it's already changing how I work. I had it reach out to Arlie on my behalf to schedule time, monitor his response, and book the meeting when he replied. It worked. That shift from "AI you type at" to "AI that does things while you're doing other things" is real, and Scout is one of the clearest examples of it right now.

Agent 365 got a lot of our attention too, especially the identity piece. Thor made a point that stuck with me: organizations are spinning up agents faster than they can track them. One customer had 1,400 agents and no clear picture of what any of them had access to. Agent 365 gives you sponsors, owners, and governance controls that map to how IT teams already manage people and service accounts. The mental model isn't new, the application to agents is.

Adam talked through Work IQ APIs and where that's heading, including how much easier it's getting to give agents access to organizational knowledge without having to wire up every tool individually. Arlie covered the Purview SDK changes in Foundry, which are a big deal for regulated industries because it moves the security configuration responsibility off developers and back to governance teams where it belongs. Thor walked through M-Dash and what a real DevSecOps process looks like when agents are doing the reconnaissance and triage work.

We also talked about Microsoft's in-house model lineup and what it means as models start to get treated more like infrastructure than differentiators. Copilot routing the right prompt to the right model quietly does a lot of work that most users never see.

The takeaway from our side of the field

Build 2026 felt different from where I sit. A year ago we were talking about what agents could do. Now we're talking about how to govern the ones already running. The product is catching up to the conversations we've been having with customers, and that matters a lot in healthcare where "we'll figure out governance later" isn't an option.

Watch the full conversation above. I'd love to hear what questions it surfaces for your organization.

Published Jun 10, 2026
Version 1.0
No CommentsBe the first to comment