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.
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. For an awesome write-up about everything around this, check out Oscar van Tol’s post Azure Functions in .NET 5 and beyond.
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.
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.
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 … 😉
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.
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 😁
Here’s a short post I didn’t want to hold from you. As you may already know I wrote a blogpost on Using Triggers & Bindings in Azure Functions. It handles quite a few nice possibilities of using triggers and bindings in Azure Functions (if I may say so myself… 😳). Fortunately, you learn something new every day. So I learned about Property Binding recently…
This post is part of a series on Managed Identity. For an introduction, see Managed Identity – Part I. For a post that shows you how to connect your application to different types of Azure resources using Managed Identity see Managed Identity – Part II. Stay tuned for future posts.
Next week my colleague Daniël te Winkel and I will do a session at Techorama 2019 titled Getting sh*t done with Azure Functions (on AKS!). Or GSDwAF for short 🤓
We will talk about running Azure Functions in a Kubernetes deployment using Managed Identities and implementing Dependency Injection. And, even better, we’ll show you how!
This post is part of a series on Managed Identity. For an introduction, see Managed Identity – Part I. Stay tuned for future posts.
Elaborating on Part I, this blog post will show you how to connect your application to different types of Azure resources using Managed Identity.
This post is part of a series on Managed Identity. Stay tuned for future posts.
Connecting your application to a resource like Storage or a SQL database used to involve a connection string. This isn’t very secure. These settings are available through the Azure portal. So they might get compromised.
With the introduction of Azure Key Vault, we got a way of separating these secrets from our application configuration. We can store them in a safe, secure place. There’s only one downside: you need a connection string to connect to Key Vault. So the problem isn’t solved; we only moved it. We can still get to the connection string the application uses to get secrets from Key Vault. So anyone with access to that connection string can still access those same secrets.