Guides / How to ask for a service credit
How to ask for a service credit
A request goes to the vendor or to your reseller, before a deadline that depends on the agreement. This guide lists the steps and quotes the deadline clauses. The vendor decides every claim, and these steps are this site's reading. Not legal advice.
Six steps
These steps are this site's reading of the four agreements below. Your own contract can differ.
- Find the agreement that applies to you. The sources at the end of this page link to the four agreements this site has read. If you bought through a reseller, ask the reseller which one applies.
- Check who files. Some agreements let you file with the vendor. Others send you to your reseller. The quotes below say which.
- Write down what happened. Note the start time, the end time, the service and the vendor's incident number if it gave one.
- Work out the period and the downtime. Each agreement counts uptime over a month or a quarter. The calculator does the sums in your browser.
- Check the deadline. The deadline is different in each agreement. See the table below.
- Send the request and keep a record. Save the request text, the numbers and the date you sent it.
Claim deadline in each agreement
Swipe sideways to see every column.
| Agreement | Claim deadline, from the agreement |
|---|---|
| Microsoft: Exchange Online | End of the calendar month following the month of the incident |
| Google Workspace | Within 30 days (counted here from the start of the downtime) |
| Atlassian Cloud | Within 15 days after the end of the calendar month |
| GitHub Enterprise Cloud | Within 30 days after the end of the calendar quarter |
Where to send it: the clauses
Each agreement says how and when to ask. The clauses are copied word for word.
Microsoft: Exchange Online
“For claims related to all other Services, we must receive the claim by the end of the Applicable Period following the month in which the Incident occurred. For example, if the Incident occurred on February 15th, we must receive the claim and all required information by March 31st.”
Service Level Agreement for Microsoft Online Services, dated 1 November 2026, last checked 12 November 2026.
“For claims related to all other services, credit requests must be submitted within one month from the end of the billing month in which the incident occurred.”
Microsoft Partner Center, dated 16 June 2026, last checked 12 November 2026. For customers who buy through a reseller.
Google Workspace
“Customer must notify Google (or, if Customer ordered Services from a Reseller, Customer must notify Customer's Reseller who must notify Google) by creating a support case within thirty days from the time Customer becomes eligible to receive a Service Credit.”
Google Workspace Service Level Agreement, dated 31 August 2026, last checked 13 November 2026.
“If Customer ordered Services from a Reseller and complies with this requirement, Customer will receive the applicable Service Credit from Customer's Reseller on behalf of Google.”
Google Workspace Service Level Agreement, dated 31 August 2026, last checked 13 November 2026.
Atlassian Cloud
“To be eligible to receive a service credit for Atlassian’s failure to meet the Service Level Commitment (“Service Credit”), Customer must submit a ticket at https://support.atlassian.com with all fields fully and accurately completed within fifteen (15) days after the end of the calendar month in which the alleged failure occurred and provide any other reasonably requested information or documentation (for instance, as described here). Atlassian’s monitoring and logging infrastructure is the sole source of truth for determining whether Atlassian has met the Service Level Commitment.”
Atlassian Cloud Service Level Agreement, dated 30 April 2026, last checked 13 November 2026.
“If Customer purchased the affected Cloud Product through a Reseller, (a) Customer or the Reseller may submit a ticket as described in Section 2.1 above; and (b) any Service Credit will be based on the fees invoiced by Atlassian to the Reseller for Customer’s use of the affected Cloud Product under the Reseller’s applicable order(s) with Atlassian. Atlassian will issue any associated Service Credits to the Reseller (and not directly to Customer), and the Reseller will be solely responsible for issuing the appropriate amounts to Customer.”
Atlassian Cloud Service Level Agreement, dated 30 April 2026, last checked 13 November 2026.
GitHub Enterprise Cloud
“Customer may redeem Service Credits only upon written request within thirty (30) days of the end of the Applicable Period. Written requests for Service Credits should be sent either (a) to GitHub Support if Customer purchases directly from GitHub, or (b) through a Microsoft support ticket if Customer purchases SLA-covered Services through Microsoft.”
GitHub Online Services SLA, dated 1 June 2026, last checked 13 November 2026.
What Microsoft asks a claim to include
“(i) a detailed description of the Incident; (ii) information regarding the time and duration of downtime; (iii) affected resource names; (iv) the number and location(s) of affected users; and v) a description of errors that occurred during the incident. Failure to provide the required information will result in claims being rejected.”
Service Level Agreement for Microsoft Online Services, dated 1 November 2026, last checked 12 November 2026.
Sources
- Service Level Agreement for Microsoft Online Services, dated 1 November 2026, read 12 November 2026
- Google Workspace Service Level Agreement, dated 31 August 2026, read 13 November 2026
- Atlassian Cloud Service Level Agreement, dated 30 April 2026, read 13 November 2026
- GitHub Online Services SLA, dated 1 June 2026, read 13 November 2026
- Microsoft Partner Center: request a credit, dated 16 June 2026, read 12 November 2026
Quotations are copied word for word from the agreement named under each one. Text outside a quotation is this site's reading. A vendor decides every claim. This is not legal advice.