Share via

715-123420: An error occurred. Please reach out to support for additional assistance.

2026-05-22T15:25:52.9466667+00:00

Region: Sweden Central

Existing deployments: GPT-5-mini / GPT-5 etc (working)

Failing deployment: GPT-5.4 (version 2026-03-05)

All attempts to deploy GPT-5.4 (or GPT-5.5 haven't tried other models) fail immediately with:

715-123420: An error occurred. Please reach out to support for additional assistance.

No additional error details are returned. The model appears in the Foundry catalog as GA and the Deploy button is available, but deployment fails every time.

Existing deployments (GPT-5 included) continue to work. The issue affects new deployments only.

I suspect this is an RTFP (Real-Time Fraud Prevention) block on the sponsorship subscription, similar to the issue reported in https://learn.microsoft.com/en-us/answers/questions/5825772/foundry-model-deployment-fails-with-715-123420-for. The Developer support plan only routes to Q&A — I cannot open a support ticket to request an unblock.

Requesting:

  1. Confirmation of whether an RTFP flag is applied to my subscription
  2. Removal of the block if confirmed
  3. Guidance on deploying GPT-5.4 or other models we might need in the future

Subscription ID: [REDACTED — will share via DM if needed]

Azure OpenAI in Foundry Models

1 answer

Sort by: Most helpful
  1. Sina Salam 29,846 Reputation points Volunteer Moderator
    2026-05-24T14:35:18.8733333+00:00

    Hello Ricardo Jorge Rebelo de Sousa,

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

    I understand that you are having 715-123420: An error occurred. Please reach out to support for additional assistance.

    The failure pattern is not consistent with a normal region, quota, or RBAC problem. Sweden Central is a supported Foundry region, GPT-5.4 is an official Foundry/Azure OpenAI model family, and Microsoft’s support model for Developer/Priority Customer Support - PCS allows Azure engineers to create a support ticket on your behalf for complex cases. The right action is not more portal troubleshooting. But Microsoft internal escalation using your failed deployment correlation IDs and subscription/resource identifiers, sent through PCS/private message so the backend team can review and remove the subscription-level hold if present. Until Microsoft completes that review, there is no customer-side fix that can reliably restore new GPT-5.4 deployments. - https://learn.microsoft.com/en-us/azure/foundry/reference/region-support, https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request

    If this is not resolve to time, comment escalate so that I can help with that or use PCS.

    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?


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.