Blog
Serverless on Azure
Running code without managing servers.
Services, hosting plans, scaling and cold starts.
2026
-
Flex Consumption wins, except for your batch jobs
Leaving Azure Functions Linux Consumption? Measured with the same app on all three targets, Flex Consumption usually responded from a cold start in under two seconds versus 20 seconds on Container Apps, and ran almost all of its timers on the minute. Container Apps Jobs win when a failed batch run has to be retried, with the platform keeping count.
-
Azure Static Web Apps: One deleted function takes down the whole API
If main in api/package.json points to a deleted file, every Static Web App API route fails despite a successful deployment: HTTP 500 in v3, HTTP 404 in v4.
-
Your Function App says 200, your data disagrees
On the isolated worker, serialization, dependency injection and telemetry behave differently. Nothing fails the build, and a null field behind HTTP 200 goes unnoticed. Every case, plus a checklist.
-
Skip .NET 11: your Azure estate belongs on .NET 10
.NET 11 ships the day .NET 8 and .NET 9 lose support, and its support ends the same day as .NET 10's. Take inventory first, then move Container Apps, App Service, and Function Apps last, one slot or revision at a time.
-
Fabric: The Hidden Destination
Turn Microsoft Fabric into a real-time event source: route EventStream data through an Azure Function into Event Grid so operational Azure workloads can react in near real time.
No articles match your search.