Future of Webjobs on Azure App Services

Beau Tang 26 Reputation points
2026-09-17T10:10:31.8733333+00:00

Hello everyone.

I have this vague memory of reading that Webjobs on Azure App Services were going to be retired but I can't find any references to that. It was some time ago.

Is my memory playing tricks on me?

Thank you.

Azure App Service
Azure App Service

Azure App Service is a service used to create and deploy scalable, mission-critical web apps.

Answer accepted by question author
Marcin Policht 108.3K Reputation points MVP Volunteer Moderator
2026-09-17T11:22:38.75+00:00

Azure WebJobs themselves have not been retired or deprecated. They remain fully supported by Microsoft.

I gather your impression might be based on one of three related retirements or changes.

The first is the retirement of Azure Scheduler. Azure Scheduler was fully shut down on December 31, 2019. Many developers used Azure Scheduler to configure and trigger Scheduled WebJobs. When Scheduler was retired, Microsoft advised migrating those specific Scheduler-based triggers to Azure Logic Apps. The WebJobs cron-schedule engine itself was not affected. Scheduled WebJobs configured through App Service with Always On continue to operate.

The second is the deprecation of the AzureWebJobsDashboard application setting. If you worked with the WebJobs SDK or legacy Azure Functions, you may remember notifications concerning this setting. It was used to output logs to a classic storage dashboard, which Microsoft phased out in favor of Azure Monitor and Application Insights. This was a change to the logging mechanism and was not a retirement of WebJobs themselves.

The third is Microsoft's broader shift toward Azure Functions and Azure Container Apps. WebJobs remain supported, but Azure Functions is the more modern serverless model and is built on the WebJobs SDK. For containerized background tasks that run for a finite duration, Azure Container Apps Jobs provide a cloud-native alternative.

If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

hth

Marcin

Was this answer helpful?

1 person found this answer helpful.

1 additional answer

Sort by: Newest
Most helpful Newest Oldest

  1. AI answer

    2026-09-17T10:10:46.28+00:00

    No general retirement of Azure App Service WebJobs is indicated in the provided Microsoft documentation.

    Current documentation describes WebJobs as a built-in App Service feature that is supported across Windows code, Windows containers, Linux code, and Linux containers, with one notable exception: custom Linux containers based on Alpine Linux aren't supported. The docs also state that all App Service plans support WebJobs and that there is no extra cost to use them.

    What the guidance does say is that WebJobs are best suited when background processing should share the same lifecycle, configuration, and deployment as an existing App Service app. For new workloads, especially event-driven or independently scalable background processing, the recommendation is to evaluate Azure Functions or Container Apps jobs instead. That is a positioning recommendation, not a retirement notice.

    There is also a recent Microsoft Q&A answer that recommends WebJobs for background processing when an App Service app hits the HTTP timeout limit, which further aligns with WebJobs still being a supported option.

    So the supported conclusion is:

    • WebJobs are still documented and supported in Azure App Service.
    • There is no retirement notice for WebJobs in the provided sources.
    • Microsoft guidance favors Azure Functions or other services for some new scenarios, which may be the source of the impression that WebJobs were being phased out.
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.