Deployments are failing with InternalServerError

[pawelkaliniakit]

I follow the guideline in README.md in order to deploy resources but the deployment fails on:

ERROR: error executing step command 'provision': deployment failed: error deploying infrastructure: deploying to subscription:

Deployment Error Details:
InternalServerError: There was an unexpected InternalServerError.  Please try again later.  x-ms-correlation-request-id: 86869c2a4397865f76b478f51ea3d4b3

sample deployment:
https://portal.azure.com/#view/HubsExtension/DeploymentDetailsBlade/~/overview/id/%2Fsubscriptions%2Fafab7bca-9723-4b94-849a-5c371fce9c36%2Fproviders%2FMicrosoft.Resources%2Fdeployments%2Fitdoesfail123456butwhy-1739889184

Details of error
{
"status": "Failed",
"error": {
"code": "InternalServerError",
"message": "There was an unexpected InternalServerError. Please try again later. x-ms-correlation-request-id: 86869c2a4397865f76b478f51ea3d4b3"
}
}

The error denotes that problem is on Auzre site.

[Yvand]

Too bad the error does not contain more details. I see it failed fast (3 secs).
As a test, are you able to create a flex func app from the portal in this resource group?
And for comparison, can you check if you get the same error using this azd template?

[pawelkaliniakit]

As a test, are you able to create a flex func app from the portal in this resource group?
that was good idea since it revealted that flex function cannot be done for the free trial subscription that I have ( initial 200 USD for one month), see:

Bezpłatna subskrypcja wersji próbnej nie jest obsługiwana dla Zużycie elastyczne. Wybierz inną subskrypcję.

means:

Free trial subscription is not supported for Flexible Consumption. Please select another subscription.

What means that now I understand what happened.
Can we raise some ticket to Azure to change message to something meaningful ? If yes then how?

[Yvand]

I agree the error should be more accurate when deploying via the API.
Sorry I cannot help you about opening a ticket, but you should be able to do it from the Azure portal directly.

[paulyuk]

@nzthiago fyi

[nzthiago]

As I mentioned on the related issue, we rolled out a fix on or right after February so that the actual error message flows through instead of InternalServerError. If it's still happening let us know so we can find out if it's an edge case we still need to fix.