Blog

Introduction Azure API Management is a hybrid, multicloud management platform for APIs across all environments. For more information on API Management, check out Microsoft Docs: About API Management. API Management (APIM) is an Azure service that enables you to manage APIs as first-class assets throughout their lifecycle. It consists of an API Gateway, a management plane and a developer portal. All these components are hosted in Azure and are completely managed by default.

The Betatalks Discord A few months ago we’ve started a Betatalks Discord server to build a community and enable our friends to discuss all the Betatalks content we put out there. Think about the Betatalks videos on YouTube, Betatalks live events and the most recent addition: Betatalks the podcast. To notify the corresponding Discord channels about new Betatalks videos or Betatalks the podcast episodes, I created Azure Logic Apps to check for new additions and post them to the webhook.

Azure .NET 5 Functions A lot has been said about .NET 5 support for Azure Functions. The most important news: it is now officially supported! 🥳 To enable running Azure Functions with .NET 5, the new Isolated Model enables Functions to run as an out-of-process language worker separate from the Azure Functions runtime. This way you’ll have full control over the Function’s dependencies on one hand, and new features like a middleware pipeline on the other.

After my two previous posts Azure Static Web Apps: a first look and Azure Static Web Apps: quirks & gotchas, let’s have an updated look at ASWA in this post. Support for new languages 👩🏻‍💻 Announced at Microsoft Ignite this year, Blazor and C# APIs now supported in Azure Static Web Apps. This enables .NET developers to build and deploy full stack .NET applications with Static Web Apps. Blazor support Since ASWA is a static hosting option, which means we don’t have a server component*, the Blazor support for ASWA means support for Blazor WebAssembly.

It’s Serverless September! The one month a year in which we can keep talking about Serverless to our friends without feeling bad about it. So here goes … 🤓 In this post we’ll have a look at Power Automate. Because of the low code / no code nature of the service, it’s a great fit for citizen developers to automate (business) processes. And although I love to code, it’s good to also look at these other types of services that expand the Serverless universe.

After playing around with Azure Static Web Apps (ASWA) for some time I found some quirks and gotchas. Of course Static Web Apps are still in preview. Most of these are probably because of that fact. Despite that, it might still be interesting to know about them. That way if you run into any of them, you’ll at least know it’s not you … 😉 🏭 Creating an Azure Static Web App It all starts when you want to create an ASWA: searching for it in the list of resources in the Azure portal doesn’t show it.

Although the two have a lot in common, even including parts of the name, there are a few very clear differences between Static website hosting in Azure Storage and Static Web Apps. We’ll have a look at what those differences are and take a first look at the most recent of the two: Static Web Apps. Static website hosting in Azure Storage Static website hosting is a feature you can enable free of charge on a storage account.

This post is part of a series on hosting your Hugo website on Azure. Keep an eye on this website for future articles. Intro As you might have seen or read somewhere, I’ve migrated the previous version of my personal website, which was in WordPress, to the current one that is made in Hugo. One of the reasons for migrating away from WordPress was the fact that due to a vulnerability in one of the WordPress modules, spammers were able to use my account to send out a lot of mails.

Intro The possibilities for software development have changed tremendously over the past couple of years. Actually, it’s better to say that the number of options has increased tremendously. With the final breakthrough and continuous expansion of the cloud, the supply of different types for resources like compute and data store is larger than ever before. And while you can even find a decision tree for selecting the right type of compute to use in for instance Microsoft Azure, selecting the right type of data store to use for your application is no simple feat.

My post Using Triggers & Bindings in Azure Functions V2 drew quite some attention over the past months. But there is a lot more to say about them. Time for a small follow up 😁 Covered previously ⌚ In my previous post we covered relative simple things like writing to blob storage and putting messages on a Service Bus. But the bindings for Azure Functions are so much more powerful.

This post on using App Configuration using .NET Full Framework was based on a contribution by Steven Hack. My last post Azure App Configuration: an introduction received a lot of good feedback. And one of those pieces of feedback was a question if it’s also possible to use App Configuration if you’re using Full Framework. The short answer: yes, this is possible! For the slightly longer answer: keep reading 🤓

Azure App Configuration is a powerful way to manage and store application configuration on a central location. Integrating it into for instance ASP.NET (Core) is pretty straightforward. This post gives you an introduction to Azure App Configuration and a simple example of how to integrate it in ASP.NET Core. Creating an Azure App Configuration 🆕 Of course there are several ways to create a specific resource in the Azure Portal. One of the simplest is to go to the portal, open up App Configuration and click the Add button.