715-123420 error in foundry model deployment

Hi @Mahiraa kansal

Error 715-123420, “Our system has detected this request as unusual activity,” is not normally caused by model quota, region availability, RBAC, or deployment configuration. Recent Microsoft Q&A cases confirm that this error can indicate an account- or subscription-level risk or fraud-protection block that requires backend review.

Since you've confirmed that all models are failing with the same error, I would avoid repeatedly changing models, regions, quotas, or recreating the Foundry resource. Those actions generally won't clear this type of restriction.

There is also a very recent case where Microsoft reviewed the same 715-123420 condition and subsequently confirmed that the subscription had been unblocked from the backend.

I recommend opening an Azure Support request for Microsoft Foundry/model deployment and providing the error code, subscription ID, Foundry resource ID, UTC timestamp, and the Trace/Correlation/Service Request ID from a failed deployment. If you cannot open a technical support request, ask a Microsoft moderator here to assist with an internal escalation, as has been done for other cases with this exact error.

Also, I suggest removing the Subscription ID from the public post and providing it privately to Microsoft Support/moderators instead.

At this point, Microsoft needs to review the backend restriction rather than continue deployment troubleshooting.

Help make this community better for everyone: if this answer resolved your issue, please accept it or upvote it. If not, share more details in a comment so we can continue the discussion and find the right solution.