A catalog of AI models in Microsoft Foundry that you can discover, compare, and deploy using Azure’s built‑in tools for evaluation, fine‑tuning, and inference
Error 715-123420 requires review by the Microsoft Foundry service team; a Q&A moderator must initiate any private exchange, because subscription and correlation details should not be posted publicly.^1^
Information to prepare for moderator review
Edit the question to include the following non-confidential details:
- Azure region
- Foundry resource type/kind
- Model name and version
- Deployment SKU/type, such as
GlobalStandard - Approximate UTC time of the latest failure
- Whether every model fails or only particular models
- Whether this is a new subscription
- Confirmation that the error is consistently 715-123420
Do not publish the full subscription ID, tenant ID, access keys, tokens, or other credentials. Wait for a moderator to contact you through a private Q&A channel. Matching cases have been routed to the product group and rectified following backend review.^2^
Collect the correlation ID
- In Azure Portal, open the affected resource group.
- Select Activity log.
- Filter to the failed deployment’s date/time.
- Open the failed deployment operation.
- Select JSON.
- Copy the Correlation ID and operation timestamp.
The correlation ID allows support to trace that operation across Azure services.^3^
Keep the correlation ID and full subscription ID ready to provide privately. Avoid repeatedly attempting deployments while the review is pending.
If moderator contact is not available
Since the technical-ticket path is unavailable under the current support plan, check whether the issue is actually permissions-related:
- Creating a subscription-scoped support request requires Owner, Contributor, Support Request Contributor, or a custom role containing
Microsoft.Support/*. - Technical support requires an eligible support plan; subscription-management support is available without one.^4^
If the required role is present but the portal still prevents a technical request, use:
Azure Portal → affected Foundry resource → Support + Troubleshooting → Create a support request
Include:
- Error code and complete message
- UTC timestamp
- Resource name, region, model/version, and deployment SKU
- Correlation ID
- Steps to reproduce
- Statement that technical-ticket creation is unavailable under the current plan
The error itself is not the normal “quota exceeded” condition. Foundry reports quota failures separately, so changing TPM or requesting quota is only relevant if the deployment also returns an explicit quota error.^5^
References