This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(57.599999999999994, 59%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDO%3C/text%3E%3C/svg%3E)
container apps will no longer deploy after registering microsoft.app resource provider and de-registering, once realising that dapr sidecar is not supported through the microsoft.app namespace . deploying through the azure portal will not work with the hello world sample image with the following error.
type : Microsoft.Web/kubeEnvironments
"details": [
{
"code": "InternalServerError",
"message": "There was an unexpected InternalServerError. Please try again later. x-ms-correlation-request-id: 45e7a218-7962-428d-a7e9-9f08a682f66c"
}
anyone experience this and resolved?
An Azure service that provides customers with a serverless container experience.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(166.4, 55.00000000000001%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJR%3C/text%3E%3C/svg%3E)
Also encountering this issue when deploying the following
resource environment 'Microsoft.Web/kubeEnvironments@2021-03-01' = {
name: environmentName
kind: 'containerenvironment'
location: location
tags: tags
properties: {
type: 'managed'
internalLoadBalancerEnabled: false
appLogsConfiguration: {
destination: 'log-analytics'
logAnalyticsConfiguration: {
customerId: workspace.properties.customerId
sharedKey: listKeys(workspace.id, workspace.apiVersion).primarySharedKey
}
}
containerAppsConfiguration: {
daprAIInstrumentationKey: appInsights.properties.InstrumentationKey
}
}
}
I think the answer is migrating to Microsoft.App/managedEnvironments@2022-01-01-preview
Looks like the issue you face is a temporary issue in the region tried or specific to a region. You can just try the deployment again at the same region or a different region. I have seen these kind of user complaints in past also and fixed by Microsoft in the backend
--please don't forget to upvote and Accept as answer if the reply is helpful--