Development Archives - medienstudio.net

Fixing the ‘No utility model is configured’ Error for Copilot BYOK in VS Code

When working with Bring Your Own Key (BYOK) models in Visual Studio Code’s GitHub Copilot chat, you might encounter a configuration error preventing the agent from completing your requests. This error typically presents itself as:

No utility model is configured for ‘copilot-utility-small’ while the selected main agent model is BYOK.

How to Use Azure Foundry Models with BYOK in VS Code

If you’re looking to leverage your own custom AI models within Visual Studio Code, using Azure AI Foundry models as your Bring Your Own Key (BYOK) provider is an excellent approach. Previously limited to the Insiders build, custom BYOK models are now officially supported in the stable release of VS Code. This allows you to integrate powerful, customized models directly into your development workflow via GitHub Copilot.

Implementing Barcode Scanning in Microsoft Teams Apps

If you are building a Microsoft Teams app and want to integrate barcode or QR code scanning, the setup process is quite straightforward. However, there is a crucial API caveat developers need to be aware of when choosing between the newer and legacy scanning functions.

While Microsoft has introduced newer API surfaces for this feature, these don’t seem ready for real-world application. Here is a pragmatic approach to ensure a reliable implementation in production.

How to leave an Azure DevOps Organization

One of those things that should be easier to find: simply go to https://aex.dev.azure.com/me and make sure you’re logged into the correct account.

On the left, confirm you have selected the correct tenant for the DevOps organization you’re trying to leave.

Sending Notifications in Microsoft Teams apps

For my Microsoft Teams apps I recently added support for Teams-native notifications. This allows me to conveniently send notifications through Microsoft Teams without having to manage some kind of push service myself.

These notifications can be sent through Microsoft Graph which I’m doing using the On-Behalf-Of-Flow, meaning this only works when a user with the required permissions is performing an action that will trigger a notification.

Here’s how I did it:

Streaming File Downloads from Azure Blob Storage through ASP.NET Core

Often times when working with Azure Blob Storage you don’t want to expose access to the service directly but rather have requests go through your own API. This allows you to control access and hide the underlying service. However, you need to be careful to not put unnecessary extra load on your service during file operations by buffering up- or downloads in memory. You may not notice this at first for smaller files like images, but I can severely impact your service performance when larger files are in play.

Azure SignalR Serverless with Azure Functions v4 Node

For my Microsoft Teams apps Zeitplan.io and Team Schedule, I recently implemented auto-updates of the calendars using SignalR to trigger the reload whenever a change was made. Since both apps run with Azure Functions on Node/TypeScript as the backend, I chose the Azure SignalR service in serverless mode. The functions are connected via Managed Identity to negotiate between the React frontend and the Azure SignalR service.

Testing Azure Functions v4 Node & TypeScript with Jest

To write and run tests for Azure Functions with Node / Typescript, we need a bit of extra setup. We’ll start with a new function project with an http trigger and then add the required dependencies:

npm install --save-dev jest typescript ts-jest @types/jest ts-node

I added ts-node as an additional dependency which is not listed in the ts-jest Getting started but required to run the tests.

Deploying to Azure Static Web Apps in Azure DevOps

I have started moving several static websites & SPAs from “Static website hosting in Azure Storage” to Azure Static Web Apps (SWA). Main reason for this is the limitation of using apex domains with Azure CDN which is the only way to use custom domains on websites hosted with Azure Storage. This is not an issue with Static Websites where you can use ALIAS, CNAME or A Records to map your domains. And with two custom domains available in the free tier this is now my go-to default.

Azure Functions + Storage with Managed Identity via Bicep

Today I needed to migrate an Azure Functions project that used to connect to Azure Storage with a normal connection string. Since that’s prohibited by policy in my new Azure subscription, we needed to change that.

This also meant we needed to move the Function App to a dedicated plan since Managed Identity is not supported with Consumption or Elastic Premium plans.