Getting "unusual activity for your account" (BadRequest) when deploying models on Azure for Students

Gael Gomes 0 Reputation points
2026-10-19T00:46:46.5633333+00:00

Hi everyone,

I'm a software engineering student and junior ai harness developer , currently building a project called Weave using my Azure for Students subscription.

Earlier today, my previous Azure OpenAI resource got hit with a temporary content policy block while I was testing some agent prompts. Since I'm still learning my way around Azure AI Foundry, I deleted the old resources (and purged them from soft-delete) and created a fresh resource (weave-openai-service in eastus2, resource group rg-weave-prod) to start clean.

The resource itself deployed fine, but now whenever I try to deploy a model (tried gpt-6-luna and gpt-5.6-luna both via portal and Azure CLI), I get stuck with this error:

Code: BadRequest

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

I even tried opening a support ticket through PowerShell (az support in-subscription tickets create), but got blocked by InvalidSupportPlan because my account is on the Free/Student tier, and the portal doesn't let me submit a technical ticket either.

I'm a real student working on an academic/portfolio project, not running any spam or abuse. Here is my LinkedIn profile if it helps verify my identity: https://www.linkedin.com/in/gael-rene-gomes

Could a Microsoft moderator please reach out via Private Message so I can share my Subscription ID and get this unusual activity flag cleared?

Thanks a lot!

Gael Gomes

Azure OpenAI in Foundry Models
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Andriy Bilous 12,596 Reputation points MVP
    2026-10-20T08:30:39.1+00:00

    Hello Gael Gomes

    This error is consistent with an Azure OpenAI account/subscription-level security or risk-protection restriction, rather than a problem with your model deployment configuration.

    Here's what I recommend:

    1. Stop deleting and recreating resources. A new Foundry resource does not necessarily clear an account-level restriction.
    2. Go to Azure Portal → Help + support → Create a support request and select Billing / Subscription management, describing the issue as an account restriction affecting Azure OpenAI deployments. Billing and subscription support is available without purchasing a technical support plan.
    3. If the request is rejected or redirected to paid technical support, ask a Microsoft Q&A moderator to facilitate a private escalation to the Azure OpenAI account-protection team. Similar cases have received private Microsoft staff follow-up.

    Include the exact error, model names, region, UTC timestamp, and request/correlation IDs. Provide subscription and resource IDs privately.

    Also mention the previous temporary content-policy block. It may be relevant to the investigation, although we cannot confirm that it caused the new deployment restriction.

    This requires Microsoft-side review if the restriction is confirmed. Changing models, recreating resources, or increasing quota is unlikely to resolve it.

    Official references:

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