Azure AI Foundry model deployments blocked by error 715-123420

ret2lib 0 Reputation points
2026-09-01T16:44:43.22+00:00

I cannot deploy models to my Azure AI Foundry resource. Every deployment attempt fails with:

715-123420: Our system has detected this request as unusual activity for your account. If you are confident this is in error, please contact support.

Failed deployment attempts:

  • Time: 2026-08-04 00:46:07 UTC
  • Model: gpt-5.6-luna
  • Correlation ID: ff87a9cd-06d1-4937-a8c5-615631e0170d
  • Time: 2026-08-17 16:58:57 UTC

I have reached out many times before but have never received a reply.

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


1 answer

Sort by: Most helpful
  1. Alex Burlachenko 26,695 Reputation points MVP Volunteer Moderator
    2026-10-25T16:30:38.22+00:00

    Hi ret2lib & thx for join me at Q&A platform,

    Error 715-123420 is generally associated with Microsoft's service-side account or subscription risk protection, rather than a problem with the model deployment configuration itself.

    This means changing the model, region, deployment SKU, or available quota is unlikely to resolve it. The restriction needs to be reviewed by the appropriate Microsoft backend team, and there isn't a supported CLI or portal workaround to clear it.

    I checked the existing discussion, and there's an important detail here. Ganesh confirmed on September 3 that your information had been forwarded for backend investigation. On September 28, he requested additional details through a private message. However, your latest comment on October 23 indicates that you never received that message.

    At this point, the issue is no longer about troubleshooting the deployment. It's about getting the existing investigation moving again.

    I'd recommend asking Ganesh to resend the private message or provide another secure way to submit the requested information. It would also be reasonable to request the current investigation status, an escalation or support case reference if one exists, and confirmation of whether the backend team is waiting for anything else.

    You've already provided a useful correlation ID, ff87a9cd-06d1-4937-a8c5-615631e0170d, along with the August 4 UTC timestamp. Those should help the team locate the original failed deployment. Any subscription identifiers or additional account verification details should be shared privately.

    Given how long this has been pending, I wouldn't recommend opening more duplicate Q&A threads or repeatedly attempting new deployments. Neither is likely to accelerate the risk review.

    Without access to Microsoft's internal review systems, nobody here can reliably determine why your subscription was flagged or when the restriction will be lifted.

    rgds,

    Alex

    p.s. if my answer is help - pls mark it as an answer

    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.