An Azure service that provides access to OpenAI’s GPT-3 models with enterprise capabilities.
Dear @Yeong Eun Kim
This error isn’t caused by your deployment settings or the model itself. Error 715‑123420: “Our system has detected this request as unusual activity for your account” is a platform-level block from Microsoft’s automated fraud/risk protection (Real-Time Fraud Protection, RTFP) that intercepts Foundry/Azure OpenAI model deployments before provisioning.
Because it’s an account/subscription safety review, changing model, region, SKU, or retrying won’t clear it; the restriction must be reviewed and lifted by Microsoft’s internal team.
How to get this reviewed or escalated
Even with a Basic support plan, you can still open a support request for subscription/account-level issues. Use the following steps:
- Open a support request in the Azure portal
- Go to Azure portal → Help + support → Create a support request.
- Issue type: Technical (or Subscription Management if that option is shown for account/risk flags).
- Service: Azure OpenAI Service or Azure AI Services (whichever owns your Foundry resource).
- Problem type: Account or subscription access (or closest equivalent like Subscription unblock or reinstatement).
- In the description, include:
- The exact error text:
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. - Your Subscription ID, resource group, Foundry/AI resource name, region, and the model + version you’re deploying (e.g.,
gpt-5-mini) - The UTC timestamp of a failed deployment attempt.
- Any IDs shown in the error or Activity Log: Trace ID, Client Request ID, Service Request ID, or Correlation ID.
- The exact error text:
- Explicitly request RTFP review
- State clearly that you are hitting error 715‑123420 and ask for the case to be routed to the Fraud Protection / RTFP team for a manual review and unblock of your subscription for Foundry/Azure OpenAI deployments.
- While the ticket is open
- Avoid repeatedly retrying deployments or creating/deleting Foundry resources; this can reinforce the risk signal.
- Wait for support to confirm the restriction is lifted, then try a single deployment again.
If the portal doesn’t let you create a “Technical” request due to Basic support, try creating a Subscription Management request instead (billing/account category), which is allowed on Basic plans, and reference the same error code and RTFP review request.
Help make this community better for everyone: if this answer resolved your issue, please accept it or leave an upvote. If not, share more details in a comment so we can continue the discussion and find the right solution.