An Azure service that provides an event-driven serverless compute platform.
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.
- Verify
AzureWebJobsStorageconnectivity- Ensure the Function App can access the storage account over HTTPS (for example, through private endpoints if public access is restricted).
- 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.
- 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.
- 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
- Review Function App logs
- Check the Function App startup logs to determine whether any startup failures are related to
AzureWebJobsStorageconnectivity or attempts to mount Azure Files.
- Check the Function App startup logs to determine whether any startup failures are related to
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 and click on Yes for was this answer helpful. And, if you have any further query do let us know