Request a Microsoft account/subscription-level review for the deployment block, because reducing TPM does not clear the “unusual activity” validation and comparable 715-123420 cases were resolved only after Microsoft adjusted or unblocked the subscription.^1^
Submit the review request
- In the Azure portal, open Help + support and select Create a support request.
- Describe the issue as:
Microsoft Foundry gpt-5-mini Global Standard deployment blocked by “Our system has detected this request as unusual activity for your account.” Request account/subscription security-validation review.
- Select the affected subscription and Foundry resource.
- If available, choose Subscription management or Billing/subscription rather than quota increase. Azure provides subscription-management support independently of technical support plans.^2^
- Include:
- Exact error message and error code, particularly
715-123420 if displayed
- Subscription ID and tenant ID
- Foundry resource and resource-group names
- Model and version:
gpt-5-mini
- Deployment type: Global Standard
- Region: North Central US
- Requested capacity: 10,000 TPM
- Failure timestamp in UTC
- Correlation ID
- Confirmation that model availability and quota were already verified
Do not post subscription IDs, tenant IDs, or correlation details publicly; provide them only through the private support request.
The account used to create the request must have Owner, Contributor, Support Request Contributor, or equivalent Microsoft.Support/* permission at subscription scope.^2^
Collect the correlation ID
In the Azure portal:
- Open the resource group containing the Foundry resource.
- Select Deployments or Activity log.
- Open the failed
Microsoft.CognitiveServices/accounts/deployments/write operation.
- Copy its Correlation ID, timestamp, and complete error details.
Azure Support uses deployment correlation IDs to locate related operations.^3^
What has already been ruled out
No further TPM reduction or regional availability check is warranted from the information provided:
-
gpt-5-mini version 2025-08-07 supports Global Standard deployment in northcentralus.^4^
- Similar failures occurred despite available quota and were rejected during an additional validation stage before normal provisioning.^5^
- Other matching cases were resolved by backend adjustment or subscription unblocking.^6^
Avoid repeatedly deleting and recreating the Foundry resource or deployment. If the subscription is new and automation is being used, submit the first deployment manually through Foundry after the restriction is released; this was the specific guidance in a matching first-deployment case.^1^
If the portal does not expose a usable support-request path, add these details to the Microsoft Q&A case and request private moderator-assisted routing. Do not place account identifiers in the public post.
References
- Model deployment blocked with error 715-123420 "unusual activity" - Microsoft Q&A
- Create an Azure support request
- View deployment history with Azure Resource Manager
- Region availability for Foundry Models sold by Azure (standard)
- Azure OpenAI: "unusual activity" BadRequest blocks all model deployments (scale + new) across my subscription - Microsoft Q&A
- Error 715-123420 when deploying model in Foundry - Microsoft Q&A