Repository navigation
webapp config set generic-configurations silently ignores webJobsEnabled #33823
Description
Activity
- addedbugThis issue requires a change to an existing behavior in the product in order to be resolved.This issue requires a change to an existing behavior in the product in order to be resolved.
on Jul 31, 2026 - addedWeb Appsaz webappaz webappService AttentionThis issue is responsible by Azure service team.This issue is responsible by Azure service team.Auto-AssignAuto assign by botAuto assign by bot
on Jul 31, 2026 Thank you for opening this issue, we will look into it.
- addedARMaz resource/group/lock/tag/deployment/policy/managementapp/account management-groupaz resource/group/lock/tag/deployment/policy/managementapp/account management-groupAzure CLI TeamThe command of the issue is owned by Azure CLI teamThe command of the issue is owned by Azure CLI teamquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
on Jul 31, 2026 x-engineering-agent commented
on Jul 31, 2026 ContributorMore actionsBug Analysis
az webapp config set --generic-configurationssilently ignores/drops thewebJobsEnabledsite-config property for both input forms (key=valueand@file.json), exiting0without applying the change. This CLI command lives in theappservicemodule atsrc/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 parsinggeneric_configurationsincustom.py), wherewebJobsEnabledmay not map onto theSiteConfigResourcemodel the same way as other keys, or gets filtered out before the PATCH/PUT call to theconfig/webARM resource. Confirm by tracing howgeneric_configurationskey/value pairs are applied to theSiteConfigobject versus the workingaz 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 webJobsEnabledPR 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 webJobsEnabledKeep 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).
- Link the issue — start the Description with a closing keyword so the PR auto-links and closes it:
- linked a pull request that will close this issue[Appservice] fix: `az webapp config set --generic-configurations` silently ignores camelCase properties like `webJobsEnabled` #33826
on Aug 1, 2026 - removedquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatAzure CLI TeamThe command of the issue is owned by Azure CLI teamThe command of the issue is owned by Azure CLI team
on Aug 1, 2026
Describe the bug
az webapp config set --generic-configurationsexits successfully but silently ignores the valid App Service site configuration propertywebJobsEnabled. The behavior reproduces with both documented input forms: akey=valueargument and a JSON file.Related command
Verify through the ARM child resource:
Errors
No error is emitted. Both
az webapp config setcommands exit0, but the property remains unchanged.Issue script & Debug output
Sanitized isolated result:
The same property is writable through the generic ARM command:
That command persists the value successfully.
Expected behavior
az webapp config set --generic-configurationsshould either:webJobsEnabled, orIt should not silently exit
0while discarding the requested configuration.Environment Summary
Additional context
This was isolated on an App Service for Linux app. Leaving
webJobsEnabled=falsecauses Linux WebJob operations to return409 Conflict, even when the WebJob payload is deployed correctly.No existing Azure/azure-cli issue containing
webJobsEnabledwas found.Suggested assignee: Jordan Selig (@seligj95)