Not able to create function app via az cli

Question

A few days ago, our pipeline started to report errors.

We attempted to upgrade the version number of az cli from 2.44.1 to 2.71.0.

At the same time, we changed the command az functionapp create from

$script:webApp = az functionapp create --resource-group $targetResourceGroupName --plan $relevantAppServicePlanName --name $fqServiceName --os-type Linux --storage-account $fnAppStorageAccount --runtime dotnet-isolated --runtime-version 8 --functions-version 4 2>$warning

az functionapp config set --resource-group $targetResourceGroupName --name $fqServiceName --linux-fx-version '"DOTNET-ISOLATED|8.0"'

to

$script:webApp = az functionapp create --resource-group $targetResourceGroupName --plan $relevantAppServicePlanName --name $fqServiceName --os-type Linux --storage-account $fnAppStorageAccount --runtime dotnet-isolated --runtime-version 8 --functions-version 4 --linux-fx-version "DOTNET-ISOLATED|8.0" 2>$warning

However, after testing, the function app still cannot be created, and both the warning and webApp are null values.

Please help. Thank you!

Answer 1

Hello Vincent,

Welcome to Q&A, Looks like the problem could be coming from two places: the linux-fx-version parameter or your storage account setup (I had similar issues before lets see).

• To fix the linux-fx-version try to escaping or quoting it properly: Use something like this: --linux-fx-version '"DOTNET-ISOLATED|8.0"'
• Checking Your Storage Account: I’ve seen cases where the issue was caused by the file service not being enabled on the storage account, which is absolutely essential for Azure Functions. In those situations, enabling the file service immediately resolved the problem. Additionally, there have been cases where the storage account was inaccessible due to network restrictions or firewall rules, leading to similar errors. Making sure your storage account is in the same region as your function app and verifying permissions can help avoid this. And of course, if the storage account is not a general-purpose account, that's another common pitfall. Specialized accounts like BlobStorage or DataLake often cause issues because Azure Functions requires general-purpose accounts.
• Debugging the Command: If all else fails, use the --debug flag when running your Azure CLI commands

References:

• https://learn.microsoft.com/en-us/cli/azure/functionapp?view=azure-cli-latest#az-functionapp-create
• https://learn.microsoft.com/en-us/azure/azure-functions/functions-app-settings#linuxfxversion
• https://learn.microsoft.com/en-us/azure/azure-functions/storage-considerations?tabs=azure-cli

If the information helped address your question, please Accept the answer.

Luis