Open soderholmd opened 1 month ago
@soderholmd can you register the microsoft.insights
RP on the Management subscription and try again for me?
@jtracey93 just checked and it is already registered on all subscriptions apart from Sandbox.
@jtracey93 tried redeploying after confirming resource providers enabled. Same result for five of the diag rules:
{
"code": "DeploymentFailed",
"target": "/providers/Microsoft.Resources/deployments/NoMarketplace-20240723163706",
"message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.",
"details": [
{
"code": "ResourceDeploymentFailure",
"target": "/providers/Microsoft.Management/managementGroups/ds-corp/providers/Microsoft.Resources/deployments/ds-corpalz-DiagSettingsMGs-uksouth-446adbf1-56d3-5ed9-8a54-4d77d",
"message": "The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'."
},
{
"code": "ResourceDeploymentFailure",
"target": "/providers/Microsoft.Management/managementGroups/ds-landingzones/providers/Microsoft.Resources/deployments/ds-landingzonesalz-DiagSettingsMGs-uksouth-446adbf1-56d3-5ed9-8a",
"message": "The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'."
},
{
"code": "ResourceDeploymentFailure",
"target": "/providers/Microsoft.Management/managementGroups/ds-platform/providers/Microsoft.Resources/deployments/ds-platformalz-DiagSettingsMGs-uksouth-446adbf1-56d3-5ed9-8a54-4",
"message": "The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'."
},
{
"code": "ResourceDeploymentFailure",
"target": "/providers/Microsoft.Management/managementGroups/ds-decommissioned/providers/Microsoft.Resources/deployments/ds-decommissionedalz-DiagSettingsMGs-uksouth-446adbf1-56d3-5ed9-",
"message": "The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'."
},
{
"code": "ResourceDeploymentFailure",
"target": "/providers/Microsoft.Management/managementGroups/ds/providers/Microsoft.Resources/deployments/dsalz-DiagSettingsMGs-uksouth-446adbf1-56d3-5ed9-8a54-4d77dd9c17",
"message": "The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'."
}
]
}
Same 'invalid authentication token' error.
@soderholmd are you able to re-test this today?
Also can you confirm the other Management Group Diagnostic Settings deployments are completing successfully?
I see in the output above only these MGs are failing:
@jtracey93 worked on the third attempt! First time ten failed, second time five failed, third time no failures.
interesting, i think there may be a platform issue. I will investigate further
Using the ALZ deployment wizard in a newly provisioned tenant. 10 of the diag settings failed to deploy with error:
All other resources deployed successfully but overall ALZ deployment job failed with error below.
Steps to reproduce
Screenshots