Simplicity IT Professional Service | Scoped implementation

Azure Functions Isolated Worker Migration: 2-Week Implementation

App teams facing .NET in-process retirement: move a bounded C# Functions scope with tests, approved cutover and recovery.

A Simplicity IT engineer will call you shortly.

Request a call

What this implementation gives you

  • An app inventory and per-app migration plan.
  • Reviewed source changes and deployment-pipeline updates for the agreed apps.
  • Test, cutover, rollback and monitoring evidence.
  • Owner sign-off and an operations handoff.

Scope and boundaries

Two weeks applies to a small, ready app scope. The delivery guide sizes implementation at 2 to 4 weeks after app complexity, source access, hosting and test readiness are confirmed.

Target .NET 10 on Functions host 4 where supported. A .NET Framework-only dependency may require the supported .NET Framework 4.8 isolated path. Linux Consumption apps need a new Flex Consumption app and a separate cutover plan. The customer approves source changes, role assignments, production cutover and rollback.

  • Functional redesign and non-.NET app migration need separate scope.
  • Older Functions host upgrades and broad network redesign need separate scope.
  • Durable Functions storage data migration is excluded.
  • Azure licenses and consumption are separate.

Your approval before production changes

A named customer owner approves each production change or cutover against the agreed scope, test evidence, rollback path, operating owner, and expected cost before it proceeds.

How the engagement runs

  1. Scope the apps

    Review C# source, Functions host, bindings, dependencies, hosting and test owners.

  2. Change and test

    Update the agreed apps and pipelines in customer-owned source control, then test in a supported staging path.

  3. Approve cutover

    App owners and change managers approve each production move and recovery plan.

  4. Verify and hand over

    Check production behavior, monitor results and deliver operating notes.

Evidence to decision flow

Context approved

The customer confirms scope, access, acceptance criteria, change windows, and named approvers before build activity begins.

Controlled delivery

Simplicity IT builds and tests only the accepted work packages in the customer-owned environment, with evidence recorded at each checkpoint.

Your decision

A named customer owner reviews the exact change, test result, rollback path, operating owner, and cost impact before any production effect or cutover.

Evidence retained

The as-built record, acceptance evidence, rollback status, decision log, and operational handoff are retained according to the customer agreement.

Microsoft technologies in scope

  • Azure Functions
  • .NET isolated worker
  • GitHub Actions or Azure Pipelines

Plan your Marketplace purchase

The Marketplace listing is a saved Contact Me draft, not a checkout. Discuss app count, complexity, terms and a customer-specific private-offer option before any purchase. Microsoft licenses and Azure consumption are separate.

Bring the app inventory, source repositories, hosting and test owners to a scoping call. Two weeks applies only to a small, ready scope.

Discuss a private offer