A Microsoft offering that enables tracking of cloud usage and expenditures for Azure and other cloud providers.
Open a free Azure Billing Support request now to have the unexpected $700 charge investigated and to request a discretionary credit or adjustment; Azure Billing Support is the appropriate team to review the charge and subscription status.^1^
1. Submit the billing request
- Sign in with the account that owns the subscription and open: https://portal.azure.com/#create/Microsoft.Support
- Enter Billing, select Go, and then select Billing.
- Select the disabled subscription.
- Select Create a support request rather than one of the suggested articles.
- Use a summary such as:
Unexpected $700 charge in two days; subscription disabled—request charge review and reactivation.
- Include:
- The affected subscription ID.
- The two-day date range.
- That the resources were created for short-term testing.
- The expected cost and the actual charge.
- The resource or service names shown in Cost Analysis.
- A clear request for investigation, a credit or waiver review, and instructions for reactivation.
- Submit the case and retain its support-request number.
Billing and subscription support does not require a paid Azure support plan.^2^ Any credit, waiver, or charge adjustment is discretionary and must be decided after Microsoft reviews the case.
2. Collect evidence and prevent further charges
In the Azure portal, open Cost Management + Billing → Cost Management → Cost analysis, select the affected subscription, and inspect the relevant two-day range:
- Change the view to daily costs.
- Group first by Service name, then by Resource or Resource group.
- Capture screenshots or export the details identifying the cost spike.
- Review the invoice, audit logs, resource ownership, and permissions if the usage is unfamiliar.^3^
- Check Cost Analysis → Smart views for an anomaly insight and drill into it to identify the affected resource group.^4^
A disabled subscription normally prevents creating or updating resources, but resources can remain retrievable or deletable.^5^ If management access is available, stop or deallocate unnecessary compute and scale down billable services where appropriate. Before deleting anything, verify dependencies and back up required data and configuration—deletion can be irreversible and disrupt dependent services.
3. Reactivate according to the displayed status
Check Azure portal → Subscriptions → affected subscription → Status. Use only the branch matching the portal message:^6^
- “Disabled because payment wasn’t received”: select the notification banner and open Settle Balance. Reactivation can take up to 24 hours after payment. Continue the billing dispute separately; submitting a dispute does not itself reactivate the subscription.
- Credit-card limit exceeded: change the payment card; eligible businesses can consider pay-by-invoice.
- Canceled pay-as-you-go subscription: open Subscriptions → subscription → Reactivate.
- Free Trial credit expired: upgrade the subscription to continue using it. Usage beyond the applicable free allowances becomes billable.
- Free Trial or Visual Studio spending limit reached: remove the spending limit in the portal. This can enable pay-as-you-go charges, so first identify and contain the resource that caused the spike.
- Security or suspicious-activity block: use the support request for the required review; payment or ordinary portal reactivation might not remove that block.
After reactivation, most resources resume automatically. If resource creation or management remains unavailable for more than 30 minutes, update the billing-support case.^6^
References