--- title: Azure Functions in .NET | daily.dev description: Azure Functions are presented as a cost-effective, serverless alternative to traditional Web APIs for event-driven workloads, background jobs, and lightweight... canonical: https://daily.dev/posts/azure-functions-in-net-shmxaognq twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Azure Functions in .NET | daily.dev og:description: Azure Functions are presented as a cost-effective, serverless alternative to traditional Web APIs for event-driven workloads, background jobs, and lightweight... og:url: https://daily.dev/posts/azure-functions-in-net-shmxaognq og:image: https://api.daily.dev/og/posts/SHMxaOGNQ.png og:image:alt: Azure Functions in .NET og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Azure Functions in .NET **[NikolaTech](https://daily.dev/sources/nikolatech)** · 5 min read · 0 upvotes · 0 comments ## Summary Azure Functions are presented as a cost-effective, serverless alternative to traditional Web APIs for event-driven workloads, background jobs, and lightweight APIs. The post covers triggers and bindings, Durable Functions for stateful orchestration, and the difference between the in-process and isolated worker models for .NET. It highlights that the in-process model is being retired, with support ending November 10, 2026, making migration to .NET Isolated the recommended path. It also walks through dependency injection setup in the isolated model and shows code examples for timer and HTTP triggers, closing with consumption plan pricing details (1 million free executions and 400,000 GB-s per month). ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### When does the Azure Functions .NET in-process model reach end of support? The in-process model for Azure Functions will no longer be supported after November 10, 2026. After that date, only the .NET Isolated worker model will be available, which also supports both LTS and STS .NET versions. Developers starting new projects or maintaining existing ones should migrate to .NET Isolated ahead of this deadline. _Track .NET runtime deprecation deadlines like this one on daily.dev before they catch your Azure Functions project off guard._ ### What is the difference between Azure Functions in-process and isolated worker models? The in-process model runs function code in the same process as the Azure Functions host, while the isolated worker model runs code in a separate .NET process independent of the host. Both behave similarly from a developer's perspective, but the isolated model adds middleware support for handling cross-cutting concerns, and it is the only model with a future since in-process is being retired. _Developers choosing a worker model for new Azure Functions projects can compare trade-offs like this on daily.dev._ ### How much does the Azure Functions consumption plan cost for free usage? The Azure Functions consumption plan includes 1 million executions per month free and 400,000 GB-s of resource consumption per month free. This allows many production-level workloads to run for only a few dollars a month or even free depending on usage, though the automatically created Azure Storage Account is billed separately and not part of the free grant. _Teams evaluating serverless costs can weigh pricing details like this on daily.dev before committing to a platform._ ## Similar posts on daily.dev - [Jaliya's Blog: Microsoft Agent Framework: Deterministic Multi-Agent Orchestrations with .NET Durable Functions](https://daily.dev/posts/jaliya-s-blog-microsoft-agent-framework-deterministic-multi-agent-orchestrations-with-net-durable-8fbicq1sw) · We Are .NET · 1 upvotes · 0 comments - [Azure Functions Ships Serverless Agents Runtime at Build 2026](https://daily.dev/posts/azure-functions-ships-serverless-agents-runtime-at-build-2026-sajc9mte5) · InfoQ · 0 upvotes · 0 comments - [Jaliya's Blog: Microsoft Agent Framework: Agents on Azure Functions with .NET](https://daily.dev/posts/jaliya-s-blog-microsoft-agent-framework-agents-on-azure-functions-with-net-e97slpynw) · We Are .NET · 0 upvotes · 0 comments - [Serverless and Microservices with C\# & Azure](https://daily.dev/posts/serverless-and-microservices-with-c-azure-ejedzqor1) · freeCodeCamp · 11 upvotes · 0 comments - [.NET 10 in Azure: A Path Through Your Estate](https://daily.dev/posts/net-10-in-azure-a-path-through-your-estate-lb2ojuqe6) · gitconnected · 7 upvotes · 0 comments --- Tags: [#.net](https://daily.dev/tags/.net), [#serverless](https://daily.dev/tags/serverless), [#c#](https://daily.dev/tags/c#), [#dependency-injection](https://daily.dev/tags/dependency-injection), [#azure-functions](https://daily.dev/tags/azure-functions) [View this post on daily.dev](https://daily.dev/posts/azure-functions-in-net-shmxaognq) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Azure Functions in .NET","url":"https://daily.dev/posts/azure-functions-in-net-shmxaognq","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/azure-functions-in-net-shmxaognq"},"datePublished":"2026-10-04T13:05:51.832Z","dateModified":"2026-10-04T13:12:28.596Z","description":"Azure Functions are presented as a cost-effective, serverless alternative to traditional Web APIs for event-driven workloads, background jobs, and lightweight...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/374aa1b6e6837dec2215d01336e7e5f2?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/374aa1b6e6837dec2215d01336e7e5f2?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"NikolaTech","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"NikolaTech","logo":"https://media.daily.dev/image/upload/s--1h2fO6FL--/f_auto,q_auto/v1791119050/logos/nikolatech?_a=BAMAMicg0","url":"https://daily.dev/sources/nikolatech"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/azure-functions-in-net-shmxaognq","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":".net,serverless,c#,dependency-injection,azure-functions","timeRequired":"PT5M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"NikolaTech","item":"https://daily.dev/sources/nikolatech"},{"@type":"ListItem","position":3,"name":"Azure Functions in .NET"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/azure-functions-in-net-shmxaognq#faq","mainEntity":[{"@type":"Question","name":"When does the Azure Functions .NET in-process model reach end of support?","acceptedAnswer":{"@type":"Answer","text":"The in-process model for Azure Functions will no longer be supported after November 10, 2026. After that date, only the .NET Isolated worker model will be available, which also supports both LTS and STS .NET versions. Developers starting new projects or maintaining existing ones should migrate to .NET Isolated ahead of this deadline. Track .NET runtime deprecation deadlines like this one on daily.dev before they catch your Azure Functions project off guard."}},{"@type":"Question","name":"What is the difference between Azure Functions in-process and isolated worker models?","acceptedAnswer":{"@type":"Answer","text":"The in-process model runs function code in the same process as the Azure Functions host, while the isolated worker model runs code in a separate .NET process independent of the host. Both behave similarly from a developer's perspective, but the isolated model adds middleware support for handling cross-cutting concerns, and it is the only model with a future since in-process is being retired. Developers choosing a worker model for new Azure Functions projects can compare trade-offs like this on daily.dev."}},{"@type":"Question","name":"How much does the Azure Functions consumption plan cost for free usage?","acceptedAnswer":{"@type":"Answer","text":"The Azure Functions consumption plan includes 1 million executions per month free and 400,000 GB-s of resource consumption per month free. This allows many production-level workloads to run for only a few dollars a month or even free depending on usage, though the automatically created Azure Storage Account is billed separately and not part of the free grant. Teams evaluating serverless costs can weigh pricing details like this on daily.dev before committing to a platform."}}]} ```