Remove azure files dependancy from an existing linux custom container function alp on elastic premium plan

Bhanusree Annameti 20 Reputation points
2026-08-05T16:21:06.3133333+00:00

have an existing Azure Function App with this following setup:

Elastic Premium plan

Linux custom container

WEBSITES_ENABLE_APP_SERVICE_STORAGE=false

Function App integrated with VNet

Storage account private endpoints deployed in the same VNet

Only TCP 443 is allowed between the Vet, Storage account and azure functions Storage public access is disabled

AzureweblobsStorage uses private endpoints over HTTPS

The Function App was originally having an Azure Files connection enabled, so these settings exist:

WEBSITE_CONTENTAZUREFILECONNECTIONSTRING

WEBSITE_CONTENTSHARE

WEBSITE_CONTENTOVERVNET

Azure appears to recreate them after deletion.

I want to remove azure file share usage completely, there shouldn't be any usage of SMB 445 and my function app should run without any issues. What should be the process to achieve function app working perfectly? Is it allowed to make function app working without using SMB 445 in Elastic premium plan?

Azure Functions
Azure Functions

An Azure service that provides an event-driven serverless compute platform.

0 comments No comments

Answer accepted by question author
Pravallika KV 18,850 Reputation points Microsoft External Staff Moderator
2026-08-05T17:34:43.98+00:00

Hi @Bhanusree Annameti ,

Looks like you're looking to remove the Azure Files (SMB/TCP 445) dependency from an existing Linux Function App on the Elastic Premium plan, while continuing to use AzureWebJobsStorage over HTTPS via private endpoints.

AzureWebJobsStorage is required by the Azure Functions runtime for host operations. The Function App must be able to access this storage account; otherwise, the host may fail to start.

The following application settings are specifically associated with Azure Files content storage:

  • WEBSITE_CONTENTAZUREFILECONNECTIONSTRING

WEBSITE_CONTENTSHARE

WEBSITE_CONTENTOVERVNET

If these settings are present, the app is configured to use Azure Files for its content, which requires SMB connectivity.

  1. Verify AzureWebJobsStorage connectivity
    • Ensure the Function App can access the storage account over HTTPS (for example, through private endpoints if public access is restricted).
  2. Remove Azure Files content settings
    • If your goal is to eliminate the Azure Files dependency, remove the Azure Files-related application settings listed above.
    • If these settings reappear after deletion, review your deployment pipeline or Infrastructure-as-Code templates, as they may be recreating them.
  3. Validate your deployment model
    • Since you're using a Linux custom container, ensure the application content is packaged within the container image so that it does not rely on an Azure Files-mounted wwwroot.
  4. Review Function App logs
    • Check the Function App startup logs to determine whether any startup failures are related to AzureWebJobsStorage connectivity or attempts to mount Azure Files.

Is it supported to run without SMB (TCP 445)?

Yes, provided your Function App is not using Azure Files for content storage. The Azure Functions runtime still requires access to the storage account configured in AzureWebJobsStorage, but that communication occurs over HTTPS. SMB (TCP 445) is only required when Azure Files is being used to store or mount the application content.

If Azure Files settings continue to be recreated automatically, the next step would be to identify what deployment or configuration process is adding them back and update that configuration accordingly.

Hope this helps!


If the resolution was helpful, kindly take a moment to click on User's imageand click on Yes for was this answer helpful. And, if you have any further query do let us know

Was this answer helpful?

3 people found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

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