Thank you for opening this issue, we will look into it.

Hi there,

I am experiencing a very similar issue. For some reason, the az functionapp commands in Azure DevOps release pipelines have stopped working for all my existing Azure Function Apps and are now throwing the error "ERROR: (ResourceNotFound) The Resource 'Microsoft.Web/serverFarms/SouthCentralUSPlan'".

If I go to Azure Function App -> Automation -> Export template, I don't see any parameters being referenced to "/providers/Microsoft.Web/serverfarms/SouthCentralUSPlan" as shown in the picture below -

Does anyone know how to solve that issue?

Thank you for any advice that would help fix the issue!

@yonzhan - any way to get someone to take a quick look at this? It's definitely a bug. Thank you.

I'm facing this same issue today. I tried eastus, westus and westus2 and no luck.

same here for us region west europe

why have you removed bug and so on? do you think it is fixed?

why do you not answer?

@yonzhan @microsoft-github-policy-service

We have been experiencing this error continuously for the past 3 weeks in the WestEurope region.

We use the az functionapp create command with the --consumption-plan-location parameter to create a new function app. The command executes successfully.

Afterwards, we try to update the settings using the command az functionapp config appsettings set, but we receive the error message:
"The Resource 'Microsoft.Web/serverFarms/WestEuropePlan' under resource group 'rg-name'" was not found.

When we check the resource group, the function app is listed there. However, the consumption function app plan is not initially visible. It only becomes available after approximately 10 minutes. Once the plan is displayed, the commands can be executed again without any issues.

When I check the activity log of the consumption plan, three operations are displayed. The second update operation has the status "Failed." In the summary for this operation, I see the error message: "The parameter SKU has an invalid value."

@yonzhan @evelyn-ys @calvinhzy @zhoxing-ms @amamounelsayed @kaibocai @shreyas-gopalakrishna @kamperiadis

This issue has been open for six months, and so far, no team member has reviewed it. In the meantime, we have found a workaround to bypass the problem. For anyone else encountering this error, here’s a potential temporary solution that might help:

1. First, create a consumption function app plan for the desired region by calling the Azure REST API through the Azure CLI. The command az functionapp plan create cannot be used here because Y1 is not allowed as an SKU.

$SkuName = "Y1"
$Location = "<your desired location>" # e.g. westeurope or southcentralus
$SubscriptionId = "<your subcription id>"
$ResourceGroup = "<your resource group name>" 
$ConsumptionPlanName = "<your consumption plan name>" # e.g. WestEuropePlan
 
$content = [PSCustomObject]@{
    type = "Microsoft.Web/serverfarms"
    kind = "functionapp"
    location = $Location
    sku = [PSCustomObject]@{
        name = $SkuName 
    }
}

ConvertTo-Json $content -depth 10 | Out-File ".\manifest.json"

$uri = "https://management.azure.com/subscriptions/$($SubscriptionId)/resourceGroups/$($ResourceGroup)/providers/Microsoft.Web/serverfarms/$($ConsumptionPlanName)?api-version=2024-04-01"

az rest `
--method put `
    --headers "Content-Type=application/json" `
    --uri $uri `
    --body "@manifest.json"

Remove-Item "./manifest.json"

2. Next, create the function app as usual with the command az functionapp create, using the --consumption-plan-location parameter. Since we already created the consumption plan for the desired region in the previous step, no new consumption plan will be generated; instead, the existing plan will be used. There is also a --plan parameter; however, a consumption plan cannot be specified with it, as doing so will return the error: "There was a conflict. AlwaysOn cannot be set for this site as the plan does not allow it."

az functionapp create `
    --name $Name `
    --storage-account $StorageAccount `
    --consumption-plan-location $Location `
    --runtime dotnet-isolated `
    --resource-group $ResourceGroup `
    --functions-version $AppVersion `
    --runtime-version $RuntimeVersion 

We hope this helps others until the issue is addressed.