Fix Azure Overdue Payment & Suspended Subscription
Why This Is Happening
You logged into the Azure portal this morning, expecting everything to be running as normal , and instead you got hit with a banner saying your subscription is disabled, or you received an email with the subject line "Your Azure subscription has been suspended due to a past due balance." Maybe your virtual machines stopped responding. Maybe your web apps threw a 503. Maybe your team is already calling you. I've seen this exact scenario play out on dozens of accounts, and I want to be upfront with you: it feels scarier than it actually is. In most cases, this is 100% fixable in under an hour.
The root cause of an Azure overdue payment issue is almost always one of three things. First, the credit or debit card on file expired , this is by far the most common trigger, especially if you set up the subscription a year or two ago and never updated your billing profile. Second, the card was declined for a reason your bank didn't tell Azure about: a fraud hold, a spending limit, or a geographic restriction. Third, and this happens more than people admit, the invoice was generated but the auto-pay mechanism failed silently, leaving a balance that aged past the 30-day grace period.
Azure's billing cycle works on a monthly cadence. When an invoice is generated and the payment attempt fails, Azure doesn't immediately suspend your account. You get a grace period, typically 30 days for pay-as-you-go subscriptions, though this can vary by agreement type. During that window, Azure sends reminder emails to the account owner. The problem is that those emails often go to a shared billing alias that nobody checks, or straight to spam. By the time someone notices the portal warning, the grace period has already closed and the subscription flips to Disabled or PastDue state.
Once disabled, Azure puts your resources into a kind of limbo. Your VMs are deallocated, your App Services stop serving traffic, your databases go offline. The data is preserved, Azure doesn't delete anything immediately, but every minute your services are down costs you. And here's the part that frustrates people most: the error messages in the portal are maddeningly vague. "Subscription is disabled" tells you nothing about what to click or where to go. Azure support chat isn't always easy to find either, especially when the subscription is in a degraded state and some portal features stop loading correctly.
The Azure overdue payment problem also surfaces differently depending on your account type. Pay-As-You-Go accounts, Azure Dev/Test subscriptions, CSP (Cloud Solution Provider) plans, and EA (Enterprise Agreement) accounts all handle billing suspension differently, and the fix path varies. This guide covers all of them.
Browse all Microsoft fix guides if you're also dealing with related issues like Azure AD sign-in failures or Microsoft 365 billing problems: Browse all Microsoft fix guides →
The Quick Fix, Try This First
If you have a Pay-As-You-Go subscription and the issue is simply an expired or declined card, this single path resolves the majority of Azure overdue payment cases. Go directly to the Azure portal billing section, update your payment method, and trigger a manual payment. Here's exactly how.
Open your browser and go to portal.azure.com. Sign in with the account that owns the subscription, this must be the Account Administrator, not just a contributor. In the left-hand navigation, click Cost Management + Billing. If you don't see it pinned, type "Cost Management" into the top search bar and select it from the dropdown.
On the Cost Management + Billing overview page, look for the orange or red banner at the top, it will say something like "Your subscription has a past due balance of $XX.XX" or "Your subscription is disabled." Click the Settle balance button directly on that banner. This takes you to a payment confirmation screen where you can either pay with the existing card on file or add a new payment method.
If the existing card is the problem, click + Add payment method before settling. Enter your new card details, Visa, Mastercard, and Amex are all accepted. Once the card is added, set it as the default by clicking the three-dot menu next to it and selecting Set as default. Then return to the past due balance screen and click Pay now.
Payment processing usually takes between 30 seconds and 5 minutes. After confirmation, your subscription status changes from Disabled to Active within 1 to 4 hours. Your VMs won't restart automatically, you'll need to start them manually, but the billing block is cleared and all portal functionality returns.
Before you change anything, you need a clear picture of what state your subscription is actually in. Azure uses specific status codes, Active, PastDue, Disabled, Warned, and Deleted, and the fix path differs depending on which one applies to you.
Navigate to portal.azure.com and go to Cost Management + Billing. In the left menu, click Billing accounts, then select your billing account from the list. Under your billing account, expand Billing profiles. Each billing profile represents a separate billing entity, most individuals have just one, but enterprise setups can have several.
Click into your billing profile and look for the Invoices tab. You'll see a list of monthly invoices with their payment status. Look for any invoice marked Past due or Open with an overdue date. Note the invoice number (it looks like G######-#### or T######-####) and the outstanding amount. You'll need this when you contact support if the portal payment doesn't go through.
Next, click Azure subscriptions in the left pane to confirm which specific subscriptions are affected. The status column will show you whether your subscription is currently Disabled or PastDue. If it says Deleted, the situation is more serious, jump ahead to the Advanced Troubleshooting section immediately, because deleted subscriptions have a time-limited recovery window.
If everything looks correct here but you still can't access resources, note the Subscription ID (a GUID in the format xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx), you'll need it when raising a support ticket.
This is the most common fix for an Azure overdue payment. Even if your card number hasn't changed, an expired expiry date is enough to cause a hard decline. Here's how to update it properly.
From Cost Management + Billing, click Payment methods in the left navigation. You'll see a table of all saved payment methods for the billing account. Find the card that's currently set as default, it has a star icon. Check the expiration date in the Expires column. If it's expired or about to expire, click the pencil icon to edit it.
You can update the expiry date and CVV for an existing card without changing the card number, this is useful if your bank issued you a replacement card with the same number. Enter the new expiry month and year, the updated CVV, and click Save.
If you need to add a completely new card, click + Add a credit or debit card. Fill in the card number, expiry date, CVV, and billing address. Make sure the billing address matches exactly what your bank has on file, even a minor mismatch like "St" vs "Street" can cause a silent decline on Azure's end.
Once the new card is added, you must explicitly set it as the default. Click the three-dot menu (…) next to the new card and choose Set as default for this billing profile. Do not skip this step. Without doing this, Azure will keep attempting to charge the old card even though the new one is saved.
After setting the default, you should see a confirmation that the payment method has been updated. The next step is to actually pay the outstanding invoice, changing the card alone doesn't clear the past due balance.
Updating your payment method doesn't automatically pay what's owed. You need to manually trigger payment of the overdue invoice. This is where a lot of people get stuck, they update the card and wait, expecting things to fix themselves, but the subscription stays disabled because nobody actually submitted the payment.
Go back to Cost Management + Billing → Invoices. Find the invoice marked Past due and click on it. On the invoice detail page, click the Pay now button. If the button is greyed out, make sure you've completed Step 2 and set a valid default payment method first.
A confirmation dialog will appear showing the total amount due, the card to be charged, and the billing address. Review everything carefully. Click Pay to confirm. Azure will attempt to charge the card in real time.
If the payment goes through, you'll see a green success banner and the invoice status will change to Paid. Your subscription will begin reactivating. This process typically completes within 1 to 4 hours, though in my experience it usually happens within 30 to 60 minutes for pay-as-you-go accounts.
If the payment fails, Azure will display an error message. The most common error at this stage is "Payment declined by issuer", which means your bank blocked the transaction. In that case, call your bank directly and ask them to authorize the charge from Microsoft/Azure. Banks often flag large or sudden cloud payments as suspicious, especially if you haven't used that card for Azure before. Once your bank clears the hold, retry the payment from the Invoices page.
PowerShell alternative, Check subscription state after payment:
Get-AzSubscription -SubscriptionId "your-subscription-id" | Select-Object Name, StatePaying the overdue invoice re-enables the subscription, but it doesn't automatically restart your resources. Deallocated VMs stay deallocated. Stopped App Services stay stopped. You have to bring things back up manually, or use a script if you have a lot of resources.
For virtual machines: go to Virtual machines in the portal, select each VM, and click Start. For a handful of VMs, doing this one by one is fine. If you have ten or more, use Azure CLI or PowerShell to batch-start them:
# Start all VMs in a resource group using Azure CLI
az vm start --ids $(az vm list -g MyResourceGroup --query "[].id" -o tsv)
# PowerShell equivalent
Get-AzVM -ResourceGroupName "MyResourceGroup" | Start-AzVMFor App Services: go to App Services, click on each app, and click Start in the top command bar. If you were running App Service Plans in the Free or Shared tier, those might not restart cleanly, check the Activity log for any provisioning errors after the subscription re-enables.
For Azure SQL Databases: these typically resume on their own once the subscription is active, but verify by going to SQL databases and confirming the status shows Online. If a database is stuck in a Paused state, click the database name and click Resume on the overview blade.
For Azure Kubernetes Service (AKS): stopped node pools need to be restarted explicitly. Go to the AKS cluster, select Node pools, and start each pool. After starting the node pool, verify your pods come back up by checking Workloads in the AKS blade.
Give everything 10–15 minutes to fully provision before you declare victory. Check the Activity log for each resource to confirm no new errors appeared during the restart.
Sometimes the portal payment flow fails silently, or you're on a subscription type, like CSP or EA, where you can't pay directly through the portal at all. In that case, you need to raise a support ticket. Here's how to do it even when your subscription is in a degraded state.
Go to portal.azure.com and type "Help + support" in the top search bar. Select it. Click + Create a support request. On the first screen, set the Issue type to Billing. Under Problem type, select Manage subscriptions, services, resources, or quotas and then choose Subscription management as the subtype. This is important, billing tickets are handled by a different team than technical support and get routed faster.
If your subscription is fully disabled and the portal is unresponsive, there's an alternative path. Go directly to the Azure Support page (portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade) and you can create a billing ticket without an active subscription. You can also call Microsoft's billing support line, the number varies by region but is listed on the support page under "Other support options."
In your ticket description, include:
- Subscription ID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
- Invoice number: G######-#### (from Cost Management + Billing)
- Error message seen in portal (exact text)
- Steps already tried: updated payment method, attempted Pay Now
- Business impact: list affected resources and services downMicrosoft billing support typically responds to active billing tickets within 2–8 business hours. For critical production outages with revenue impact, mark the severity as A – Critical to get faster response. Once you're connected with a billing engineer, they can manually apply payment, waive late fees in some cases, and directly re-enable the subscription on the back end, something you cannot do yourself through the portal.
Advanced Troubleshooting
If the standard payment flow didn't work, or you're managing Azure at an enterprise scale under an EA or CSP agreement, the fix path is fundamentally different. Let's work through the scenarios I see most often in complex environments.
Enterprise Agreement (EA) Subscriptions
If your organization has an EA with Microsoft, you don't pay invoices through the portal at all. EA billing is handled through the Azure EA Portal at ea.azure.com, not through portal.azure.com. Your EA Administrator, which may be someone in your finance or procurement team, not IT, needs to log into the EA portal and review the enrollment status. Overdue balances on EA agreements are settled through PO-based invoicing directly with Microsoft's enterprise licensing team. If you're an IT admin without EA admin rights, escalate this to whoever manages your Microsoft licensing contract.
CSP (Cloud Solution Provider) Subscriptions
If you're on a CSP plan, meaning you purchased Azure through a reseller or managed service provider, you do not pay Microsoft directly. Your payment obligation is to your CSP partner. Contact your CSP's billing department, not Azure support. The CSP partner pays Microsoft on your behalf, and if there's a billing dispute or overdue balance on your partner account, they need to resolve it. Signs that you're on CSP: your invoices come from a company that isn't Microsoft, or your Cost Management shows a different billing entity.
Checking Event Viewer and Azure Activity Log for Root Cause
After you resolve the payment, investigate why the auto-pay failed in the first place. In the Azure portal, go to Cost Management + Billing → Invoices, click your invoice, and look for the payment history tab. It shows each attempted charge with a timestamp and result code. Common result codes include:
- 05: Do not honor (generic bank decline)
- 14: Invalid card number
- 41: Lost card reported
- 51: Insufficient funds
- 54: Expired card
- 91: Issuer unavailable (temporary bank issue, retry usually works)For code 91, a simple retry will likely succeed. For code 05 or 54, you need to contact your bank or replace the card.
Subscription Is Showing "Deleted", Act Immediately
If your subscription status is Deleted, you have a 90-day recovery window before Azure permanently destroys all resources. During this window, Microsoft can restore the subscription, but only through a support ticket, and only if the past due balance is cleared first. Do not wait. Open a billing ticket right now with Severity A. Include your Subscription ID and state clearly that the subscription shows as Deleted and you need emergency recovery. The Azure backend team can restore deleted subscriptions, but after 90 days the data is gone.
Policy-Blocked Resource Restart via Azure Policy
In enterprise environments, Azure Policy rules can prevent resources from restarting even after a subscription is re-enabled. If VMs or services fail to start and you see errors like "RequestDisallowedByPolicy" in the Activity log, check your assigned policies in Policy → Compliance. A common culprit is a policy that enforces specific VM SKUs or regions, if your resources were running a SKU that's now policy-blocked, you'll need to resize before restarting.
Call or ticket Microsoft Support immediately if: your subscription status shows Deleted, payment goes through but the subscription stays disabled after 6+ hours, you're on an EA or CSP agreement and can't find the right billing contact, or you're seeing unexplained charges you don't recognize (possible unauthorized access). For any situation involving potential fraud or unauthorized charges, escalate to severity A, don't try to self-service it through the portal.
Prevention & Best Practices
An Azure overdue payment suspension is one of those problems that almost never needs to happen twice. Once you've lived through the scramble of bringing services back online while stakeholders breathe down your neck, you never want to experience it again. Here's how to make sure you don't.
First, set up billing alerts. In Cost Management + Billing → Billing alerts, configure alerts for when your monthly spend hits 80% and 100% of your expected budget. These won't directly prevent a payment failure, but they ensure someone is watching the numbers every month. Pair this with an invoice alert, under Cost alerts, you can configure alerts that fire when a new invoice is generated, giving you immediate visibility without having to log in and check.
Second, use a corporate card or a dedicated virtual card for Azure billing, never a personal card with a spending limit that might not cover a surprise spike. Virtual cards issued by services like your corporate bank's expense platform are ideal because you can set per-vendor limits and get real-time spend notifications.
Third, keep your billing contact email up to date. Go to Cost Management + Billing → Properties on your billing account and verify the Bill-to contact email. This is where overdue notices go. If it's pointing to a generic alias or a former employee's address, payment warnings will never reach the right person.
Fourth, assign the Billing Reader role to your finance team in addition to your IT staff. Too often, IT manages the subscription but nobody in finance has visibility into Azure invoices until something goes wrong. Shared visibility means the finance team can flag payment issues before they become outages.
Finally, consider setting up Azure Cost Management budgets with auto-action. You can configure a budget that automatically triggers an email or a Logic App workflow when spending anomalies are detected, this gives you a fighting chance to catch runaway costs before the invoice balloons to a size that causes a payment failure on a card with a modest limit.
- Set a billing alert at 80% and 100% of your expected monthly spend in Cost Management → Cost alerts, takes 3 minutes to configure
- Verify your bill-to contact email quarterly, check Cost Management + Billing → Properties and make sure it reaches a real person
- Add a backup payment method and keep it current, Azure will attempt the backup card automatically if the primary fails
- Grant Billing Reader access to at least one person in your finance team so IT doesn't bear sole responsibility for catching invoice issues
Frequently Asked Questions
How long after paying the overdue balance will my Azure subscription be re-enabled?
For most pay-as-you-go subscriptions, re-enablement happens within 1 to 4 hours after a successful payment. In practice, I've seen it take as little as 20 minutes. If it's been more than 6 hours and the subscription still shows Disabled in the portal, open a support ticket, sometimes the reactivation pipeline gets stuck and needs a manual poke from the Azure billing team. Keep in mind that re-enabling the subscription doesn't auto-start your VMs or App Services; you'll need to restart those resources manually once the subscription is active again.
Will Azure delete my data if my subscription is suspended for too long?
Azure follows a specific data retention timeline after suspension. When a subscription is first disabled, your data and resources are preserved for 30 days in PastDue/Disabled status, you're just blocked from using them. After 30 days of non-payment with no action, the subscription transitions to Deleted state, which starts a 90-day countdown before Azure permanently purges all resources and data. That 90-day window is your last chance to recover, but you must open a billing support ticket and clear the balance. After the 90-day mark, nothing can be recovered. If you're anywhere near that window, treat it as a P1 incident.
I paid the invoice but the Azure portal still says my subscription is disabled, why?
This is more common than it should be. First, check that the invoice you paid now shows Paid under Cost Management + Billing → Invoices, sometimes there are multiple overdue invoices and you only paid the most recent one. Second, confirm the payment wasn't actually declined by checking the payment history tab on the invoice. Third, clear your browser cache and reload the portal, occasionally the portal shows stale subscription status cached in your session. If the invoice shows Paid and it's been more than 6 hours, contact billing support with your subscription ID and payment confirmation number.
Can I dispute an Azure charge while also getting my subscription re-enabled?
Yes, but you need to handle these as two separate requests in parallel. To get your subscription re-enabled quickly, pay the overdue balance first, Azure won't re-enable a subscription with an outstanding balance regardless of whether you believe the charges are correct. At the same time, open a separate billing support ticket with the label "Billing dispute" and document which line items you're contesting and why. Microsoft's billing team can issue credits or adjustments retroactively once the dispute is reviewed, typically within 30 days. Don't hold your subscription hostage to the dispute process, pay first, dispute simultaneously.
Why can't I find the "Pay Now" button in the Azure portal?
There are a few common reasons the Pay Now button is missing or greyed out. One: you're not signed in as the Account Administrator, only the account owner or billing account administrator role can settle invoices. Two: your subscription is a CSP or EA type, which doesn't support portal-based payments, you need to contact your CSP partner or EA billing contact instead. Three: your billing account type is Microsoft Customer Agreement (MCA), in which case the payment flow is under Billing profiles → [Your Profile] → Invoices, not the top-level subscription page. Four: the portal session is partially loaded, try opening Cost Management + Billing in a new InPrivate/Incognito window while signed in as the billing admin.
I'm getting "You don't have permission to view this billing account" when I try to fix the Azure overdue payment, what now?
This error means your Azure account doesn't have the Billing Account Owner or Billing Account Contributor role on the billing account. This is extremely common in organizations where one person set up the subscription and another person is now trying to manage it. You need to contact whoever originally created the Azure billing account and ask them to grant you the Billing Account Contributor role via Cost Management + Billing → Access control (IAM). If that person has left the organization and you can't reach them, you'll need to contact Microsoft Support directly, they can verify your identity through domain ownership and reassign billing account access. Have your domain admin credentials ready for that call.