Is deployment of flex consumption function apps not supported under release pipelines?

Question

Is deployment of flex consumption function apps not supported under release pipelines?

Oblio 71

Related to this question, it appears that I cannot deploy a function app to a flex consumption resource using a release pipeline (not a build pipeline) because the interface does not provide fields to set the values correctly. Can someone confirm or tell me how to do it? Currently I have a release pipeline that uses AzureFunctionApp@2 and the flex plan is checked. The task deceptively succeeds after not deploying anything and logs "The Deployment Type option does not apply for Flex Consumption."

Mohammad Altaf 360 Reputation points Microsoft External Staff Moderator

2026-07-23T13:16:09.81+00:00

Hi @Oblio

Just following up to see if your issue has been resolved or if you had a chance to review my earlier comment?
Oblio 71 Reputation points

2026-07-23T13:22:04.2966667+00:00

Yes, it turns out that it was the existence of that env var that was causing the problem.

Answer accepted by question author

0 additional answers

Your answer

Mohammad Altaf 360 Reputation points Microsoft External Staff Moderator

2026-07-23T13:16:09.81+00:00

Hi @Oblio

Just following up to see if your issue has been resolved or if you had a chance to review my earlier comment?
Oblio 71 Reputation points

2026-07-23T13:22:04.2966667+00:00

Yes, it turns out that it was the existence of that env var that was causing the problem.

Answer 1

Hi @Oblio

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

Azure Functions running on the Flex Consumption plan use a different deployment model than other Azure Functions hosting plans. The message "The Deployment Type option does not apply for Flex Consumption" is expected behavior and does not by itself indicate that the deployment has failed.

According to the maintainer of the AzureFunctionApp@2 task, when the target Function App is identified as a Flex Consumption app, the task ignores the traditional deployment type setting and follows the Flex Consumption deployment path automatically.

If the deployment task completes successfully but the Function App is not updated, the issue is typically related to deployment validation, storage access/permissions, or unsupported application settings. Reported examples include the presence of the WEBSITE_RUN_FROM_PACKAGE setting on Flex Consumption apps and storage access issues during deployment.

To help identify the root cause, please enable System.Debug = true in the pipeline and review the deployment logs for any OneDeploy, storage access, or deployment validation errors. These logs usually provide the specific reason why the deployment completed without updating the application.

Hope this helps. Please let us know if you need further assistance.

Mohammad Altaf 360 Reputation points Microsoft External Staff Moderator

2026-07-23T16:00:59.0433333+00:00

Hi @Oblio ,

Thanks for your positive response, If the assistance was helpful, kindly take a moment to click on Accept Answer and click on Yes. It will be helpful for other community members.

Thank you!