An Azure service that provides access to OpenAI’s GPT-3 models with enterprise capabilities.
Hi @Bakir-3311
Error 715-123420 isn’t documented in Microsoft’s public Azure OpenAI error reference, so there is no verified customer-side command or configuration change that can remove this restriction.
The error text explicitly requests contacting Microsoft Support. Since existing deployments can still be updated while all new deployment creations fail across the affected subscription, this doesn’t match the normally documented quota, capacity, authentication, or request-payload errors. However, only Microsoft can confirm whether an account or subscription protection control caused the block.
Recommended actions:
- Check Azure Service Health for an active Azure OpenAI or Microsoft Foundry incident affecting Sweden Central. Service Health displays subscription-specific service issues and affected regions.
- Open Subscription → Activity log, locate the failed Microsoft.CognitiveServices/accounts/deployments/write operation, and record its correlation ID. Azure documents the correlation ID as the identifier Support uses to trace failed control-plane operations.
- Create an Azure support request from Help + support → Create a support request, or from the affected resource under Support + Troubleshooting. The account needs Owner, Contributor, Support Request Contributor, or equivalent Microsoft.Support/* permission at subscription scope.
Include:
- Error code 715-123420 and complete error message
- Subscription and tenant IDs
- Affected resource IDs and Sweden Central region
- Failed model names, versions, and deployment types
- UTC timestamps
- Activity Log correlation IDs
- Trace, client-request, or service-request IDs shown by the portal or API
- Confirmation that existing deployment updates succeed but new deployment creation fails
- A request for review of the unusual-activity restriction
Do not publish subscription IDs or diagnostic identifiers in the public Q&A thread; provide them only through the private support request.
Microsoft Support must inspect the subscription-side enforcement state and determine whether it can clear the restriction.
References:
- View Azure Service Health issues
- Get the operation correlation ID
- Azure Activity Log
- Create an Azure support request
Help make this community better for everyone: If this answer helped or resolved your issue, please accept it or upvote it. If not, share more details in a comment so we can continue the discussion and find the right solution. Thank you.