Hi,
I think the docs about azure functions are hard to follow.
While there is a a lot of flavours, as the service evolves its hard to follow the changes, best practices and spot why things break.
We have functions apps deployed to webapp for some time now, and in recent deployments we struggle to see why deployment fails.
Hi, I think the docs about azure functions are hard to follow. While there is a a lot of flavours, as the service evolves its hard to follow the changes, best practices and spot why things break. We have functions apps deployed to webapp for some time now, and in recent deployments we struggle to see why deployment fails.
Here is some exmples, https://learn.microsoft.com/en-us/azure/azure-functions/functions-best-practices?tabs=csharp#storage-connection-settings we can read: _On your first deployment using an ARM template, don't include WEBSITECONTENTSHARE, which is generated for you. or in here, https://github.com/Azure/azure-quickstart-templates/blob/master/quickstarts/microsoft.web/function-http-trigger/main.bicep is not included. Again in https://learn.microsoft.com/en-us/azure/azure-functions/functions-app-settings#website_contentshare for more detailed info we can read that for this scenario: _When you don't set a WEBSITECONTENTSHARE value for the main function app or any apps in slots, unique share values are generated for you. This is the recommended approach for an ARM template deployment.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.