Pavan Davuluri

And Microsoft Foundry and Windows gives you the ability to bring your own models and run them on the edge.

It allows you to run open source models on the edge.

And in Windows, we also carry inbox models, surface as APIs.

And you can simply use those APIs powered by the Windows models in case you're not in a place to be able to bring your own models or use open source models.

Great question.

Actually, that's a scenario that we're exploring with the Copilot team right now in terms of how we can connect dots between the Copilot experience in the cloud and what your file system could look like in Windows.

Primarily, that is a cloud experience.

But one of the new innovations we have that we're actually sharing at Ignite is this notion of agent connectors in Windows.

So agent connectors in Windows are going to be backed by an on-device registry from the Windows team.

And in that specific example, in fact, we're going to have a File Explorer connector on Windows.

Awesome.

So yeah, that was a great question.

So your model in the cloud can ask Windows for access to your file system.

And in the case of Copilot Plus devices, you can also ask for semantic access to the system.

And so it's not just looking for names and files and folders.

The model can actually ask a query to the agent connector locally on Windows for, find me a file with a red barn door, and we will retrieve a semantic result.

Absolutely.

I think photos for consumers, Microsoft Office documents for commercial customers are all great examples of why the file system in Windows is something that people are familiar with, that they trust, they want to be able to unlock in their experiences.

And so

That was the primary motivation for starting with the File Explorer connector, in fact.