Microsoft Foundry deployments blocked with error 715-123420 – Basic support plan

Farhaan Tariq 0 Reputation points
2026-11-03T21:28:18.3266667+00:00

I am unable to deploy embedding models in Microsoft Foundry because every deployment attempt returns this error:

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

Affected models:

text-embedding-3-small

text-embedding-3-large

text-embedding-ada-002

I have tried deploying in East US and East US 2, and also created another Foundry resource under the same Azure subscription. The issue persists.

Other models, including GPT models, deploy successfully under the same subscription.

My Activity Log confirms failed deployment operations with error code 715-123420.

I am using the Basic Azure support plan, which does not allow me to submit a technical support request.

Could a Microsoft moderator please help escalate this issue to the appropriate backend team for review of the unusual-activity restriction?

I can provide my subscription ID, resource details, deployment timestamps, and correlation IDs through a private message.

Thank you.

Azure OpenAI in Foundry Models
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Farhaan Tariq 0 Reputation points
    2026-11-03T21:36:42.34+00:00

    Update: Azure Basic support request automatically closed – requesting Microsoft moderator assistance

    I followed the recommendation to submit an Azure Subscription Management support request.

    However, Microsoft automatically closed the request because the issue requires technical support, which is not included in my Basic support plan.

    Support request number: 2611030040009458

    The underlying issue remains unresolved. My Microsoft Foundry embedding-model deployments continue to fail with error 715-123420:

    "Our system has detected this request as unusual activity for your account."

    This affects text-embedding-3-small, text-embedding-3-large, and text-embedding-ada-002 across East US and East US 2, including a second Foundry resource under the same subscription. Other GPT model deployments work successfully.

    Could a Microsoft moderator please assist with escalating this issue to the appropriate backend security/fraud-protection team for investigation?

    I can provide my subscription ID, Foundry resource ID, timestamps, and Activity Log correlation IDs through a private message.

    I am currently learning and exploring with Azure AI and Microsoft Foundry as part of my AI and machine learning. I am not using Azure for a commercial use. I am using it for learning, hands-on practice, and developing practical AI skills. I would appreciate assistance because I cannot afford to purchase a paid support plan simply to resolve this issue.

    Thank you.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-11-03T21:29:27.02+00:00

    Submit this as an Azure Subscription management request rather than a Technical request, because matched cases of error 715-123420 required an account-level review and backend release rather than changes to the model, region, or Foundry resource.^1^

    Submit the request with Basic support

    Azure provides subscription-management support without requiring a paid technical support plan.^2^

    1. In the Azure portal, select ? in the global header and describe the problem.
    2. Select Create a support request. If an assistant experience appears, switch to the classic support-request workflow if that option is offered.
    3. Select:
      • Issue type: Subscription management
      • Subscription: The subscription receiving 715-123420
      • The closest available account/subscription problem type
    4. In Problem details, request an account-level review of the Microsoft Foundry unusual-activity restriction. Do not classify it as a quota request.
    5. Include:
      • Full error code and message
      • Affected models
      • Foundry resource name and resource ID
      • Azure region
      • Exact UTC timestamps
      • Activity Log correlation IDs and request IDs
      • Confirmation that GPT deployments succeed while embedding deployments fail
      • Confirmation that changing regions and creating another resource in the same subscription did not resolve it
    6. Complete the contact information and create the request.

    The account must have Owner, Contributor, Support Request Contributor, or equivalent Microsoft.Support/* permission at subscription scope to open the request.^2^

    Suggested ticket text:

    Microsoft Foundry embedding-model deployments fail with error 715-123420, “Our system has detected this request as unusual activity for your account.”

    The failure affects text-embedding-3-small, text-embedding-3-large, and text-embedding-ada-002 in East US and East US 2. It also occurs from a second Foundry resource in the same subscription, while GPT model deployments succeed.

    Please perform an account/subscription-level review of the unusual-activity restriction and route the case to the service team that can validate and release the deployment block. This is not a quota-increase request. UTC timestamps, resource details, and Activity Log correlation IDs are attached.

    While the review is pending

    Do not continue switching regions, recreating resources, or repeatedly submitting deployments. A closely matched case states that these actions do not clear this restriction and that internal Microsoft review is required.^3^

    Resolved cases show the restriction being removed after service-team analysis, followed by a request to retry after approximately one to two hours.^4^ Once support confirms release:

    1. Wait for the interval specified by the service team.
    2. Make one deployment attempt.
    3. Confirm that the deployment reaches Succeeded.
    4. If it fails again, update the same case with the new UTC timestamp and correlation ID.

    If the Subscription management request is rejected

    If the request is automatically closed with instructions to purchase technical support:

    1. Keep the support case number and closure response.
    2. Add a comment to this Microsoft Q&A thread stating that the free Subscription management route was attempted and automatically closed.
    3. Ask a Microsoft moderator to arrange a private exchange for the subscription ID, resource ID, timestamps, and correlation IDs.
    4. Do not post subscription IDs or other account identifiers publicly.

    A similar Basic-plan case followed the Subscription management path but was automatically closed, after which the user requested moderator escalation.^1^ Moderator escalation is not guaranteed, but documenting the failed public support route and its case number gives the moderator a concrete escalation record.

    References

    1. Azure AI Foundry deployment blocked by 715-123420 - Microsoft Q&A
    2. Create an Azure support request
    3. Model Deployment error: 715-123420 - Microsoft Q&A
    4. Error 715-123420 when deploying model in Foundry - Microsoft Q&A
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.