Azure OpenAI gpt-5.6-terra quota request – Unified Gating email verification blocked (HTTP 403)

Question

Hello,

I am requesting an Azure OpenAI quota increase for gpt-5.6-terra, deployment type Data Zone Standard, EUR data zone.

The quota request was submitted successfully and I received the Microsoft email titled “Action needed: Verify your email account with Microsoft” from Microsoft Vetting Services.

When I click “Verify email address”, the Microsoft verification link redirects to:

https://3pc.microsoft.com/vetting/email_accept

The page then displays:

“The request is blocked.”

The verification email was received recently and the link is still within its stated 7-day validity period. I have not modified or forwarded the verification URL.

Requested quota: 100 kTPM Model: gpt-5.6-terra Deployment type: Data Zone Standard Pool: EUR Subscription type: Microsoft Azure Sponsorship

Microsoft Reference ID shown on the blocked page: 20260817T070349Z-r16bfb5fc7d6rkrjhC1ROMpdfw0000000pcg000000008t5v

This appears to be the same Unified Gating / vetting verification problem reported by other Azure AI Foundry users, where the verification request reaches the Microsoft endpoint but receives HTTP 403.

I do not have a paid Azure technical support incident entitlement, so I am asking whether a Microsoft moderator can help route or escalate this to the Azure OpenAI / Foundry quota and vetting team.

Could Microsoft please check the current verification transaction and, if necessary, reissue the verification token or recreate the pending verification transaction, rather than requiring repeated duplicate quota requests?

Thank you.

Answer 1

I am getting a similar issue, getting blocked when I try to verify the Microsoft account through Microsoft Vetting Services.

"The request is blocked.

20260824T162518Z-169b9999687bjnrjhC1PAR6hgs00000011gg00000000r9s3"

I can't access to technical support as I am on the basic plan which is incredibly frustrating and the troubleshooting measures aren't particularly helpful. Hoping that posting on here can move things along.

Answer 2

Hello @Radim Kretik

This appears to be an issue with the Microsoft Unified Gating/vetting verification workflow, rather than the Azure OpenAI quota configuration itself.

A nearly identical issue has already been reported where the Microsoft verification email redirects to:

3pc.microsoft.com/vetting/email_accept

and returns HTTP 403 – "The request is blocked."

Since your quota request was successfully submitted and the failure occurs specifically when processing the Microsoft-issued verification link, repeatedly submitting new quota requests is unlikely to resolve the underlying verification transaction.

I would recommend:

• Keep the existing quota request rather than submitting duplicates.
• Retain the Microsoft Reference ID displayed on the blocked page.
• If a Microsoft moderator responds, provide the Reference ID and quota-request details through a private message, along with the subscription ID if requested.
• Ask that the case be routed to the appropriate Azure OpenAI/Foundry quota or vetting team to investigate or reissue the verification transaction.

Do not post your subscription ID, tenant ID, verification URL/token, or other account identifiers publicly.

Also, the current Azure OpenAI quota documentation confirms that gpt-5.6-terra supports Data Zone Standard deployments, so the deployment type itself is documented. The requested quota still remains subject to Microsoft's approval and available capacity.

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