It's possible for multiple function apps to share the same storage account without any issues. For example, in Visual Studio you can develop multiple apps using the Azurite storage emulator. In this case, the emulator acts like a single storage account. The same storage account used by your function app can also be used to store your application data. However, this approach isn't always a good idea in a production environment.
Connect one storage account to multiple Azure functions
Hi,
We have four Azure functions(3 CosmosDB Trigger, IoTHub Trigger). Can we connect one storage account in all the functions.
2 answers
Sort by: Most helpful
-
Tulika Priyadarshini 165 Reputation points Microsoft Employee
2023-06-14T16:48:11.79+00:00 -
SnehaAgrawal-MSFT 22,166 Reputation points
2023-06-20T08:50:14.8666667+00:00 Thanks for reaching here! To add on further here-
It is recommended to use a separate storage account for each function app, especially when you have Durable Functions or Event Hub triggered functions, which both generate a high volume of storage transactions. When your application logic interacts with Azure Storage, either directly (using the Storage SDK) or through one of the storage bindings, you should use a dedicated storage account.
However, if you still want to use the same storage account for all your functions, you can do so by specifying the same storage account connection string in the application settings of all your functions.
But keep in mind that this can lead to performance issues and may not be the best practice.
Hope this helps.
Please accept as "Yes" if the answer provided is useful, so that you can help others in the community looking for remediation for similar issues.