According to the docs I can set the values using this syntax. As far I can see, nothing is mentioned regarding the case sensitivity.
When I execute this:
az webapp config appsettings set --settings test01="lower-cased" ...
it behaves as expected. Then, executing the following:
az webapp config appsettings set --settings test01="lower-cased to be upped" ...
also performs as expected (updating the value). However, execution of the below produces an error.
az webapp config appsettings set --settings Test01="upper-cased" ...
That surprises me because if Azure is case-sensitive, then no collision should occur, hence allowing me to have two independent variables (i.e. test01 and Test01). Conversely, if it is case-insensitive, then no collision should occur neither, hence updating the previously set value.
Instead, I see this error message. It confuses me.
Operation returned an invalid status 'Conflict'
This is an expected behavior as it is due the case sensitivity of Azure App Service settings.
If you provide same name of setting with same case-sensitivity, then it will update the setting with new value:
If you try changing case and and execute command, you will get conflict error because App setting thinks Test and test both are same and it thinks it as a duplicate as @Dai said.