Problem Deleting Azure Functions Flex Consumption Always Ready Instance
- Dominant language
- Python
- Stars
- 4.6k
- Forks
- 3.5k
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 60
Description
### Describe the bug
When attempting to delete Always Ready instances from a Flex Consumption Function App using the Azure CLI, the deletion does not work when targeting the `function` setting name.
- Running the command with `--setting-names http` successfully removes the Always Ready configuration.
- Running the command with `--setting-names function:` does **not** remove the Always Ready configuration.
- The CLI output suggests the configuration should be removed, but the `alwaysReady` list is not cleared.
As shown in the attached log output (with the Tenant IDs and Subscription IDs scrubbed), the `PUT` request sent to the app still contains the `alwaysReady`, which is probably preventing the deletion from being applied.
### Related command
az functionapp scale config always-ready delete
### Errors
No errors, but the Always Ready instance is not deleted.
### Issue script & Debug output
[delete-already-ready-output.txt](https://github.com/user-attachments/files/22432350/delete-already-ready-output.txt)
### Expected behavior
Deleting Always Ready instances using `--setting-names function:` should delete the Always Ready instance(s).
### Environment Summary
azure-cli 2.77.0
core 2.77.0
telemetry 1.1.0
Dependencies:
msal 1.34.0b1
azure-mgmt-resource 23.3.0
Python location 'C:\Program Files\Microsoft SDKs\Azure\CLI2\python.exe'
Config directory 'C:\Users\chadg\.azure'
Extensions directory 'C:\Users\chadg\.azure\cliextensions'
Python (Windows) 3.13.7 (tags/v3.13.7:bcee1c3, Aug 14 2025, 14:15:11) [MSC v.1944 64 bit (AMD64)]
### Additional context
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.