Hello @Hariprasad - Thanks for reaching out & posting on the MS Q&A channel!
I suspect the issue is to do with setting the WEBSITE_CONTENTSHARE
. With an automatic approach via ARM, the recommended approach is to not set the WEBSITE_CONTENTSHARE
app setting as it'll be auto-generated during ARM deployment. The following considerations are noted for ARM deployments:
On the other hand, as stated above, if your storage account is in a VNET, you should then specify a value for the WEBSITE_CONTENTSHARE
setting.
Depending on your exact scenario, here are some working samples (maintained by MS) that you can use to enhance the one that you're working on: https://github.com/Azure-Samples/function-app-arm-templates#arm-templates-for-function-app-deployment
For the scenario where the Storage Account is secured by the VNET, it looks like the file share resource is created explicitly:
{
"type": "Microsoft.Storage/storageAccounts/fileServices/shares",
"apiVersion": "2022-05-01",
"name": "[format('{0}/default/{1}', parameters('functionStorageAccountName'), variables('functionContentShareName'))]",
"dependsOn": [
"[resourceId('Microsoft.Storage/storageAccounts', parameters('functionStorageAccountName'))]"
]
}
I hope this helps, and I look forward to your reply ;)