Are File Shares created for every new Function App deployed through Visual Studio?

mark 1

Does Azure create a new File Share for every individual Function App being deployed from Visual Studio considering the Function App is created in a new resource group?
Can't we specify an existing file share in a Storage Account to be used?

1 answer

deherman-MSFT 33,141 Reputation points Microsoft Employee

2021-07-30T18:09:57.563+00:00

@mark
You should be able to choose an existing Storage Account when publishing to Azure. Check this section of the documentation for more details.

Hope this helps. Let me know if you run into issues or have further questions.

-------------------------------

Please don’t forget to "Accept the answer" and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.
Please sign in to rate this answer.
mark 1 Reputation point

2021-10-18T20:27:11.887+00:00

@deherman-MSFT
I guess I figured it out myself. My question was more specific to "file shares" getting created in a given Storage Account (SA) by Azure, for every new Function App (FA), which stores data relevant to that FA (such as logs, package zips, trace files, data-protection keys, etc.,), as I have used same SA for 3 different FA's (for learning purposes) in 3 different resource groups (RG). Hence, we see 3 file shares in the same SA (which is the issue). I believe Azure creates multiple file shares for every new FA to segregate their data. Accordingly, I am also billed for using space in the SA (on monthly basis in pay as you go model). In case I delete a FA, that's using a SA present in another RG, Azure will not delete the corresponding file share (as the SA here is in another RG) which leaves behind the file share un-deleted. I will anyways be billed for this un-deleted file share. As this directly affects monthly billing costs (if un-deleted), I was looking at ways to re-use an existing "file share" by over righting it, especially while creating a new FA (to reduce billing costs) rather than manually deleting the unwanted file share. The solution for this billing issue (as always recommended by Microsoft) is to create a new SA for a new FA and put them in a single RG and delete the RG (if not used). Right?

![141377-0-resourcegroup.png][1]![141531-1-functionappfunctions.png][2]![141444-2-filestore.png][3]![141475-3-all-fileshares-in-storageaccount.png][4]
Sign in to comment