Unable to create Foundry resources error 715-123420

I think 715‑123420 means the deploy did not succeed and Azure provides no further detail, and the supported step is to sign out and back into the portal, retry once, and send the error text and the request or correlation IDs to Azure support, and the follow‑up is to open Help + support in the directory that owns the subscription and try the ticket under Subscription management, then attach the same error text and IDs if it goes through.

Hello Likitha,
Greetings! Thanks for raising this question in Q&A forum.

The error 715-123420: An error occurred. Please reach out to support for additional assistance is a generic backend failure thrown by Azure AI Foundry when the deployment creation request fails at the platform level — before it even reaches the model provisioning stage. This typically happens due to missing resource provider registrations, insufficient subscription permissions, a quota or policy block, or a transient backend issue in Foundry itself. Since the error gives no specific detail, we need to rule these out one by one.

Here are the steps to diagnose and resolve this:

Step 1: Register all required Resource Providers

Missing resource provider registrations are one of the most common causes of this error, especially on newer subscriptions. Go to:

Azure Portal → Subscriptions → Your Subscription → Resource Providers

Search for each of the following and confirm they are in Registered state:

• Microsoft.MachineLearningServices
• Microsoft.CognitiveServices
• Microsoft.Storage
• Microsoft.KeyVault
• Microsoft.ContainerRegistry

If any show as NotRegistered, click on them and hit Register. Wait for each to fully complete before retrying your deployment.

Step 2: Verify your role and permissions

Creating deployments in Foundry requires at minimum a Contributor role on the subscription or resource group. A Reader role will fail silently with a generic error exactly like this one. Check your access by going to:

Azure Portal → Your Resource Group → Access Control (IAM) → View My Access

If you only have Reader access, ask your Azure administrator to elevate it to Contributor or Owner and then retry.

Step 3: Check if an Azure Policy is blocking the deployment

Some organizations apply subscription-level Azure Policies that restrict resource creation by type, region, SKU, or naming convention. Go to:

Azure Portal → Search "Policy" → Click Compliance → Look for any Non-compliant policies tied to your subscription or resource group

If a blocking policy exists, work with your admin to either request an exemption or adjust your deployment settings to comply.

Step 4: Try deploying via Azure CLI for a clearer error message

The portal often hides the real failure behind a generic message. The CLI returns the full error detail which will point you directly to the root cause:

az ml workspace create \
  --name <your-workspace-name> \
  --resource-group <your-resource-group> \
  --location eastus

Copy the exact CLI error output — it will usually tell you precisely what is blocked, whether that is quota, policy, a missing provider, or something else.

Step 5: Try a different Azure region

If the issue is a transient backend problem specific to your current region, switching regions can unblock you immediately. Try creating a new Foundry project and deployment in East US, West Europe, or Sweden Central and see if the same error appears.

Step 6: Open an Azure Support Ticket

Since the error message itself is directing you to contact support, and given that error code 715-123420 is a platform-level failure you cannot investigate further on your own, raising a formal ticket is the correct next step. Go to:

Azure Portal → Help + Support → New Support Request and fill in:

• Issue type: Technical
• Service: Azure AI Foundry
• Problem type: Creating or Managing Resources
• Problem subtype: Deployment creation failure
• Severity: B (Moderate)

In the description include:

• Exact error code: 715-123420
• The model or resource type you were trying to deploy
• Your subscription ID, resource group name, and target region
• A screenshot of the error from the Foundry portal
• Any steps you have already tried from this list

The Azure support team can pull backend diagnostic logs for this specific error code and identify the exact failure point quickly.

If this answer helps you kindly accept the answer which will help others who have similar questions.

Best Regards,

Jerald Felix.