Title: 715-123420 blocking all model deployments on Azure OpenAI subscription

Question

Title: 715-123420 blocking all model deployments on Azure OpenAI subscription

Gourav Salottra 20

Subscription ID: 4289c1d1-43f4-4f42-904d-3405d11eb42f

Resource group: thrivarc

Resources: thrivarc (Azure OpenAI), thrivarc-foundry (AIServices)

Error: 715-123420 on ALL deployment attempts including gpt-5.4, DeepSeek-R1-0528

Existing deployments (gpt-4o, gpt-4o-mini) were created before the block.

No new deployments succeed. Quota shows available capacity.

Requesting RTFP review and subscription unblock.

Anshika Varshney 15,625 Reputation points Microsoft External Staff Moderator

2026-06-01T18:15:07.1533333+00:00

Hi @Gourav Salottra

When this error occurs (Error Code 715-123420 or 555420), it indicates that Azure AI Foundry has blocked GPT model deployment due to a fraud signal, and the request requires review by the appropriate internal team.

To proceed with further investigation and escalation, could you please share the details requested in private message for the same.

Thankyou!
Anshika Varshney 15,625 Reputation points Microsoft External Staff Moderator

2026-06-02T07:50:02.0366667+00:00

Hi @Gourav Salottra

We’ve raised INC for this issue, and our team is actively working on it. Please remain patient we’ll provide an update as soon as we receive further information.

Thankyou!
Anshika Varshney 15,625 Reputation points Microsoft External Staff Moderator

2026-06-11T12:40:20.1666667+00:00

Hi @Gourav Salottra

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

Thankyou!

Answer accepted by question author

Anshika Varshney 15,625 Microsoft External Staff Moderator

Hi @Gourav Salottra

Hope you are doing well.

We have received an update from the PG team that the issue has been rectified. Analysis and adjustments completed, please try again within 1-2hours.

Could you please check from your end and confirm whether the issue is now resolved?

If the updated response resolves your query, kindly consider clicking Upvote and Accept Answer so it can help others as well.

Looking forward to your response.

Thankyou!

0 comments

1 additional answer

Your answer

Anshika Varshney 15,625 Reputation points Microsoft External Staff Moderator

2026-06-01T18:15:07.1533333+00:00

Hi @Gourav Salottra

When this error occurs (Error Code 715-123420 or 555420), it indicates that Azure AI Foundry has blocked GPT model deployment due to a fraud signal, and the request requires review by the appropriate internal team.

To proceed with further investigation and escalation, could you please share the details requested in private message for the same.

Thankyou!
Anshika Varshney 15,625 Reputation points Microsoft External Staff Moderator

2026-06-02T07:50:02.0366667+00:00

Hi @Gourav Salottra

We’ve raised INC for this issue, and our team is actively working on it. Please remain patient we’ll provide an update as soon as we receive further information.

Thankyou!
Anshika Varshney 15,625 Reputation points Microsoft External Staff Moderator

2026-06-11T12:40:20.1666667+00:00

Hi @Gourav Salottra

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

Thankyou!

Answer 1

Jerald Felix 18,760 Volunteer Moderator

Hello Gourav Salottra,

Greetings! Thanks for raising this question in the Q&A forum.

The error code 715-123420 typically indicates that your Azure subscription has been flagged or temporarily blocked by Microsoft's automated abuse/fraud prevention system (also called the RTFP Real-Time Fraud Prevention system). This can happen even when quota appears available, and it blocks all new deployments at the subscription level. Your existing deployments (like gpt-4o and gpt-4o-mini) remain unaffected because they were created before the block was applied.

Here's what you can do to get this resolved:

Step 1: Raise an Azure Support Request

Go to the Azure Portal at portal.azure.com and sign in.
In the left menu, click on "Help + Support."
Click "Create a support request."
Set Issue type as "Technical" and select your subscription.
Under Service, search for and select "Azure OpenAI."
Describe the issue clearly mention error code 715-123420, that all new deployments are blocked, and that you are requesting an RTFP review and subscription unblock.
Include your Subscription ID, Resource Group name (thrivarc), and the specific models you tried to deploy (gpt-5.4, DeepSeek-R1-0528).

Step 2: Set Severity Appropriately

Choose severity "B – Moderate" or higher if this is blocking your business operations.
This ensures faster routing to the Azure backend team who can review and lift the RTFP flag.

Step 3: While You Wait

Try deploying in a different Azure region if you haven't already sometimes the block may be region-specific.
Check the Azure Service Health dashboard at status.azure.com to rule out any ongoing platform-level issues.
Verify that your subscription has no unpaid invoices or policy violations under "Cost Management + Billing," as these can sometimes trigger deployment blocks.

Step 4: Follow Up if Needed

