403 Forbidden: Resource temporarily blocked on gpt-5.5 - How to configure for legitimate bursty traffic

Question

403 Forbidden: Resource temporarily blocked on gpt-5.5 - How to configure for legitimate bursty traffic

Kunal Singal 0

Environment

model: gpt-5.5

region: East US 2

I recently deployed gpt-5.5 and was trying to use it with codex
Since then model seems to be blocked

HTTP/2 403 content-length: 123 content-type: application/json apim-request-id: f6501a03-6b98-48a1-8cda-288f920af250 strict-transport-security: max-age=31536000; includeSubDomains; preload x-content-type-options: nosniff x-ms-region: East US 2 date: Mon, 25 May 2026 18:57:37 GMT {"error":{"code":"Forbidden","message":"Your resource has been temporarily blocked because we detected unusual behavior."}}

Codex usage (seems expected to me for a coding agent)
User's image

Expected usage context:

Expected usage is bursty by design - not anomalous:

Production agents (end-user facing): unpredictable bursty usages by nature (not uniform over days / within single day)
At times coding agents like codex (idle for hours / days then there can be usages like above)

Key questions

Please help in unblocking the above resource? (apim-request-id above)
What specifically triggered the block: token volume, idle→burst pattern, or content filter? The 403 gives no diagnostic signal.
What limits need to be increased to accommodate bursty workloads given the expected usage? Ideally i would want to eliminate / relax these limits to accommodate our expected bursty workloads.
Is there a documented warmup recommendation for new or idle deployments?

Radwan Almsora 250 Reputation points

2026-05-25T19:34:17.64+00:00

Hi @Kunal Singal,

Sorry for the inconvenience caused.

Please check if the Azure OpenAI resource is temporarily flagged by the automated anti-abuse system due to the sudden burst of 8.8M tokens after an idle period. If it is blocked, you cannot unblock it manually through the portal or by recreating the deployment.

You need to open a formal technical support ticket first by following these steps https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request. Provide your region East US 2 and the specific request ID f6501a03-6b98-48a1-8cda-288f920af250 in the ticket.

To accommodate bursty workloads in the future, implement exponential backoff and client-side rate limiting to smooth out the traffic spikes from your coding agent.

After opening the support ticket, try testing the deployment again once the internal team reviews the resource status.

Please "upvote" if the information helped you. This will help us and others in the community.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Kunal Singal 0 Reputation points

2026-05-25T19:48:10.7233333+00:00

Hi @Radwan Almsora
Thanks for the response, i still have some doubts:

Please check if the Azure OpenAI resource is temporarily flagged by the automated anti-abuse system due to the sudden burst of 8.8M tokens after an idle period

I am not sure where to check this exactly? I've been getting same error response 403: blocked response for some days, so i believe it already confirms that resource is flagged.

To accommodate bursty workloads in the future, implement exponential backoff and client-side rate limiting to smooth out the traffic spikes from your coding agent.

I am not sure how exponential backoff is supposed to help here? I mean above resource seems to be blocked since 19th may - so even retry with exponential backoff on 403s would not succeed here

client-side rate limiting - what should be the limiting factor here ? is it ip / op tokens (TPM)? is it #requests (RPM)? what are the accepted limits under which requests won't be flagged (and block the resource itself?). Is there any official documentation / resource explaining these limits ?
Anshika Varshney 12,775 Reputation points Microsoft External Staff Moderator

2026-05-28T06:11:03.7533333+00:00
Hi @Kunal Singal

Thank you for your patience. We received an update from the Product Group team and wanted to share the findings.

The HTTP 403 error you are seeing with the message about unusual behavior 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.

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

Please let me know if you need help.

Thankyou!
Anshika Varshney 12,775 Reputation points Microsoft External Staff Moderator

2026-06-01T18:33:14.5833333+00:00

Hi @Kunal Singal

Did you get any chance to review the response.

Thankyou!
Anshika Varshney 12,775 Reputation points Microsoft External Staff Moderator

2026-06-02T18:56:53.0533333+00:00

Hi @Kunal Singal

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

1 answer

Your answer

Radwan Almsora 250 Reputation points

2026-05-25T19:34:17.64+00:00

Hi @Kunal Singal,

Sorry for the inconvenience caused.

