A unified Azure platform for creating and managing AI models, agents, and applications with built‑in enterprise security, monitoring, and governance
Hi fan & thx for join me at Q&A platform,
Error 715-123420 is the key detail here. The message about unusual account activity suggests that the request was blocked by a service-side risk or eligibility check during Azure AI Foundry resource creation, rather than by a normal Bicep template validation problem.
Your earlier RequestConflict issue is probably unrelated. The current failure occurs during preflight validation for Microsoft.CognitiveServices/accounts, so changing resource dependencies or running azd up repeatedly is unlikely to resolve it.
Creating and deleting resources while working through Microsoft Learning labs is a legitimate use case, but automated protection systems can still flag certain deployment patterns. That doesn't prove ur account has been restricted for fraud, and the public error message doesn't tell us which specific condition triggered the block.
Unfortunately, there's no documented customer-side command I'm aware of that can clear error 715-123420 or force a new risk evaluation. If this is a false positive, it needs to be reviewed by the Microsoft team responsible for the restriction.
I'd ask a Microsoft Q&A moderator to help identify the correct private escalation path for Azure AI Foundry resource provisioning and account risk review. The engineering team should check the failed deployment's correlation ID, the subscription's provisioning eligibility, and the reason the request was rejected. They can then determine whether additional verification is required or whether the restriction can be cleared.
Regarding the support portal, the Support + troubleshooting panel is part of the normal support flow, but it should eventually provide a way to continue with an eligible support request. If clicking Go never advances, even in InPrivate mode, that may be a separate portal issue or a limitation of the subscription's support entitlement. Azure for Students doesn't generally include unrestricted technical support, so a moderator may need to help identify an available escalation route.
I'd avoid creating another subscription, changing accounts, or repeatedly redeploying as a workaround. Those actions won't establish why the original request was blocked and could complicate the investigation.
You've already collected the right evidence. Keep the subscription ID, deployment tracking ID, and any account verification information private. A moderator can advise whether a secure channel is available, although posting here doesn't automatically initiate an internal risk review.
The main thing Microsoft needs to establish is whether 715-123420 represents a temporary automated restriction, an account eligibility issue, or a provisioning policy that applies to Azure for Students. Only the responsible Microsoft team can confirm that for ur subscription.
One question: can u still create ordinary Azure resources in the same subscription, or are only Microsoft Foundry / Cognitive Services deployments failing? That distinction may help narrow the scope of the restriction.
rgds,
Alex
p.s. if my answer is help - pls mark it as an answer