If you don't hear back within 24–48 hours, follow up on the support ticket with your tracking number.
You can also reach out via the Azure Community forums or your Microsoft account manager (if you're on an enterprise plan) to escalate.

Unfortunately, RTFP unblocks cannot be done through the portal self-service they require manual review by the Microsoft support team, so raising a support ticket is the right and only path forward here.

If this answer helps you kindly accept the answer which will help others who have similar questions.

Best Regards,

Jerald Felix.

Gourav Salottra 20 Reputation points

2026-06-01T01:59:56.2266667+00:00
Hi Jerald,

Thank you for the detailed response. I followed all the steps you outlined and have narrowed down the exact root cause.

az provider show --namespace Microsoft.CognitiveServices returns "Registered", confirming the provider is active on my subscription. However, az feature list --namespace Microsoft.CognitiveServices returns an empty array — no features are registered at all, including OpenAI.

When I attempt to register the feature manually via:

text az feature register --namespace Microsoft.CognitiveServices --name OpenAI

I receive:

text (FeatureNotFound) The feature 'OpenAI' could not be found. Code: FeatureNotFound

This confirms the issue is not a fraud flag but rather that the OpenAI feature has never been provisioned on this subscription and cannot be self-served through the CLI or portal. This requires manual activation by the Microsoft backend team.

Subscription details for your reference:

Subscription ID: 4289c1d1-43f4-4f42-904d-3405d11eb42f

Resource Group: thrivarc

Subscription type: Startup

Existing working deployments: gpt-4o, gpt-4o-mini (created before the block)

Blocked models: gpt-5.4, DeepSeek-R1-0528

I am building Thrivarc, an AI-powered research platform currently in active development. This block is directly halting production work. I would be very grateful if you could escalate this for manual OpenAI feature activation on my subscription, or point me to the exact team/form that can action this without requiring a paid support plan.

Thank you for your time and help on this.

Best regards, Gourav Founder, Thrivarc
Jerald Felix 18,760 Reputation points Volunteer Moderator

2026-06-01T02:09:00.8633333+00:00
Thanks for your detailed follow-up @Gourav Salottra this is really helpful information and great troubleshooting work on your end!

You've actually identified the root cause very precisely. The fact that az feature list --namespace Microsoft.CognitiveServices returns an empty array and that manually registering the OpenAI feature throws a FeatureNotFound error confirms that the OpenAI feature flag has never been provisioned on your Startup subscription at the backend level. This is different from a typical RTFP fraud flag it is a backend provisioning issue that requires manual activation by the Microsoft team, and you are absolutely right that it cannot be self-served through the CLI or portal.

Here is exactly what you should do next to get this resolved without a paid support plan:

Step 1: Submit a Free Azure Support Request (Billing/Subscription level no paid plan needed)

Go to portal.azure.com and sign in.

Navigate to "Help + Support" and click "Create a support request."

Set the Issue Type to "Subscription Management" this type of request is available for free and does not require a paid support plan.

In the description, clearly state that the OpenAI feature is not provisioned on your Startup subscription, the az feature register command returns FeatureNotFound, and you are requesting manual backend activation of the OpenAI feature under Microsoft.CognitiveServices.

Include your Subscription ID (4289c1d1-43f4-4f42-904d-3405d11eb42f), Resource Group (thrivarc), and mention that existing gpt-4o and gpt-4o-mini deployments work but no new deployments are possible.

Step 2: Reach Out via the Azure Developers Community

Post your issue on the official Azure Feedback / Developer Community at developercommunity.visualstudio.com or the Azure GitHub Issues page at github.com/Azure/azure-rest-api-specs/issues.

Tag it with "Azure OpenAI" and "CognitiveServices feature provisioning" these channels are monitored by Microsoft engineers who can escalate backend provisioning issues.

Step 3: Try the Microsoft for Startups Founders Hub Channel

Since your subscription type is Startup, sign in to foundry.microsoft.com (Microsoft for Startups Founders Hub).

Use the support or contact option within the Founders Hub dashboard startup subscribers often get faster routing for backend provisioning issues through this channel.

Mention that you are building Thrivarc, that active development is blocked, and request urgent OpenAI feature activation on your subscription.

Step 4: Include This Technical Evidence in All Communications

When you contact any support channel, make sure to paste the following outputs to speed up resolution:

Output of az provider show --namespace Microsoft.CognitiveServices (showing "Registered")

Output of az feature list --namespace Microsoft.CognitiveServices (showing empty array)

The FeatureNotFound error from your az feature register attempt

Your Subscription ID, error code 715-123420, and blocked model names

This technical evidence makes it very clear this is a backend provisioning gap and not a policy or quota issue, which will help the support team act faster.

You are very close to a resolution — the issue is well-defined and just needs the right Microsoft backend team to flip the feature flag on your subscription. Please do follow up if you do not hear back within 48 hours.

If this answer helps you kindly accept the answer which will help others who have similar questions.

Best Regards,

Jerald Felix