Please check if the Azure OpenAI resource is temporarily flagged by the automated anti-abuse system due to the sudden burst of 8.8M tokens after an idle period. If it is blocked, you cannot unblock it manually through the portal or by recreating the deployment.

You need to open a formal technical support ticket first by following these steps https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request. Provide your region East US 2 and the specific request ID f6501a03-6b98-48a1-8cda-288f920af250 in the ticket.

To accommodate bursty workloads in the future, implement exponential backoff and client-side rate limiting to smooth out the traffic spikes from your coding agent.

After opening the support ticket, try testing the deployment again once the internal team reviews the resource status.

Please "upvote" if the information helped you. This will help us and others in the community.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Kunal Singal 0 Reputation points

2026-05-25T19:48:10.7233333+00:00

Hi @Radwan Almsora
Thanks for the response, i still have some doubts:

Please check if the Azure OpenAI resource is temporarily flagged by the automated anti-abuse system due to the sudden burst of 8.8M tokens after an idle period

I am not sure where to check this exactly? I've been getting same error response 403: blocked response for some days, so i believe it already confirms that resource is flagged.

To accommodate bursty workloads in the future, implement exponential backoff and client-side rate limiting to smooth out the traffic spikes from your coding agent.

I am not sure how exponential backoff is supposed to help here? I mean above resource seems to be blocked since 19th may - so even retry with exponential backoff on 403s would not succeed here

client-side rate limiting - what should be the limiting factor here ? is it ip / op tokens (TPM)? is it #requests (RPM)? what are the accepted limits under which requests won't be flagged (and block the resource itself?). Is there any official documentation / resource explaining these limits ?
Anshika Varshney 12,775 Reputation points Microsoft External Staff Moderator

2026-05-28T06:11:03.7533333+00:00

Hi @Kunal Singal

Thank you for your patience. We received an update from the Product Group team and wanted to share the findings.

The HTTP 403 error you are seeing with the message about unusual behavior 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.

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

Please let me know if you need help.

Thankyou!
Anshika Varshney 12,775 Reputation points Microsoft External Staff Moderator

2026-06-01T18:33:14.5833333+00:00

Hi @Kunal Singal

Did you get any chance to review the response.

Thankyou!
Anshika Varshney 12,775 Reputation points Microsoft External Staff Moderator

2026-06-02T18:56:53.0533333+00:00

Hi @Kunal Singal

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Answer 1

Hello Kunal Singal,

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

I understand that you are having 403 Forbidden: Resource temporarily blocked on gpt-5.5 - and need How to configure for legitimate bursty traffic.

I can say that this error is rampart recently for now with many services.

This issue is not a normal quota or rate-limit problem. A standard Azure OpenAI quota/rate-limit issue normally appears as HTTP 429, while the customer’s error is HTTP 403 with the message “Your resource has been temporarily blocked because we detected unusual behavior.” This points to a service-side protection / abuse-monitoring block, not something that can be fixed by simply increasing TPM/RPM or changing max_tokens. Azure abuse monitoring evaluates both content signals and usage behavior patterns, including recurrence, severity, and potential misuse indicators. - https://learn.microsoft.com/en-us/azure/foundry/openai/concepts/abuse-monitoring, https://learn.microsoft.com/en-us/azure/foundry/openai/how-to/quota

Best thing to do is to stop all traffic to the affected resource, then open an Azure technical support request asking Microsoft to perform a temporary block / unusual-behavior review using the APIM request ID, timestamps, resource name, region, deployment name, and the full 403 response. Azure support is the only reliable path to both unblock the resource and confirm the backend trigger category. - https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request

After Microsoft clears the block, the workload should be redesigned for bursty Codex / coding-agent traffic. If the workload remains on Standard or Global Standard deployment, enforce client-side rate shaping, backoff, jitter, request smoothing, and gradual ramp-up. If the workload is production-critical and legitimately bursty, move it to Provisioned Throughput (PTU) because PTU is designed for predictable throughput and latency with allocated model-processing capacity. - https://learn.microsoft.com/en-us/azure/foundry/openai/concepts/provisioned-throughput, and https://learn.microsoft.com/en-us/azure/foundry/openai/how-to/latency

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.

Share via

403 Forbidden: Resource temporarily blocked on gpt-5.5 - How to configure for legitimate bursty traffic

1 answer

Your answer