Skip to main content

Supercharging On-Device AI: Foundry Local + Semantic Kernel

So far my ‘go to’ approach for using language models locally was through Ollama and Semantic Kernel. With the announcement of Foundry Local at Build, I decided to try to combine AI Foundry Local with Semantic Kernel.


Time to dive in…

What Is Foundry Local?

Foundry Local is Microsoft’s local execution runtime for large language models. Unlike cloud-hosted models, Foundry Local runs entirely on your device, giving you privacy, customization, and cost-efficiency. Thanks to its simple CLI and REST API, it integrates smoothly into existing workflows and can support a variety of models and use cases.

The easiest way to get started with Foundry Local is through winget:

winget install Microsoft.FoundryLocal

Once Local Foundry is installed, you can request the list of available models:

foundry model list

Download the model you want to use:

foundry model download phi-3.5-mini

Now you can run foundry using the downloaded model:

foundry model run phi-3.5-mini

If you forgot, the models you already have in cache, you can check this using following command:

foundry cache list

Once the model is running, you can start asking questions:

Use your Foundry Local model in Semantic Kernel

Start by running Foundry Local in service mode:

foundry service start

This will expose an OpenAI API compatible endpoint on http://localhost:5273. We’ll use this endpoint in our application.

Create a new console application and add a reference to Microsoft.SemanticKernel.Connectors.OpenAI:

dotnet package add Microsoft.SemanticKernel.Connectors.OpenAI

Next thing you need to do is to configure the OpenAI connector to use the local model:

Remark: Notice that we add a v1 to the URL and use the model id

The remaining part of you Semantic Kernel code should remain the same:

Let’s run the app to verify that it works:

 

More information

Get started with Foundry Local | Microsoft Learn

microsoft/Foundry-Local

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...