No Support Plan Needed: Claiming SLA Credits on AWS, Azure, GCP and DigitalOcean
October 20, 2026
Cloud SLA credits are filed through billing channels, not technical support, which means you never have to pay for a support plan to collect what an outage already owes you. AWS bundles Basic support with every account and its SLAs route claims through the Support Center. Azure includes billing and subscription management support for all customers, and credit requests are submitted as billing tickets. Google Cloud and DigitalOcean have no support-tier requirement at all. If you have been assuming claims need a paid plan, that assumption has been quietly costing you money.
Where the misconception comes from
The confusion is understandable. Azure really does gate technical support behind paid plans, and AWS tells you to "open a case in the AWS Support Center", which sounds like it belongs to the paid-support world. Neither fact applies to credit claims.
A credit claim is a billing matter. AWS's own SLA text says to open a case, and Basic accounts can open cases in the Support Center. Azure's support plan comparison shows billing and subscription management support, plus unlimited billing tickets, included at every tier including the free Basic one. The claim never enters the technical support queue. It goes to the billing team, which is free for every customer of every one of the four providers.
| Provider | Claim channel | Paid plan needed | Filing window |
|---|---|---|---|
| AWS | Support Center case with "SLA Credit Request" in the subject | No. Basic support is included with every account | By the end of the second billing cycle after the incident |
| Azure | Portal: Help + support, Issue type Billing, Problem type Refund Request | No. Billing support is included for all customers | Within 60 days of the incident |
| Google Cloud | Cloud Platform SLA contact form | No | Within 60 days of eligibility (30 days for some services) |
| DigitalOcean | Email success@digitalocean.com | No | Within two billing cycles of the outage month |
AWS: a Support Center case, not a paid support plan
Every AWS SLA says the same thing about how to claim: open a case in the AWS Support Center, with "SLA Credit Request" in the subject line, your 12-digit account ID, the billing cycle, the region, the dates and times of each impacted period, and request logs that show the errors hitting your resources. Basic support is included for all AWS customers, so nothing needs to be purchased to open that case.
The deadline is the end of the second billing cycle after the incident. An outage on October 3 lands in the October billing cycle, which closes October 31, so the claim must be in before the end of December. AWS pays confirmed claims as a credit within one billing cycle of confirmation, and it does not pay credits under $1.
A paid AWS plan buys faster technical response and more tooling. It does not buy the right to claim. The credit tiers, the $1 floor and the deadline are identical whether you run on Basic or on Business Support+.
Azure: the credit request is a billing ticket
Azure is the provider where the misconception does the most damage, because its technical support genuinely does sit behind paid plans. Read the support plan comparison and the opposite is true for claims: billing and subscription management support is included for all customers, and the SLA credit request is filed as a billing ticket.
In the portal, open Help + support, create a new support request with Issue type set to Billing and Problem type set to Refund Request, and state in the description that this is an SLA credit request. Include the impacted services, the date, time and time zone of the outage, the incident ID from Service Health history, and your subscription and tenant details.
File within 60 days of the incident. If you bought through a CSP partner, request the credit through your partner rather than the portal; Microsoft routes those claims through Partner Center. Approved credits appear on the next invoice and are capped at the monthly fee for the affected service, and planned maintenance and issues outside Microsoft's control do not qualify.
Google Cloud: a contact form, no tier required
GCP calls its credits financial credits. The Compute Engine SLA states the process plainly: notify Google technical support within 60 days of becoming eligible, using the Cloud Platform SLA contact form, and provide log files showing the downtime periods with dates and times. No support tier is required to use that form.
The window is per service. Compute Engine currently allows 60 days from eligibility, while several other services keep the older 30-day window, so check the SLA for the service that failed rather than assuming the clock. Google applies approved credits within 60 days of the request, capped at the monthly bill for the affected service in the affected region, and any outage caused by your own actions or by quotas does not count.
DigitalOcean: an email, nothing to buy
DigitalOcean does not sell support plans at all, so there is no gate to trip over. Email success@digitalocean.com within two billing cycles of the month the downtime occurred, with the email address on the account, the affected Droplet or resource details, and the outage dates and times. Credits land within one billing cycle.
The claim channel is billing, not technical support. Every major cloud provider lets you file an SLA credit claim without a paid support plan. What actually kills claims is the deadline, the missing evidence, and never filing at all.
The money math: buying a plan to claim is paying for nothing
A support plan exists to give you faster technical help. It does not open any claims that are not already open on any of the four providers. If the only reason you were going to buy one was to file credit requests, here is what that purchase would buy you:
| Support plan | Monthly price | SLA claims it opens up |
|---|---|---|
| AWS Business Support+ | from $29/month per account, or a percentage of usage | None. Basic already files claims |
| Azure Developer | $29/month | None. Billing support is already free |
| Azure Standard | $100/month | None |
| Azure ProDirect | $1,000/month | None |
| Google Cloud / DigitalOcean | no equivalent | Nothing to buy |
Run the numbers on a real claim. A 10% credit on a $2,000/month EC2 bill in the breached region is $200. The cheapest AWS plan that would not have opened that door costs from $348 a year. On Azure the gap is wider: Standard runs $1,200 a year for exactly the same nothing. The credit you collect pays you; the plan only pays the provider.
What claiming actually costs you
The real cost of a claim is not a plan. It is five things you can assemble in an afternoon:
- The incident ID or health dashboard entry for the outage, from the provider's status history.
- Timestamps in UTC covering the full impact window.
- Your own request logs that show the errors (AWS and GCP explicitly ask for these).
- The right channel and wording so the ticket routes to the billing team, not the technical queue.
- A calendar reminder before the window closes. AWS's end-of-second-cycle and GCP's 30 or 60 days are the ones people miss.
File one claim this month
Pick the last real outage you experienced, open the billing channel for that provider, and submit before the window closes. The plan you were about to buy is the one you do not need. If you have no logs for that last outage because nothing was watching, start monitoring now so the next one captures the window automatically; that is the part actually worth spending on.