Cannot deploy models to Foundry projects due to "unusual activity" on my account

Douglas Starnes 0 Reputation points MVP
2026-07-18T16:30:43.05+00:00

As of 7/18/2026 when I try to deploy a model to a Foundry project, I receive an error about the request being flagged for "unusual activity" (see attachment).

The only thing that I can think of that has happened is on Wednesday July 15th, the credits for my MVP tenant were refreshed. I have been able to create agents with the Agent Service that worked fine but deploying a model directly from a project will not work. And I have tried models from different publishers (at least OpenAI and Microsoft).

Thanks! 2026-07-18_11-16-42

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

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Manish Deshpande 7,785 Reputation points Microsoft External Staff Moderator
    2026-07-18T18:00:13.42+00:00

    Hello @Douglas Starnes

    Thanks for reaching out to Microsoft Q&A we have started looking into this meanwhile could you please provide any error if your receiving post this error.

    Wait for the internal review to clear the block

    • Other cases with Error 715-123420 / 555420 have been resolved after the platform team removed the block, and customers were able to deploy again.
    • If you’re able to retry: Redeploy or delete it and try again after some time (commonly within 1–2 hours, and if it persists, after up to 24 hours), since the unblock/propagation can take time.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Christos Panagiotidis 2,741 Reputation points
    2026-07-19T10:24:26.25+00:00

    This error does not look like a normal quota, RBAC, model availability, or project configuration problem. Error 715-123420 is generally associated with an automated account-risk or fraud-protection block that occurs before the deployment request reaches the model provisioning process. That would explain why Agent Service still works while direct model deployments fail across multiple publishers. Similar recent cases required Microsoft Support to remove the backend restriction.

    Was 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.