Error code 715-123420 with the message:
{
"code": "715-123420",
"message": "An error occurred. Please reach out to support for additional assistance."
}
is not listed in the documented Azure Resource Manager deployment error codes and is not covered by the provided troubleshooting guidance for common deployment errors.
The message explicitly instructs to contact support, and the behavior persists across a new resource group and a fresh deployment, which aligns with scenarios where manual review or a platform-side block (such as risk or fraud controls) must be cleared by Microsoft.
The only actionable next step supported by the context is to:
- Collect full deployment details and error information:
- In the Azure portal, go to the target Resource group.
- Open Activity log and locate the failed deployment operation, then open the error details to capture the full error payload and correlation IDs.
- Also check Settings → Deployments on the resource group and open Error details for the failed deployment to confirm there are no additional ARM error codes (such as
DeploymentFailed, BadRequest, or quota/policy errors) accompanying 715-123420.
- Open a support request with Microsoft Azure support and provide:
- The error code
715-123420 and full error JSON.
- Subscription ID, region, resource type, and model (GPT‑4.1 mini) being deployed.
- Approximate time of failure and the correlation IDs from the Activity log / deployment details.
If any standard ARM error code appears in the deployment details (for example, AuthorizationFailed, RequestDisallowedByPolicy, ResourceQuotaExceeded, or SkuNotAvailable), follow the specific mitigation steps for that code as documented, but the presence of 715-123420 and the directive to contact support indicates that resolution ultimately requires direct intervention from Microsoft.
References: