Azure OpenAI API returns 403 "Your resource has been temporarily blocked because we detected unusual behavior" while Playground works

Question

Azure OpenAI API returns 403 "Your resource has been temporarily blocked because we detected unusual behavior" while Playground works

Siddhant Vishnu 0

I am experiencing an issue where Azure AI Foundry Playground works correctly, but all direct API requests fail. I have enough credits in my account as well.

What works:

Azure AI Foundry Playground

Deployment is healthy and responds normally

Subscription is active

Credits are available

What fails:

Direct API calls

Codex application

Any external client using the API

Error returned:

{
  "error": {
    "code": "Forbidden",
    "message": "Your resource has been temporarily blocked because we detected unusual behavior."
  }
}

I have verified:

The API key is correct

The deployment exists and is active

The issue is reproducible outside of Codex

The issue occurs across multiple API clients

The deployment responds successfully in Playground, but all external API requests are blocked with the error above.

Because the Playground works while API access fails, this does not appear to be a deployment health issue, billing issue, or authentication issue.

Has anyone encountered this before? Could this indicate that the resource has been flagged by Azure abuse monitoring or safety systems?

If so, what is the recommended process for having the restriction reviewed and API access restored?

Thank you.

0 comments

3 answers

Your answer

Answer 1

SRILAKSHMI C 19,090 Microsoft External Staff Moderator

Hello @Siddhant Vishnu

Thank you for reaching out to Microsoft Q&A.

We got reply from the backend team,

The HTTP 403 error you are seeing with the message about unusual behaviour is because your Azure OpenAI resource has been temporarily blocked by the platform’s abuse detection system. This is an intentional Trust and Safety action and not due to a service outage or platform bug.

This kind of block can happen when the system detects patterns that look unusual, such as repeated requests, high frequency calls, or activity that may trigger safety or policy checks. From the platform side, this is expected behavior and is done to protect the service.

At this stage, there is no configuration change or troubleshooting step that can unblock the resource directly from the service side. The correct way forward is to request a review through the abuse mitigation process.

What you can do now is:

Submit an appeal through the Azure OpenAI abuse or mitigation request process
Provide your subscription details and resource name
Share a brief explanation of your usage scenario so the team can review and validate it

Once submitted, the relevant team will review your case and take appropriate action if the block was applied in error.

Here is the form Limited Access Review: Modified Abuse Monitoring

In short, this is not a technical issue in your setup but a safety enforcement action, and it requires review through the designated process.

Thank you!

SRILAKSHMI C 19,090 Reputation points Microsoft External Staff Moderator

2026-06-12T17:36:01.58+00:00

Hi @Siddhant Vishnu,

Following up to see if the above answer was helpful. If this answers your query, please do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Thank you!
Siddhant Vishnu 0 Reputation points

2026-06-12T22:16:04.1933333+00:00

Thank you for the guidance.

I reviewed the "Limited Access Review: Modified Abuse Monitoring" form that was recommended. However, the form states that applications submitted using personal email addresses (such as Outlook or Gmail) will be denied and that Modified Abuse Monitoring is only available to managed customers and partners.

I am a Microsoft for Startups Founders Hub participant and authenticated using my LinkedIn account (which is on my personal gmail). I do not currently have a company domain email address.

Could you please confirm whether this is the correct process for appealing a Trust & Safety enforcement action on an existing Azure OpenAI resource, or advise on the appropriate appeal process for Founders Hub participants without a company domain?

Answer 2

Siddhant Vishnu 0

This is a resource level problem.

0 comments

Answer 3

Amira Bedhiafi 42,846 MVP Volunteer Moderator

Hello Siddhant!

Thank you for posting on MS Learn Q&A.

This happens across multiple clients and with valid API keys.

Please review the resource-level safety block and check whether the resource was flagged by Trust & Safety monitoring. If possible, please escalate to the Azure OpenAI gating team for unblock review.

https://learn.microsoft.com/en-us/azure/foundry-classic/foundry-models/concepts/content-filter

Siddhant Vishnu 0 Reputation points

2026-06-03T19:50:44.2166667+00:00

Thank you for the response.

To clarify, this does not appear to be a prompt-level content filtering issue.

The deployment functions normally in Azure AI Foundry Playground, but all external API requests return:

403 Forbidden

"Your resource has been temporarily blocked because we detected unusual behavior."

The issue is reproducible across multiple clients and with valid credentials.

Given that Playground access works while API access is blocked, this appears to be a resource-level restriction rather than a content filtering event.

Could this case please be reviewed by the Azure OpenAI Trust & Safety / gating team for an unblock assessment?

Thank you.

Share via

Azure OpenAI API returns 403 "Your resource has been temporarily blocked because we detected unusual behavior" while Playground works

3 answers

Your answer