Hello team. I get the error below when creating new azure migrate project:
{
"status": "Failed",
"error": {
"code": "DeploymentFailed",
"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": "Conflict",
"message": "{\r\n \"status\": \"Failed\",\r\n \"error\": {\r\n \"code\": \"ResourceDeploymentFailure\",\r\n \"message\": \"The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'.\",\r\n \"details\": [\r\n {\r\n \"code\": \"InternalServerError\",\r\n \"message\": \"An error occurred.\",\r\n \"details\": []\r\n }\r\n ]\r\n }\r\n}"
}
]
}
}
{
"status": "Failed",
"error": {
"code": "InternalServerError",
"message": "An error occurred.",
"details": []
}
}
After reviewing all Azure Policy assignments at both the subscription and resource‑group levels, I haven’t found any policy that would block this deployment. For context, I successfully created an Azure Migrate project two days ago and then deleted it, but since yesterday every attempt to provision a new project has been failing during the private‑endpoint creation phase. Could we take a closer look together to identify any residual artifacts or conflicts that might be preventing the deployment?
Azure Migrate
1 answer
Sort by: Most helpful
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more