Skip to main content

Getting started with the Azure AI services

Azure has a lot to offer if you want start building AI enabled solutions. But where do you start? There is just so much to learn and explore that it is easy to get lost in all the services, documentation and information out there. That's where the Book of AI comes in. This comprehensive guide is designed to help you navigate the world of AI services in Azure, providing you with the resources, tutorials, and sample code you need to build innovative solutions using Azure AI services.

Why use the Book of AI?

The website itself gives the following arguments:

I can only agree with that. Use the book of AI to try out not only the different Azure AI services but also the different SDK’s and client libraries. Not a C# developer?  No problem! All examples are available in multiple programming languages.

 

Eat your own AI

But for me the greatest feature of the Book of AI is not the content itself but the way it has been created. Instead of manually writing the complete website, it was completely generated by combining the power of OpenAI's GPT-4o model with the Azure AI CLI.

They first created a context aware OpenAI assistant that contained all the source code:

github clone https://github.com/Azure/azure-ai-cli
ai chat assistant create --name MyCliAssistant --files "\*\*/*.cs"

Then they used the Azure AI CLI to execute different prompts. Check out the dev folder inside the Github repo to find the different prompts used to generate the website.

ai chat --built-in-functions --user-prompt @PROMPT1

Here is an example:

 

 Impressive!

More information

BOOK of AI

Unlock Azure AI with the Book of AI: A Developer's Journey by Rob Chambers

Labels:

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...
Read more

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.
Read more

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...
Read more