Azure Functions Timer Trigger does not work with Premium File Shares Storage Account type

Haani Jessin 20 Reputation points
2024-04-21T13:02:27.0733333+00:00

Function Plan: EP1

Storage Account: Premium file share

I have a timer trigger function which works as expected in testing when using a General Purpose V2 Storage Account type but I get the following error when deploying the function to an environment with the plan config mentioned above:

Host instance 'xxx' failed to acquire host lock lease: Azure.Core: Name or service not known (xxxx.blob.core.windows.net:443). System.Net.Http: Name or service not known (xxxx.blob.core.windows.net:443). System.Net.Sockets: Name or service not known.

I was initially facing issues with the function app in general being super buggy in the portal such as several pages not loading and giving an "Encountered an error (InternalServerError) from host runtime." but I was able to fix this by setting AzureWebJobsSecretStorageType=files based on the documentation here. Before this, the function keys page would give the InternalServerError and didn't show the master and default keys but they were generated after changing the storage type setting. However, the timer trigger still does not work and I believe it may have something to do with the storage account type as the file share account type does not have a blob.core.windows.net endpoint.

Is it simply not possible to have a timer trigger with this type of storage account and I have to switch to StorageV2 or am I missing something?

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
4,452 questions
Azure Storage Accounts
Azure Storage Accounts
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
2,793 questions
{count} votes