Flex Consumption Function App deployment fails because Azure adds unsupported build settings.

Question

Flex Consumption Function App deployment fails because Azure adds unsupported build settings.

Kayle Leibold 0

Details: Function App: bts-security-monitor

Resource group: bts-security-monitor-rg

Plan: Linux Flex Consumption, Python 3.11

Every deployment fails with:

InvalidAppSettingsException: The app settings SCM_DO_BUILD_DURING_DEPLOYMENT, ENABLE_ORYX_BUILD are not supported with this SKU.

We removed both settings and restarted the Function App, but Azure’s deployment pipeline continues to add/reject them. The failure occurs using Azure CLI with remote build enabled and disabled, and Functions Core Tools. Please advise the supported deployment method or correct the platform issue.

Kayle Leibold 0 Reputation points

2026-08-18T18:59:06.0966667+00:00

Thank you. Those two settings are absent from the Function App. We also tried the current OneDeploy route using the app's private deployment storage after trying Azure CLI (remote build both enabled and disabled) and Functions Core Tools. The Azure diagnostic logs still show the deployment being rejected for those settings, including failures attributed to az_cli and core_tools.

Is there a specific Azure CLI/Core Tools version or OneDeploy command you recommend for this Linux Flex Consumption Python 3.11 app, or should this be handled through Azure Support?

2 answers

Your answer

Kayle Leibold 0 Reputation points

2026-08-18T18:59:06.0966667+00:00

Thank you. Those two settings are absent from the Function App. We also tried the current OneDeploy route using the app's private deployment storage after trying Azure CLI (remote build both enabled and disabled) and Functions Core Tools. The Azure diagnostic logs still show the deployment being rejected for those settings, including failures attributed to az_cli and core_tools.

Is there a specific Azure CLI/Core Tools version or OneDeploy command you recommend for this Linux Flex Consumption Python 3.11 app, or should this be handled through Azure Support?

Answer 1

kagiyama yutaka 5,085

I think Flex Consumption for Linux Python 3.11 only supports OneDeploy, and those two build‑flags are not supported for this SKU. So the step is a clean OneDeploy ZIP deployment or a func azure functionapp publish with no build flags, and when the deployment is still rejected, send the deploy‑id and correlation‑id to Azure Support.

0 comments

Answer 2

Hi Kayle,

For Flex Consumption, SCM_DO_BUILD_DURING_DEPLOYMENT and ENABLE_ORYX_BUILD should not be used at all. Flex uses One Deploy, and Oryx is automatically used when remote build is requested. (learn.microsoft.com)

For GitHub Actions, use:

uses: Azure/functions-action@v1

with:

app-name: bts-security-monitor

package: .

remote-build: true

Do not include scm-do-build-during-deployment or enable-oryx-build. Microsoft also recommends OIDC authentication rather than a publish profile for Flex deployments. (learn.microsoft.com)

For Python, Core Tools normally requests remote build automatically:

func azure functionapp publish bts-security-monitor

Python 3.11 is supported for this scenario. (learn.microsoft.com)

If the two settings are definitely absent from the Function App and your deployment definition, but Azure still injects them, update Azure CLI/Core Tools and retry. If it still happens, I would open an Azure Support case with the deployment ID and correlation ID. At that point the deployment path is behaving differently from the documented Flex Consumption model.