WEBSITE_CONTENTAZUREFILECONNECTIONSTRING description conflicts with Automation Documentation for Linux

[mwisesyk]

The App settings description for WEBSITE_CONTENTAZUREFILECONNECTIONSTRING states that it is required for Windows and Linux for Consumption and Premium plans: This setting is required for Consumption and Premium plan apps on both Windows and Linux. It's not required for Dedicated plan apps, which aren't dynamically scaled by Functions.

The automation documentation articles/azure-functions/functions-infrastructure-as-code.md states the following though: The [WEBSITE_CONTENTAZUREFILECONNECTIONSTRING](https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-app-settings.md#website_contentazurefileconnectionstring) and [WEBSITE_CONTENTSHARE](https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-app-settings.md#website_contentshare) settings aren't supported on Linux Consumption plan.

Later on it shows it's required for the premium plan with Linux on that page but not for Consumption.

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: 18aa54fd-3aa1-37c5-925c-51a0195b1030
• Version Independent ID: 60198016-1ea9-e7ae-b00b-2c665d5ad8ca
• Content: App settings reference for Azure Functions
• Content Source: articles/azure-functions/functions-app-settings.md
• Service: azure-functions
• GitHub Login: @ggailey777
• Microsoft Alias: glenga

[Naveenommi-MSFT]

@mwisesyk

Thanks for your feedback! We will investigate and update as appropriate.

[MughundhanRaveendran-MSFT]

@mwisesyk , The app setting website_contentazurefileconnectionstring is required for Windows Consumption, Windows Premium and Linux premium.

Supported SKU: Windows Consumption, Windows Premium and Linux premium. Unsupported SKU: Linuc Consumption, Linux Dedicated App service plan and Windows dedicated App service plan.

Hope this clarifies your question

[mike-urnun-msft]

@mwisesyk Sorry for the late reply. The information in the former is correct, and the guidance in the Automation doc is now already updated to be consistent.

We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.