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

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...