Azure OpenAI deployment blocked by 715-123420 on Microsoft for Startups subscription - request RTFP/backend review

Micro Extract 0 Reputation points
2026-08-27T08:26:48.49+00:00

We are experiencing Azure OpenAI deployment error 715-123420 on a Microsoft for Startups subscription.

The issue persists after Microsoft's recommended waiting period and one controlled retry more than 24 hours later.

Environment

  • Service: Azure OpenAI / Azure AI Foundry
  • Region: Southeast Asia
  • Model: gpt-5-mini
  • Version: 2025-08-07
  • Deployment type: GlobalStandard
  • Requested capacity: 1
  • Verified available capacity before deployment: 500

Validation already completed

  • Model is available to the subscription.
  • Live model capacity is available.
  • GitHub OIDC authentication succeeds.
  • Azure subscription, resource group and Azure AI account boundaries are verified.
  • Required RBAC is present.
  • Deployment-name conflict checks pass.
  • This is not an Azure quota failure.

First failure

2026-08-26T02:33:02Z

Error: 715-123420: Our system has detected this request as unusual activity for your account.

Controlled retry after >24 hours

2026-08-27T07:07:46Z

Same error: 715-123420

No model deployment was created on either attempt and automated deployment has been disabled again.

Microsoft Q&A guidance for this error indicates that 715-123420 can represent an RTFP/fraud-risk signal requiring internal Microsoft review.

Request

Please escalate this issue to the appropriate RTFP / Fraud Protection / Trust & Risk / Azure OpenAI Product Group backend team for review and adjustment if this is a false positive.

This is not a quota increase request.

We will not perform additional deployment attempts until Microsoft confirms the backend analysis/adjustments are complete.We are experiencing Azure OpenAI deployment error 715-123420 on a Microsoft for Startups subscription.

The issue persists after Microsoft's recommended waiting period and one controlled retry more than 24 hours later.

Environment

  • Service: Azure OpenAI / Azure AI Foundry
  • Region: Southeast Asia
  • Model: gpt-5-mini
  • Version: 2025-08-07
  • Deployment type: GlobalStandard
  • Requested capacity: 1
  • Verified available capacity before deployment: 500

Validation already completed

  • Model is available to the subscription.
  • Live model capacity is available.
  • GitHub OIDC authentication succeeds.
  • Azure subscription, resource group and Azure AI account boundaries are verified.
  • Required RBAC is present.
  • Deployment-name conflict checks pass.
  • This is not an Azure quota failure.

First failure

2026-08-26T02:33:02Z

Error:
715-123420: Our system has detected this request as unusual activity for your account.

Controlled retry after >24 hours

2026-08-27T07:07:46Z

Same error:
715-123420

No model deployment was created on either attempt and automated deployment has been disabled again.

Microsoft Q&A guidance for this error indicates that 715-123420 can represent an RTFP/fraud-risk signal requiring internal Microsoft review.

Request

Please escalate this issue to the appropriate RTFP / Fraud Protection / Trust & Risk / Azure OpenAI Product Group backend team for review and adjustment if this is a false positive.

This is not a quota increase request.

We will not perform additional deployment attempts until Microsoft confirms the backend analysis/adjustments are complete.

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


1 answer

Sort by: Newest
  1. Jerald Felix 18,760 Reputation points Volunteer Moderator
    2026-08-27T16:00:43.6366667+00:00

    Hello Micro Extract,

    Greetings! Thanks for raising this question in the Q&A forum.

    Error 715-123420 is not a quota, RBAC, or capacity issue even though it surfaces at deployment time. It is a Risk and Trust Fraud Protection (RTFP) signal generated by Azure's backend fraud detection system. The platform has flagged the subscription's deployment activity as unusual, and this is a backend hold rather than something misconfigured on your side. That matches everything you have already validated: available capacity, RBAC, OIDC auth, and boundaries all being correct is expected, because none of those factors control whether RTFP flags a subscription.

    This type of signal is common on newly created or recently upgraded subscriptions, including Microsoft for Startups enrollments, when there is a sudden change in deployment pattern, model type, or requested capacity that looks anomalous to the fraud detection model, even though it is legitimate usage. It cannot be resolved by retrying, waiting longer, changing regions, or recreating the resource, since the block is tied to the subscription's risk profile rather than the specific deployment call. Repeated retries can sometimes extend the review period rather than clear it, so you were right to hold off on further attempts.

    Here is how to get this properly reviewed.

    Do not retry deployment further. Continued attempts do not clear an RTFP hold and can add noise to the backend review.

    Open an Azure Support ticket under the correct category. In the Azure Portal, go to Help + support > New support request, and select:

    • Issue type: Subscription Management (not Technical, since this is not a service outage or configuration issue)
      • Problem type: Billing and Subscription Fraud or Subscription and account management, whichever is offered, referencing the RTFP flag
      Include full identifying detail in the ticket so the backend reviewer can locate the exact flagged events:
      - Subscription ID
      
         - Azure AI Foundry resource/account name and resource group
      
            - Region: Southeast Asia
      
               - Model and version: `gpt-5-mini`, version `2025-08-07`
      
                  - Deployment type: GlobalStandard
      
                     - Timestamps of both failed attempts: `2026-08-26T02:33:02Z` and `2026-08-27T07:07:46Z`
      
                        - The exact error code `715-123420` and message text
      
                           - Any correlation ID, request ID, or trace ID returned in the deployment response, if you captured one
      
                           **Note your support plan.** If this is a Basic support plan, Subscription Management and billing-related requests are still accepted even without a paid technical support plan, so you should be able to file this without upgrading.
      
                           **Ask explicitly for RTFP/backend review.** State clearly in the ticket description that this is believed to be a false-positive fraud detection flag, not a quota request, so it routes to the correct backend team rather than a generic support queue.
      
                           **Avoid deleting or recreating the Azure AI Foundry resource** while the ticket is open, since resource churn can look like further anomalous activity and complicate the review.
      

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

    Best Regards,

    Jerald Felix

    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.