Azure Foundry Error 715-123420 — Basic Support — Request for Microsoft Internal Escalation

Error 715-123420 requires an account-specific Microsoft review; keep this Microsoft Q&A question open so a Microsoft moderator can initiate private contact and, where appropriate, route the case to the relevant service or security team.

Closely matching cases document the same unusual-activity error being resolved after review or remediation by Microsoft’s internal team.^1^^2^

What to do now

1. Do not publish subscription, tenant, resource, or correlation IDs in this public thread.
2. Wait for a Microsoft moderator to open a private-message conversation. A customer cannot initiate that Q&A private channel; moderators use it when account-specific information is required. Subscription IDs, tenant IDs, support-ticket IDs, and scrubbed logs are permitted there.^3^
3. When contacted privately, provide:
   • Subscription and tenant IDs
   • Foundry/Azure OpenAI resource ID
   • Exact model names and versions
   • Region and deployment SKU: East US / Global Standard
   • Failure time: October 29, 2026, 23:53 UTC
   • Deployment operation and correlation IDs from Azure portal → Monitor → Activity log
   • The full 715-123420 error text
   • Confirmation that GPT-6 Luna succeeds while Terra and Sol fail
4. Avoid repeated deployments or resource recreation while review is pending. A matching Q&A case states that retries, region changes, and recreated resources do not clear this type of restriction and may worsen the activity pattern.^4^

A moderator can assess and route the request, but a public Q&A post does not guarantee that a private message or internal escalation will be opened. Only Microsoft staff can confirm the account-specific disposition.

Supported ticket routes

Azure Basic Support does not include ordinary technical support tickets. Azure does provide unlimited support for subscription management, billing, quota adjustments, and account transfers, while technical cases require an eligible support plan.^5^

If the portal offers Priority Community Support, complete its guided support flow:

1. Azure portal → ? → Support + Troubleshooting.
2. Describe error 715-123420 against the affected resource.
3. Review the generated Microsoft Q&A draft and remove sensitive data.
4. Publish it and provide identifiers only through a moderator’s private message or the email conversation associated with the generated ticket.^6^

If Partner Launch Benefits are expected to include a support entitlement that is not appearing, ask the tenant administrator or owner of the support agreement to verify that the benefit is linked and accessible. Official guidance recommends that route when support access should exist but is unavailable because of entitlement or subscription coverage.^7^

Do not submit this as a quota request merely to bypass the technical-support restriction: the reported failure is an account-specific deployment review, and quota has already been verified.

References

1. Model deployment blocked by error 715-123420 (Real-Time Fraud Protection) - Microsoft Q&A
2. 715-123420: An error occurred. Please reach out to support for additional assistance. - Microsoft Q&A
3. Private messages on Microsoft Q&A
4. Model Deployment error: 715-123420 - Microsoft Q&A
5. Create an Azure support request
6. Get Azure help through Priority Community Support (PCS)
7. Microsoft Cloud Portals: Self-Help When a Support Request Cannot Be Opened