az functionapp create returns error when trying to create a dotnet-isolated functionapp

Related command

az functionapp create

Describe the bug When using the command below to create an isolated .NET 5 function app environment the az functionapp create returns immediately with the error message (line breaks added to make it easier to read the message)

Runtime dotnet-isolated not supported for os linux. Supported runtimes for os linux are: 
['dotnet', 'dotnet', 'node', 'node', 'node', 'python', 'python', 'python', 'java', 'java', 'powershell', 'powershell', 'custom']. 
Run 'az functionapp list-runtimes' for more details on supported runtimes.

Please note the duplicate supported runtimes displayed as well.

To Reproduce

1. Have the Azure CLI version 2.36.0
2. Create required resources for the command to run (see the documentation from Azure Functions dotnet worker repo)
3. Execute the following command and replace related <> values

az functionapp create `
  --resource-group <Resource group> `
  --name <Function name> `
  --storage-account "<Storage account>" `
  --consumption-plan-location westeurope `
  --functions-version 3 `
  --os-type Linux `
  --runtime dotnet-isolated `
  --runtime-version 5.0 `
  --app-insights-key <App-insights key> `
  --assign-identity

Expected behavior

The dotnet-isolated should be allowed as a runtime since it is supported by Azure Functions.

Environment summary

• Azure CLI version 2.36.0

  • az version
    {
      "azure-cli": "2.36.0",
      "azure-cli-core": "2.36.0",
      "azure-cli-telemetry": "1.0.6",
      "extensions": {
        "aks-preview": "0.5.48",
        "application-insights": "0.1.14",
        "log-analytics-solution": "0.1.1",
        "peering": "0.2.1"
      }
    }
    

  • installed using MSI
• Powershell 7.2.3

Additional context

• This identical command works in earlier versions of Azure CLI (2.31.0), but have for some reason stopped working and gives us the specified error.
• The error is the same if you try to execute it with os-type Windows
• The Azure Function dotnet documentation states that this is correct command.
• For some reason it isn’t possible to deploy isolated .NET 6 using 2.31.0 but that’s another story (and generally a problem with .NET 6 and out of scope of this issue).

[navba-MSFT]

@dozer75 I have reached out to the Product owners with all the details. I will update this thread once I hear back from them.

[navba-MSFT]

@dozer75 We had reached out to the Product Owners in the background and they are aware of this issue. Hence just to unblock you the workaround was shared. We hear you and understand your concerns. We sincerely apologize for the inconvenience caused.

We’re discussing whether we truly want to make a change to our guidance as opposed to working with the CLI team to have the bug fixed. We’ll provide an update here soon

Reference: https://github.com/Azure/azure-functions-dotnet-worker/pull/894

Also there’s an issue tracking it https://github.com/Azure/azure-functions-dotnet-worker/issues/857 which has been created. There is no ETA on when it will be fixed, but it seems the Stacks API fix is blocked on some other host issue.