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: 40a8cf827bda6608812193d637b48c8e

TraceID: 40a8cf827bda6608812193d637b48c8e

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

Details of error:

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

[paulyuk]

Please see this issue with the likely cause and solution registering Microsoft.app.
The exception you ran into was likely due to Microsoft.App not being registered on your Azure subscription. Ensure that the Microsoft.App resource provider is enabled for your subscription by [following these instructions](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-providers-and-types#register-resource-provider).

[pawelkaliniakit]

Paul Yuknewicz (@paulyuk) I confirm - the same as here:
Azure-Samples/functions-quickstart-typescript-azd#9

InternalServerError is not poper error for the situation - maybe 409 - Conflict would be better one.
Anyway - error message does not say anything meaningful.

[nzthiago]

pawelkaliniakit - is the error still reproducing in that you don't see the real error message (related to Microsoft.App not being registered) in the portal? We rolled out a fix for the actual error message to flow through instead of InternalServerError, so if it's still happening let us know so we can find out if it's an edge case we still need to fix.