Error 715-123420 blocks Azure OpenAI GPT-5 and Foundry model deployments despite visible quota

v p 25 Reputation points
2026-05-21T04:22:45.63+00:00

We are blocked from deploying GPT-5-family Azure OpenAI models and Azure AI Foundry / AIServices marketplace models. Deployment attempts fail immediately with:

715-123420: An error occurred. Please reach out to support for additional assistance.

This appears similar to other Microsoft Q&A reports where 715-123420 is described as a platform-level / RTFP / backend validation block rather than a normal quota, region, RBAC, or resource-configuration issue. We are requesting Microsoft moderator help to route this to the internal team that can review and unblock 715-123420 / RTFP / Fraud Protection / Security cases, or create a secure collaboration ticket if needed.

What works:

  • Normal Azure resources work. We successfully created, logged into, and deleted an Azure VM.
  • Microsoft.CognitiveServices provider is Registered.
  • Azure OpenAI resource creation works.
  • gpt-4.1-mini deployment works and API calls succeed.

Working Azure OpenAI resource:

/subscriptions/d973f401-0cab-424f-81e4-d61d854ea6a3/resourceGroups/rg-oai-smoke-20260521/providers/Microsoft.CognitiveServices/accounts/vp05210835oai28074

Working deployment:

  • Model: gpt-4.1-mini
  • Version: 2025-04-14
  • SKU: Standard
  • Region: westus
  • Result: deployment succeeds and API calls work.

Failing Azure OpenAI deployments:

  1. gpt-5.4-mini
    • Model/version: gpt-5.4-mini 2026-03-17
    • SKU tried: DataZoneStandard
    • Quota visible: OpenAI.DataZoneStandard.gpt-5.4-mini = 1000
    • Error: 715-123420
    • Correlation IDs:
      • 29134a9d-339d-46ed-a6fd-3afaf00a28f6
      • f0fd8d15-3409-404b-9f74-4d0630c93a62
  2. gpt-5-mini
    • Model/version: gpt-5-mini 2025-08-07
    • SKU tried: GlobalStandard
    • Region tried: eastus2
    • Quota visible: OpenAI.GlobalStandard.gpt-5-mini = 500
    • Error: 715-123420
    • Correlation ID:
      • f83aa64d-1ae6-464c-a997-d6b9cac93d44

Failing Azure AI Foundry / AIServices marketplace deployments:

AIServices account creation succeeds, but model deployments fail with the same 715-123420 code.

  1. Kimi-K2.6
    • Version: 2026-04-20
    • Format/provider: MoonshotAI
    • SKU: GlobalStandard
    • Region: westus2
    • Quota visible: 100
    • Error: 715-123420
    • Correlation ID:
      • 6c47c136-5acf-4319-bb14-6db9d88858e0
  2. DeepSeek-V4-Pro
    • Version: 2026-04-23
    • Format/provider: DeepSeek
    • SKU: GlobalStandard
    • Region: westus2
    • Quota visible: 1000
    • Error: 715-123420
    • Correlation ID:
      • 7838c879-0835-4a1c-a6c6-fb0e25be8146
  3. Kimi-K2.5
    • SKU: GlobalStandard
    • Region: westus2
    • Quota visible: 100
    • Error: 715-123420
    • Correlation ID:
      • 64989086-76aa-46a0-bf3b-c397753f2f8d

We also saw the same 715-123420 behavior with additional Foundry model attempts such as DeepSeek-V3.2 and gpt-oss-120b.

Why this does not look like normal configuration failure:

  • A basic Azure VM lifecycle works.
  • Azure OpenAI resource creation works.
  • gpt-4.1-mini deploys and runs successfully.
  • Quota is visible for the failing models.
  • The failures happen across multiple model families and providers.
  • The failures happen immediately during deployment.
  • Recreating resources and trying other model/region combinations did not resolve it.

Basic Azure support blocks technical ticket creation for this issue. It only allows billing, subscription management, and quota requests. This issue appears technical/backend-policy related, not billing. If this cannot be handled through Microsoft Q&A / moderator routing, please let us know whether the Developer support plan is sufficient to get this reviewed. Our current plan is to upgrade only to Developer support if required; we are not planning to purchase Standard or Professional Direct support for this issue.

Request:

Please help route this to the correct Microsoft internal team for 715-123420 / RTFP / Fraud Protection / Security review, or let us know the exact support path required. We can provide any additional non-secret identifiers needed through a secure channel. We will not share API keys, secrets, or credentials.

Foundry Models
Foundry Models

A catalog of AI models in Microsoft Foundry that you can discover, compare, and deploy using Azure’s built‑in tools for evaluation, fine‑tuning, and inference


Answer accepted by question author
Anshika Varshney 15,710 Reputation points Microsoft External Staff Moderator
2026-05-26T11:05:36.1733333+00:00

Hello @v p

Hope you are doing well.

We have received an update from the PG team that the issue has been rectified. Could you please check from your end and confirm whether the issue is now resolved?

If the updated response resolves your query, kindly consider clicking Upvote and Accept Answer so it can help others as well.

Looking forward to your response.

Thankyou!

Was this answer helpful?

1 person found this answer helpful.

1 additional answer

Sort by: Newest
  1. Alex Burlachenko 26,695 Reputation points MVP Volunteer Moderator
    2026-05-21T07:39:35.3266667+00:00

    v p hello and thx for jion us here at Q&A platform,

    I think this needs msft backend review or unblock, not another config change... this is not quota, RBAC, provider registration, or region capacity. The pattern is too specific gpt-4.1-mini deploys and runs but GPT-5-family + Foundry marketplace models fail immediately with 715-123420 across providers/regions despite visible quota.

    That strongly points to a backend risk / policy / RTFP validation block on the subscription or deployment path, not resource configuration.

    There are multiple recent Microsoft Q&A reports with the same code being treated as platform-level deployment blocking, not normal customer-side failure.

    What I would do stop deleting or recreating resources, it wont clear the flag and can make the activity pattern look worse. Open support ticket under Azure OpenAI / Azure AI Foundry Models and phrase it like “715-123420 deployment validation block, visible quota, provider registered, resource creation works, smaller model deploys, GPT-5/marketplace deployments fail across regions, providers. Please open a ticket to RTFP/Fraud Protection/Security backend review. Include all correlation IDs, subscription ID, working deployment proof, failing model, SKU or region combos, and UTC timestamps.

    If Basic support blocks technical tickets, Developer support should be enough to create a technical support case.

    rgds,

    Alex

    &

    If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal
    

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.