"az functionapp create" failing to create App Service Plan in select regions

### Describe the bug

Using the Azure CLI to create a new consumption plan function in South Central US fails to create the associated app service plan, but the function is created successfully. Using the Azure Portal to create the function in SCUS (point and click, not cloud shell) works as expected and creates the Y1 plan.

Using the Azure CLI and South Central US location, after creating the consumption plan function, an app service plan name is shown:


Clicking on the app service plan name produces the following 404 error:


Using "az functionapp show" against the newly created function throws an error:


Using the Azure CLI and East US location, the function and its app service plan are created successfully and the app service plan can be viewed in the portal.


### Related command

Repro Steps

```
$someRandom = "PUT SOMETHING SHORT & RANDOM IN HERE"
$location = "southcentralus"
$resourceGroupName = "FunctionResourceGroup"
$storageName = "funcstorage$someRandom"
$functionAppName = "funcapp$someRandom"

az group create --name $resourceGroupName --location $location
az storage account create --name $storageName --location $location --resource-group $resourceGroupName --sku Standard_LRS
az functionapp create --name $functionAppName --storage-account $storageName --consumption-plan-location $location --resource-group $resourceGroupName --functions-version 4

-- this following line will fail in SCUS
az functionapp show --name $functionAppName --resource-group $resourceGroupName
```


### Errors

Clicking on the app service plan name produces the following 404 error:


Using "az functionapp show" against the newly created function throws an error:


### Issue script & Debug output

Can provide on request. It's big and did not show any errors.

### Expected behavior

"az functionapp create", when using the --consumption-plan-location argument, should create a Y1 app service plan that can be viewed in the portal. The "az functionapp show" command should be able to retrieve details of the function.

### Environment Summary


Same incorrect behavior seen when using the Azure Portal Cloud Shell & PowerShell.

### Additional context

_No response_