Azure AI Foundry: model deployment fails with "unusual activity for your account" (BadRequest)

Anurag Maurya 20 Reputation points
2026-07-23T15:45:50.57+00:00

I'm trying to deploy a model in Azure AI Foundry and the deployment is rejected with an "unusual activity" error. This appears to be a false positive, and the error message itself directs me to contact support, so I'm raising it here.

What I'm doing

Deploying the model gpt-5.6-sol in Azure AI Foundry (Azure OpenAI Service) through the portal.

Error returned


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

If you are confident this is in error, please contact support.

Diagnostic IDs

  • Trace ID: c261a9f6-3249-49da-b028-42321122edd5
  • Client request ID: b63d2741-40e4-4934-9b90-ca441724e47a
  • Service request ID: 611f02a5-8873-4040-b446-061e32202f9e

What I've already checked

  • The subscription is active and in good standing with no billing issues.
  • Quota is available in the region for this model.
  • Retried the deployment after some time — same error each attempt.
  • No unusual or automated traffic is being generated from this account.

What I need

Could someone from the product/support team check what triggered this flag against my account and have it reviewed and lifted so I can proceed with the deployment? I have not shared my subscription ID here since this is a public forum, but I'm happy to provide the subscription ID, resource group, and resource name privately to whoever picks this up.

Thanks in advance.

Community Center | Not monitored
0 comments No comments

Answer accepted by question author

Allan Solomon Mejia 3,175 Reputation points
2026-07-23T18:18:20.78+00:00

Hi Anurag,

The error "Our system has detected this request as unusual activity for your account" is typically generated by Azure's risk detection service rather than by the model deployment process itself. Since you've already confirmed your subscription is active, quota is available, and the issue is reproducible, there's unfortunately little you can troubleshoot from your side.

I'd recommend opening a Microsoft Support ticket and including the Trace ID, Client Request ID, and Service Request ID you've captured. These identifiers allow the engineering team to locate the backend logs and determine what triggered the risk assessment. They can also confirm whether the flag can be cleared or if additional verification is required for the subscription or tenant.

Before opening the ticket, it's also worth verifying:

The Azure AI Foundry resource is deployed in a region that supports gpt-5.6-sol.

The account has the required Azure RBAC permissions (for example, Cognitive Services OpenAI Contributor or equivalent).

No Conditional Access, tenant security policies, or organizational restrictions are blocking the deployment request.

If all of those check out, this is most likely a backend service issue that only Microsoft Support can investigate using the diagnostic IDs you've provided.

Please "Accept the Answer" if this information helped you. This will help us and others in the community as well.

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Most 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.