Why am I being charged for Azure

Michael Lynn 0 Reputation points
2026-05-19T06:46:52.9566667+00:00

I signed up for Azure free trial. It asked for credit card for verification. After using it for 6 days and 3 weeks later got charged for $84.32. Can't figure out why I'm being charged. I had little bit of free credit left and I shut down the VM. I can't access the Azure login because it says it is blocked due to inactivity. I can't contact anybody in Microsoft was it keep sending you in loop and can't submit any support tickets. Called the toll free numbers and getting nowhere except in circle. There's no way to fight and submit for this refund because I didn't sign up for any auto payments other than the free trial. There's no way to contact because being locked out.

What's wrong with this picture? Any solutions to this? Do I need to file chargeback?

Community Center | Not monitored
0 comments No comments

2 answers

Sort by: Most helpful
  1. Bharath Y P 10,435 Reputation points Microsoft External Staff Moderator
    2026-05-19T18:49:07.1733333+00:00

    Hello Michael, sorry you’re stuck in a billing nightmare let’s unpack what’s likely happened and how to fix it:

    1. Azure free trial basics
      • You get $200 of credit valid for 30 days. Once your credit runs out or the 30 days expire, your trial “upgrades” to Pay-As-You-Go automatically—and any running resources start billing your card.
    2. Stopping a VM doesn’t always stop all charges
      • If you only “Stopped (Deallocated)” a VM, you no longer pay for compute, but you still pay for OS/data disks, public IPs, reserved cores, etc.
      • If you deleted the VM but left disks or App Service plans, those resources still incur charges until you delete them or switch them to a free tier.
    3. Reactivate your portal access
      • Subscriptions can get “blocked due to inactivity.”
      • Sign into https://portal.azure.com, look for a “reactivate” or “upgrade” banner on your subscription blade, and follow the prompts.
      • If the portal still won’t let you file a support ticket, use this direct link to open a billing support case: https://go.microsoft.com/fwlink/?linkid=2083458
    4. Analyze exactly what burned through your credit
      • In the Azure portal go to Cost Management + Billing → Subscriptions → [Your subscription] → Cost analysis.
      • Group or filter by service/resource to see daily charges.
    5. Request a refund before doing a chargeback
      • Once you regain portal access, go to Cost Management + Billing → your billing scope → look for Request a refund. That checks for any transactions eligible for an expedited refund.
      • If you can’t find it in-portal, include your subscription ID and invoice date/amount when you open your support case.

    Next steps for you:

    • Reactivate/upgrade the subscription so you can delete all unused resources (disks, static IPs, app service plans, etc.)

    • Run Cost analysis to pinpoint where the $84.32 came from

    • Click Request a refund or file a billing support ticket with your subscription ID and invoice details

    Let us know if you hit any blockers or need help interpreting what Cost analysis shows—happy to guide you through it!

    Reference docs

    Hope this helps. If the information was useful, please consider accepting the answer and upvoting. Feel free to reach out if you need any further assistance. Thank you.

    Was this answer helpful?


  2. AI answer

    2026-05-19T06:47:30.39+00:00

    Unexpected Azure charges after a free trial usually come from one of these causes:

    1. Free limits were exceeded
      • Free Azure accounts have usage limits. When those limits are exceeded, all additional usage is billed at pay-as-you-go rates, even if some free credit remains.
      • The FAQ explicitly notes that unexpected charges on a free account are most likely due to exceeding free limits. See “Why am I getting charged? I have a Free Azure account.”
    2. Resources still incurred charges even when the VM was “shut down”
      • If a VM is only stopped from inside the OS and not deallocated, certain charges (for example, disks, IPs, or other attached resources) can continue.
      • The correct way to verify charges is to review the invoice and usage details.
    3. Billing cycle timing
      • Azure bills at the end of the billing period. Charges for usage during the first 6 days can appear on an invoice weeks later, which matches the described 3‑week delay.

    To understand the $84.32 charge and prepare for any dispute or refund request:

    1. Review the Azure bill and usage
      • Use the “Review your individual Azure subscription bill” guidance to compare:
        • The invoice
        • The detailed daily usage file
        • Cost analysis in the Azure portal
      • This shows exactly which services (for example, VM, disks, networking) generated the $84.32.
    2. Analyze unexpected charges
      • Follow the “Analyze unexpected charges” guidance referenced in the Cost Management FAQ and “Understand usage and charges” article:
        • Review the invoice with Cost analysis.
        • Identify which resources and which days generated the cost.
        • Check who created/used those resources if multiple identities are involved.
    3. Tenant blocked due to inactivity
      • The error “AADSTS5000225: This tenant has been blocked due to inactivity” means the tenant is in an inactive state.
      • Administrators can request reactivation within 20 days of entering inactive state by contacting Microsoft via the global support phone numbers.
      • Another reported workaround is:
        • Use an InPrivate/incognito browser and go to https://signup.azure.com.
        • Sign in with the same email used for the free account.
        • If the system recognizes an existing free account with remaining services, it may prompt to upgrade to pay‑as‑you‑go, which can restore portal access so billing can be reviewed.
    4. Get billing support (free)
      • Billing support for Azure is free.
      • Use the documented process to create a billing support request from the Azure portal (once access is restored) by going to the support request creation blade and selecting Billing.
      • If portal access cannot be restored because the tenant is blocked, the tenant administrator must contact Microsoft using the documented global support phone numbers to request tenant reactivation first, then open a billing case.
    5. Investigate the charge from the Microsoft account side
      • For charges that appear as Microsoft or Microsoft Azure on the bank/credit card statement, use the “How to investigate a billing charge from Microsoft” guidance:
        • Sign in to the Microsoft account dashboard.
        • Go to “Manage your payments” and select “Investigate” on the unrecognized charge.
      • This can confirm which subscription and which Microsoft account generated the charge.
    6. Refund / dispute path
      • For subscription charges, use the “How to get a refund on a Microsoft subscription” guidance (linked in the Q&A answers) to check refund eligibility and submit a refund request.
      • If Microsoft and the bank both confirm the charge as valid usage (for example, usage beyond free limits), a chargeback may not succeed; the first step should always be a billing support case with Azure.

    In summary, the next concrete steps are:

    1. Attempt to restore access (tenant reactivation or signup.azure.com path).
    2. Once in the portal, review the invoice and usage with Cost analysis to see exactly what generated $84.32.
    3. Open a free Azure billing support request and, if applicable, use the Microsoft account “Investigate” flow for the card charge.
    4. Only if Microsoft billing support cannot resolve or correct the charge should a chargeback with the bank be considered.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.