azurefunctions

This article explains how to (possibly) fix an error along the lines of "Encountered error while fetching the list of EventHub PartitionIds" which is thrown by your Azure Function (or other code) trying to trigger based on IoT Hub or Event ...

Here is another pretty quick one - trying to debug Azure Functions fails with a confusing error message about failing to create a lease for a partition.

In this article, I'm listing the quick fixes to your Azure Functions suddenly throwing seemingly random and very unexpected CORS errors.

One more article before Christmas! 😁 This time, I'll be fixing a function that's triggering based on new messages received through my IoT Hub in my Azure Functions project.

Another fun one with Azure Functions! At least it's a simple one: this time, I ran into a weird issue while doing some code reusing - well, copy-pasting - between a couple of different projects.

This article explains how to fix an issue where your Azure Functions function (yes, that's a capital F and a lowercase f to denote the difference between the product and the piece of compute) fails to fire when a POST request comes in, even though it...

This article explains another fun issue that you might run into when developing Azure Functions in your local environment. It was weird how unclear the few results were that I could find. And the issue is just... very hazy in general.

This article aims to patch one annoying gap in Microsoft's documentation: how, exactly, do you update Azure Function App's application settings using an Azure DevOps build/release pipeline?

Another day, another issue with Azure Functions ! For such a simple and powerful tool, it sure does produce a lot of topics for blog articles!

Sometimes, you need to change the hosting model (or tier) for your resources on Azure.

Well, that title is a mouthful. But it's the topic for today, so what can you do? That said, this article should be pretty topical, as the issue started popping up only a few days ago.

Ah, one more on the related topics of different configurations for your Azure Function apps. In this article, I will describe how you can configure the Entity Framework Core database context to be injected into your Azure Functions App.

Azure Functions use dependency injection, and that allows us to define all kinds of prebuilt or custom-built services as being available for our functions really easily.

Hah - another interesting one. This article describes how to resolve an error along the lines of " Microsoft.Data.SqlClient: Microsoft.Data.SqlClient is not supported on this platform. ", thrown by the Azure Functions host.

This article describes a solution to an error "Insufficient memory to continue the execution of the program." I was debugging an Azure Function locally and ran into it - it stopped my Azure Function from starting at all.

So, another interesting issue I ran into when developing Azure Functions locally. What an endless bag of funsies!

I don't know about you, but it's happened to me a few times: fire up your Azure functions project, hit F5 to start debugging project builds without errors, Azure Functions host starts... And shuts down right away.

This post describes how you can easily enable debug/verbose information for your Azure Functions for a lightweight and built-in way to extract just a bit more information out of your Azure Function executions.

This post describes how you can access your Entity Framework Core model classes and the database context in your Azure Functions. In my example I'm using EF Core 2.1, but the main principle should be the same for later versions as well.

Welp - another interesting error encountered while deploying Azure Functions to Azure.

Have you ever run into a situation, where you just wanted to remove the currently standing function definitions from your app service without actually nuking the whole Functions app? I have!

I recently ran into an issue when developing Azure Functions locally. My SPFx webpart was configured to request information from my locally running Azure Function but suddenly started ending up in error.

Ignite 2018 is done and dusted, and it's a good time to quickly recap what's new for Azure Functions in the coming months. They've certainly been getting a lot of love from Microsoft, which is GREAT!

Let me start this article, by reminding everyone that Azure Functions are awesome, and you should use them despite some hiccups. Having said that, let's fix some errors!

This article explains how you can access an Azure Function's Application/Environment settings/variables from your C# code.