Azure Functions In-Process Model Deprecation — Migration to Isolated Worker Model Required

Brief description of your issue

The WinGet REST Source Functions project (WinGet.RestSource.Functions) uses the Azure Functions in-process hosting model, which Microsoft has announced will retire on November 10, 2026. After this date, in-process function apps will no longer be supported and may stop functioning.

When deploying via the Microsoft.WinGet.RestSource PowerShell module (v1.10.0), the Azure portal shows a deprecation banner on the deployed Function App:

Action required: Migrate your Azure Functions app to the isolated worker model before November 10, 2026.

Steps to reproduce

1. Deploy a WinGet REST source using:

   Install-Module Microsoft.WinGet.RestSource
   New-WinGetSource -Name "mywinget" -ResourceGroup "rg-winget" -Region "westeurope"
   

2. Open the deployed Function App in the Azure portal.
3. Observe the deprecation banner at the top of the Function App blade.

Expected behavior

The project should use the Azure Functions isolated worker model (Microsoft.Azure.Functions.Worker) to ensure continued support and compatibility beyond November 2026.

Actual behavior

The project's WinGet.RestSource.Functions.csproj references in-process model packages

Environment

N/A

Start by inspecting src/WinGet.RestSource.Functions/WinGet.RestSource.Functions.csproj and the deployment path used by the Microsoft.WinGet.RestSource PowerShell module. Identify the current in-process package references and the project changes required for the isolated worker model. Done means the deployed Function App no longer shows the Azure deprecation banner and remains compatible beyond November 10, 2026.