Skip to content

webapp config set generic-configurations silently ignores webJobsEnabled #33823

Description

@btardif

Describe the bug

az webapp config set --generic-configurations exits successfully but silently ignores the valid App Service site configuration property webJobsEnabled. The behavior reproduces with both documented input forms: a key=value argument and a JSON file.

Related command

# Begin with properties.webJobsEnabled=true.
az webapp config set `
  --name <linux-app-name> `
  --resource-group <resource-group> `
  --generic-configurations 'webJobsEnabled=false' `
  --output none

'{"webJobsEnabled":false}' | Set-Content .\webjobs-config.json -NoNewline

az webapp config set `
  --name <linux-app-name> `
  --resource-group <resource-group> `
  --generic-configurations '@.\webjobs-config.json' `
  --output none

Verify through the ARM child resource:

az rest `
  --method get `
  --uri "https://management.azure.com/subscriptions/<subscription-id>/resourceGroups/<resource-group>/providers/Microsoft.Web/sites/<app-name>/config/web?api-version=2024-11-01" `
  --query properties.webJobsEnabled `
  --output tsv

Errors

No error is emitted. Both az webapp config set commands exit 0, but the property remains unchanged.

Issue script & Debug output

Sanitized isolated result:

Before        : true
KeyValueExit  : 0
AfterKeyValue : true
JsonFileExit  : 0
AfterJsonFile : true

The same property is writable through the generic ARM command:

$webConfigId = "/subscriptions/<subscription-id>/resourceGroups/<resource-group>/providers/Microsoft.Web/sites/<app-name>/config/web"

az resource update `
  --ids $webConfigId `
  --api-version 2024-11-01 `
  --set properties.webJobsEnabled=true

That command persists the value successfully.

Expected behavior

az webapp config set --generic-configurations should either:

  • persist webJobsEnabled, or
  • reject the unsupported or unmapped property with a nonzero exit code and actionable error.

It should not silently exit 0 while discarding the requested configuration.

Environment Summary

azure-cli                         2.88.0
core                              2.88.0
telemetry                          1.1.0

Extensions:
azure-devops                       1.0.6
kusto                              0.5.0
resource-graph                     2.1.1

Dependencies:
msal                              1.36.0
azure-mgmt-resource               24.0.0

Python location 'C:\Program Files\Microsoft SDKs\Azure\CLI2\python.exe'
Python (Windows) 3.14.5 [MSC v.1944 64 bit (AMD64)]
PowerShell 7.6.4
Windows 10.0.26200

Additional context

This was isolated on an App Service for Linux app. Leaving webJobsEnabled=false causes Linux WebJob operations to return 409 Conflict, even when the WebJob payload is deployed correctly.

No existing Azure/azure-cli issue containing webJobsEnabled was found.

Suggested assignee: Jordan Selig (@seligj95)

Activity

  1. added
    bugThis issue requires a change to an existing behavior in the product in order to be resolved.
    on Jul 31, 2026
  2. yonzhan commented on Jul 31, 2026

    @yonzhan
    Collaborator

    Thank you for opening this issue, we will look into it.

  3. added
    ARMaz resource/group/lock/tag/deployment/policy/managementapp/account management-group
    Azure CLI TeamThe command of the issue is owned by Azure CLI team
    questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
    on Jul 31, 2026
  4. x-engineering-agent commented on Jul 31, 2026

    @x-engineering-agent
    Contributor

    Bug Analysis

    az webapp config set --generic-configurations silently ignores/drops the webJobsEnabled site-config property for both input forms (key=value and @file.json), exiting 0 without applying the change. This CLI command lives in the appservice module at src/azure-cli/azure/cli/command_modules/appservice/.

    Root cause is likely in the update logic for generic configurations (e.g. update_site_configs / the code parsing generic_configurations in custom.py), where webJobsEnabled may not map onto the SiteConfigResource model the same way as other keys, or gets filtered out before the PATCH/PUT call to the config/web ARM resource. Confirm by tracing how generic_configurations key/value pairs are applied to the SiteConfig object versus the working az resource update --set properties.webJobsEnabled=... path, which patches the same ARM resource directly and succeeds.

    Expected fix: ensure webJobsEnabled (and any other currently-dropped generic-configuration keys) is correctly mapped and persisted, or if truly unsupported, raise a clear, actionable error instead of silently succeeding.

    Use this EXACT PR title: [AppService] Fix #33823: az webapp config set --generic-configurations: Fix generic-configurations silently dropping webJobsEnabled

    PR title & description format (required)

    This repo enforces a PR format (guide). Please author the PR exactly as follows or CI's Check the Format of Pull Request Title and Content will fail.

    Use this EXACT PR title (copy verbatim, do not reword):

    [AppService] Fix #33823: `az webapp config set --generic-configurations`: Fix generic-configurations silently dropping webJobsEnabled
    

    Keep the backticks around the command and the Fix #33823: prefix. You may only adjust the wording after the command (the final summary) if the fix changes; the [AppService] prefix, issue link, and backticked command must stay.

    Description — follow the PR template and fill in:

    • Link the issue — start the Description with a closing keyword so the PR auto-links and closes it: Fixes #33823.
    • Related command — the az ... command this affects.
    • Description (mandatory) — why the bug happens, what you changed, and the resulting behavior.
    • Testing Guide — example command(s) showing the fix works.
    • History Notes — leave the title to drive the history note, or add extra lines in the same format (component in brackets + the command in backticks), e.g. [AppService] `az <command>`: <note>.
    • Keep the template checklist and tick the items you've satisfied.

    Posted by agent-assist (autonomous bug-fix pipeline).

  5. removed
    questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
    Azure CLI TeamThe command of the issue is owned by Azure CLI team
    on Aug 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

ARMaz resource/group/lock/tag/deployment/policy/managementapp/account management-groupAuto-AssignAuto assign by botService AttentionThis issue is responsible by Azure service team.Web Appsaz webappact-identity-squadact-observability-squadapp-service-generalbugThis issue requires a change to an existing behavior in the product in order to be resolved.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions