OnLTS
End of support: November 10, 2026

The Azure Functions in-process model reaches end of support on November 10, 2026.

I migrate your function apps to the isolated worker model on .NET 10 for a fixed price. You get a pull request with your own tests passing and a step-by-step plan to switch the app in Azure through a staging slot.

See the fixed prices Run the free check first

Why in-process apps have to move

  • End of support. After November 10, 2026 the in-process model gets no fixes and no support from Microsoft.
  • No .NET 10. In-process stops at .NET 8. .NET 10 only runs on the isolated worker model.
  • .NET 8 ends the same day. .NET 8 and .NET 9 reach end of support on November 10, 2026 too, so an in-process app on .NET 8 hits both deadlines at once.
  • Linux Consumption plan: .NET 10 apps can't run there. They need the Flex Consumption plan.
  • Silent breakage. The isolated worker uses System.Text.Json, which ignores [JsonProperty] and binds those properties to default values without any error.

Sources: Migrate to the isolated worker model · In-process vs isolated, supported versions · .NET 8 and 9 end of support

Fixed price, three sizes

Prices in USD, paid through Upwork. You know the full cost before anything starts.

Every tier includes

  • Project moved to the isolated worker SDK and net10.0, worker packages in place of Microsoft.Azure.WebJobs.*
  • Program.cs with your FunctionsStartup registrations, logging and Application Insights
  • Function signatures, bindings and output bindings converted; HTTP triggers on ASP.NET Core integration
  • Every Newtonsoft attribute on bound types found and converted, so nothing binds to default values
  • A deployment runbook: FUNCTIONS_WORKER_RUNTIME, staging slot, swap, and the CI/CD settings to update
  • 14 days of fixes for anything the migration caused
Starter

One small function app

US$490

Delivery in 5 days from access.

  • One function app, up to 10 functions
  • HTTP, timer, queue and blob triggers
  • 1 revision
Order one small function app
Standard

Larger or two apps

US$890

Delivery in 8 days from access.

  • Up to 2 function apps, up to 30 functions in total
  • Any standard binding, including Service Bus (extension 5.x), Event Hubs and Cosmos DB
  • 2 revisions
Order larger or two apps
Advanced

Several apps

US$1,490

Delivery in 12 days from access.

  • Up to 5 function apps, up to 80 functions in total
  • Durable Functions, middleware and custom serialization
  • 3 revisions
Order several apps

Delivery in business days from access. If your code turns out bigger than the tier you bought, I tell you before starting and you choose: pay the difference or get a full refund.

Not included

  • Switching the function app in Azure: that is a deployment step you run, with my runbook
  • Changing the hosting plan (for example Linux Consumption to Flex Consumption)
  • Moving off the retired Service Bus SDK in code outside the functions (a separate fixed-price job)
  • New features or refactoring beyond what the migration needs

How I work

Everything happens in writing, on your schedule. A 15-minute call is available if you want one, never required.

  1. Read-only access. Add a read-only collaborator on GitHub, Azure DevOps or GitLab, or send a zip. No production credentials and no secrets.
  2. The work gets done. A set of AI coding agents does the scanning, the code changes and the test runs. I review every change and sign off before you see it.
  3. You get a pull request. With notes on what changed, what to watch on deploy and the results of your own tests. Without write access, you get a patch file.
  4. You deploy. I never touch production: no deploys, no production databases, no infrastructure changes. You merge and release when it suits you.

The job is accepted when the solution builds and your existing tests pass. Tests that already failed before are listed in the notes and stay out of scope. No automated tests? We agree on a short smoke checklist before I start, and that becomes the acceptance criterion.

Free first step: check your solution yourself

Net10Check is a free command-line tool. Run it in your solution folder and it flags every in-process function project, the retired Service Bus SDKs and the other things that block .NET 10. It runs locally and uploads nothing.

dotnet tool install -g Net10Check
net10-check

If the report is short, you can probably do it in-house. If it is long, send it to me and I will tell you, for free, which tier fits. Message me on Upwork.

FAQ

Can we stay on .NET 8 and just switch to isolated?

Yes, the isolated worker supports .NET 8, but .NET 8 itself leaves support on November 10, 2026. I target .NET 10 unless you have a reason not to, and the price is the same.

Do you change the function app in Azure?

No. I never touch production. You get the pull request and a runbook for the staging slot and the swap, which avoids the error window between changing the runtime setting and deploying the new build.

Our functions run on .NET Framework 4.8.

The isolated worker supports .NET Framework 4.8, so a migration without moving to .NET is possible. Tell me before buying and I will confirm the tier.

Which tier do I need?

Count the function apps and functions, or run Net10Check and send me the output. I tell you the tier for free before you buy.