Request to Review Azure OpenAI Foundry Access – Error 715-123420

振荀 孙 20 Reputation points
2026-08-20T12:07:28.3433333+00:00

Hello Microsoft Azure Team,

I am requesting a review of my Azure OpenAI Foundry access.

Subscription: Azure subscription 1 Resource group: rg-footing-lab Foundry resource: ai-footing-lab123456 Region: East Asia Model: gpt-5.6-terra Deployment name: footing-terra

When I attempted to deploy the model in Azure AI Foundry, the request was blocked with error 715-123420:

“Unusual activity detected for your account.”

The Azure subscription and Foundry resource are active, but model deployment is unavailable. The Microsoft account associated with this Azure subscription is rarely used for email, although I can still sign in and manage the subscription. Please use my preferred contact email above for further communication.

This is a legitimate personal research project, and I will comply with all Microsoft Azure OpenAI and Foundry usage policies. Please review the account and subscription access and remove the restriction if appropriate.

Thank you.

Microsoft Foundry
Microsoft Foundry

A unified Azure platform for creating and managing AI models, agents, and applications with built‑in enterprise security, monitoring, and governance

Answer accepted by question author
Karnam Venkata Rajeswari 5,255 Reputation points Microsoft External Staff Moderator
2026-08-25T22:32:49.9866667+00:00

Hello @振荀 孙 ,

Welcome to Microsoft Q&A .Thank you for reaching out to us.

The current behavior suggests that the deployment request may be failing during an earlier validation stage before the model provisioning process begins. The error message itself does not expose the exact validation reason, so confirmation requires additional backend investigation.

Possible areas that may require review include:

  • Subscription eligibility validation
  • Subscription-level authorization checks
  • Automated risk or trust validation controls
  • Model deployment access validation

Regarding the request for an RTFP review, the available information does not conclusively confirm that an RTFP restriction is present. However, the observed pattern is consistent with scenarios where additional backend validation may be required to determine whether a subscription-level condition is preventing deployments from completing.

The following checks can help rule out common deployment blockers before backend investigation.

  1. Confirming Model Availability Verify that the selected models are supported in the intended region and deployment type. Checks:
    • Confirm model availability for the selected Azure region.
    • Confirm that the selected deployment type (for example, Global Standard) is supported for the model.
  2. Validating Quota and Capacity Availability Confirm that sufficient quota is available for:
    • Subscription
    • Region
    • Selected model deployment
    Quota or capacity issues normally return more specific quota-related messages. However, validating quota helps eliminate standard deployment limitations.
  3. Verifying Resource Provider Registration Confirm that the required resource providers are registered and in a healthy state:
    • Microsoft.CognitiveServices
    • Microsoft.MachineLearningServices
    Expected status: Registered
  4. Reviewing Governance and Policy Restrictions Review Azure Policy assignments that may restrict:
    • AI model deployments
    • Allowed regions
    • Resource types
    • Deployment configurations
  5. Performing Additional Deployment Validation To determine whether the issue is limited to a specific deployment method or occurs at the service level:
    • Retry after a short interval to rule out temporary service behavior.
    • Attempt a deployment with a new deployment name to exclude deployment-specific inconsistencies.
    • Test deployment through Azure AI Foundry portal.
    • If possible, test through Azure CLI or ARM/Bicep to confirm whether the failure occurs at the service layer.

As an additional verification , please note that

For sponsored subscriptions, it may also be useful to confirm that the selected models appear under the appropriate model collection in Azure AI Foundry, as model eligibility and billing behavior can vary depending on the model source.

The following references might be helpful , please check them out

We have reached out to you on private messenger for further assistance

 

Thank you

Was this answer helpful?

1 person found this answer helpful.
0 comments

1 additional answer

Sort by: Newest
Most helpful Newest Oldest
  1. Jerald Felix 18,760 Reputation points Volunteer Moderator
    2026-08-20T16:15:32.97+00:00

    Hello 振荀 孙,

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

    This is the same underlying issue as error code 715-123420 reported elsewhere: an automated fraud and abuse detection flag on your subscription, not a quota, RBAC, or model availability problem. That is why the Foundry resource and subscription both show as active while the deployment itself is blocked instantly.

    One important thing to flag directly: the Microsoft Q&A community forum is not monitored by the account security or fraud review team, and posts here cannot trigger a manual account review. Requests addressed to "the Microsoft Azure Team" in this forum will not reach the team that can lift this restriction, since this is a peer community forum staffed by other users and moderators rather than the backend abuse detection team. To get the flag reviewed, you need to go through an actual support channel.

    Here is how to get this resolved:

    1. Open an Azure support request through the Azure portal under Help + Support, or at https://azure.microsoft.com/support/create-ticket/. Choose issue type Subscription Management and category Subscription unblock or reinstatement, since this is a risk-flag review rather than a technical bug.
    2. Include your subscription ID, resource group name, Foundry resource name, region, and the exact error code 715-123420 in the ticket description so the reviewing team can locate the flagged event without needing you to reproduce it.
    3. Confirm your account's contact and verification details are current in the Azure portal under your account profile, since infrequently used Microsoft accounts tied to a subscription can factor into this kind of automated risk scoring, and having a working verification path speeds up manual review.
    4. Avoid creating, deleting, or recreating Foundry resources while the ticket is open. Additional resource churn can reinforce the flag rather than help clear it.
    5. If you do not have a paid support plan, subscription and billing related requests, including this type of account restriction review, are generally accepted without requiring a paid technical support plan since it is not a code or configuration issue.

    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?

    1 person found this answer helpful.
    0 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.