failed to update app settings in function app "WEBSITE_CONTENTAZUREFILECONNECTIONSTRING"

Xuefeng Luo 20 Reputation points Microsoft Employee
2025-04-08T03:28:36.3266667+00:00

Hi Experts:

Due to company compliance requirements, we need to promptly update our Function App to use Managed Identity for invoking and updating Azure Functions. We followed the instructions on this page: https://eng.ms/docs/cloud-ai-platform/devdiv/serverless-paas-balam/serverless-paas-vikr/app-service-web-apps/app-service-team-documents/functionteamdocs/faqs/tutorial-secretless-mi#configure-your-function-app-and-storage-account-with-managed-identity

However, when updating the L2AzureFunctionTest Function App(L2AzureFunctionTest/environmentVariablesAppSettings), we encountered an issue: Even though we have configured the WEBSITE_RUN_FROM_PACKAGE app setting with an Azure Blob URL (e.g., https://(storageblob).blob.core.windows.net/azure-l2adfprod/L2ADFProd.zip), we are unable to remove the two app settings:

WEBSITE_CONTENTSHARE

WEBSITE_CONTENTAZUREFILECONNECTIONSTRING

We keep receiving the error:

“Required parameter WEBSITE_CONTENTAZUREFILECONNECTIONSTRING is missing.”

Could an expert help us understand how to properly migrate this Function App to use Managed Identity and eliminate the use of secrets for Function App updates and deployments?

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
5,909 questions
0 comments No comments
{count} votes

Accepted answer
  1. Deepanshukatara-6769 16,565 Reputation points Moderator
    2025-04-08T07:17:03.4066667+00:00

    Hello ,

    This is applicable for function apps running on dedicated app service plan however for apps running on consumption and premium plan, there are additional settings that needs to be added WEBSITE_CONTENTAZUREFILECONNECTIONSTRING with storage account connection string value and WEBSITE_CONTENTSHARE with storage account fileshare name. Please note that these settings are not applicable for Linux plans.

    So The limitation is on the Azure Files side which is used by Consumption and EP plans for dynamic scaling.

    The following issue has more info on this matter: Managed identity support for WEBSITE_CONTENTAZUREFILECONNECTIONSTRING setting


    Please "Accept Answer" if the answer is helpful so that others in the community may benefit from your experience.

    Thanks
    Deepanshu


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.