Cannot update config for Flex function b/c of functionAppScaleLimit setting

[rmontroy]

Checked for a solution in the Azure portal

Yes

Investigative information

• Timestamp: Mon Nov 18 2024 21:42:32 GMT-0500 (Eastern Standard Time)
• Function App version: ~4
• Function App name: func-processor-oy7gjmowosxds
• Function name(s) (as appropriate): N/A
• Invocation ID: N/A
• Region: East US 2
• Operation name: Update web sites config

Repro steps

steps required to reproduce the problem:

1. Change any config setting in the Portal or via az webapp config update (e.g., minimum TLS version).
2. Save changes.

Actual behavior

BadRequest
The following site configuration property (Site.SiteConfig.FunctionAppScaleLimit) for Flex Consumption sites is invalid. Please remove or rename it before retrying.

Known workarounds

None
(I tried az resource update --resource-type Microsoft.Web/sites -g <group> -n <func-app-name>/config/web --remove properties.functionAppScaleLimit. There was no error, but the setting was not removed.)

Related information

This function was created via a modified version of this template: functions-quickstart-python-http-azd

[bhagyshricompany]

Hi @rmontroy Thanks for reporting.can you try with consumption plan? please share the snap config.Thanks

[rmontroy]

The issue does not occur with the consumption plan.
Note that the error message is specific to "Flex Consumption sites".

[bhagyshricompany]

@satvu please comment and validate.Thanks

[erwinkramer]

@rmontroy i had this same issue today. I worked around it by setting it to the same value as functionAppConfig.scaleAndConcurrency.maximumInstanceCount. In my case, that value was 100.

I also attempted to force it to null but that didn't update it, probably the same as you attemted, but with Bicep.

[rmontroy]

Thanks @erwinkramer! Can confirm, it worked for me, too.

[RohitRanjanMS]

This may be due to an old version of the API (or an older version of tooling that then uses an older version of the API). Can you confirm if you are still facing this issue?