Has this happened to anyone else?

Search Azure complaints by service name, notice wording, case type, charge, outage, policy, or the thing support called it. The useful match is often not the company name; it is the exact phrase in the email or dashboard.

Bill nobody can explainConsumption billing means the number is only knowable once it is already owed. A resource left running, an egress charge nobody modelled, a tier that changed under a rename — and the breakdown is a portal blade that reco…

Subscription disabledA spending threshold, a payment method that failed a check, a fraud classifier — and the subscription is disabled with everything inside it still billing or already gone. Reinstatement is a support case, support is behin…

Support that costs money and answers nothingThe route to a human runs through a support plan purchased in advance, and what it buys is a case queue rather than an answer. Tier one restates the documentation, the case is transferred across time zones, and the resol…

Searchable evidence

The strongest matches on Azure Sucks come from the words that appeared in the bill, warning, appeal, support case, policy notice, dashboard, receipt, refund email, or outage update. A useful search can be a Azure detail, an error phrase, a line item, a product name, a region, a case type, or the exact wording a support script kept sending back.

The subscription ID and the billing period.
The meter name and the resource generating the charge.
The day the cost stepped up, from the daily usage export.
The support case number and what tier of support you were paying for.

Common threads here include Bill nobody can explain, Subscription disabled, Support that costs money and answers nothing, Outage or region failure. Searching one concrete phrase usually beats searching only the brand name, because the long-tail wording is how two strangers find out they were handed the same problem.