Closed jansenbe closed 5 years ago
Might be related to different parameter needs for consumption plan vs general plan. See https://docs.microsoft.com/en-us/azure/azure-functions/functions-infrastructure-as-code and https://blog.siliconvalve.com/2018/05/03/multi-environment-deployments-for-compiled-c-azure-functions-with-vsts-release-management/
Root cause found: when you provide an already taken name for the storage account this error happens. Fix: add more validation in the script before executing
The needed checks are implemented. Closing this issue
There was one more reason for this issue: if you've used a character that's forbidden in a storage account name inside the function app name (e.g. uppercase character) then the WEBSITE_CONTENTSHARE property got populated with an invalid value. This will be fixed in the provisioning script.
See https://github.com/SharePoint/sp-dev-modernization/issues/27.