Forbidden: Your resource has been temporarily blocked because we detected unusual behavior. | Apim-request-id: 95dad2cd-aa54-454b-9497-a1fef36c7dee

Sourabh Meena 0 Reputation points
2026-05-19T07:19:59.0566667+00:00

My Azure OpenAI / Microsoft Foundry resource is blocked.

Error shown in Azure Foundry Chat Playground:

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

Apim-request-id:

11e51ab7-c13e-4cc8-891a-042e279720fd

Resource details:

Resource name: ESSE-Writer

Resource group: ESSE

Region: Southeast Asia

Deployment tested: esse-gpt-5.4-mini

Earlier deployment: esse-gpt-5.4

This happens even with a simple "hello" message in Azure Foundry Playground, so it appears to be a resource-level block.

Use case:

Internal development/testing for ESSE Writer. This is not public user traffic.

I have stopped all API traffic and retries. Before running again, I will add:

  • max_concurrency = 1
  • delay between calls
  • cache enabled
  • no retry on Forbidden/blocked errors
  • hard stop on content filter or abuse-monitoring errors
  • small daily budget/call cap

I am on the Basic support plan and the portal does not allow me to create a technical ticket. Please advise how to get this reviewed/unblocked or escalated.

Azure AI Anomaly Detector
Azure AI Anomaly Detector

An Azure service that identifies anomalies and defects early with time-series detection.

2 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Sina Salam 31,456 Reputation points Volunteer Moderator
    2026-05-20T13:35:11.5633333+00:00

    Hello Sourabh Meena,

    Welcome to the Microsoft Q&A and thank you for posting your questions here.

    I understand that you are experiencing the Azure OpenAI error "Forbidden: Your resource has been temporarily blocked because we detected unusual behavior."

    The resource has been placed under Azure OpenAI abuse-monitoring enforcement after Microsoft detected traffic patterns, content activity, or usage behavior that triggered automated protection mechanisms.

    The only resolution is to stop all traffic to the affected Azure OpenAI resource, review application activity for abnormal request patterns or policy violations, collect diagnostic information (such as Request IDs, timestamps, deployment names, and Azure Monitor logs), and submit a Microsoft Support request for a resource-level review if the block does not clear automatically.

    Creating new deployments, regenerating API keys, changing models, or repeatedly retrying requests does not address the underlying enforcement action and is not considered a reliable remediation path.

    Use the following official resources for guidance and investigation:

    I hope this is helpful! Do not hesitate to let me know if you have any other questions, steps or clarifications.

    Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.

    Was this answer helpful?

    0 comments
  2. SRILAKSHMI C 19,735 Reputation points Microsoft External Staff Moderator
    2026-05-25T16:36:42.8833333+00:00

    Hi @Sourabh Meena

    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!

    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.