HI Alexander
Based on my experience, this can sometimes happen when Azure detects account or subscription activity that triggers an automated security review, even if the actions were done for legitimate setup purposes. New environments, multiple deployments, subscription changes, or unusual sign-in patterns can sometimes be flagged unexpectedly.
If support submission is also failing, it becomes even more frustrating, but in cases like this, the issue usually needs to be reviewed by Microsoft directly because it is often tied to a backend security restriction.
If possible, I would suggest trying:
- submitting a support request from another browser or session
- checking whether there is a different admin account that can open the ticket
- reaching out through your CSP or reseller if applicable
- using Microsoft billing, sales, or account support channels to get the case routed properly
From what I have seen, this is usually not something that can be resolved entirely on the customer side once the account has been disabled for suspicious activity.
I hope you find this helpful
♠ ♠ Ace ♠ ♠