SaaS terms · Service-level agreements
An uptime promise is only as useful as its credit clause
An SLA can describe availability precisely and still provide a narrow remedy. Read the measured service, exclusions, claim deadline, fee base and maximum credit as one chain before relying on an uptime number.
Read the SLA beside its definitions
Five fields keep an SLA promise honest
Measured service
Which product, tier, resource or users are covered? “Platform availability” is not automatically every feature your team uses.
Availability rule
Find the downtime definition and calculation period. Scheduled maintenance or a user-minute formula can change the result.
Exclusions
List preview tiers, customer changes, third-party failures, planned work and other exclusions. An outage notice alone may not prove a missed level.
Claim window
Record who must claim, what incident evidence is required and the deadline. A missed written clock can end the remedy even when downtime occurred.
Credit base and ceiling
Identify the affected service or resource fees and the maximum credit. A service credit may not cover lost revenue or other indirect loss.
Primary-source case study · Microsoft Online Services SLA
The percentage is not the whole remedy
Microsoft's consolidated Online Services SLA page lists an English edition dated November 1, 2026. Its general terms say a customer may be eligible for a credit if a service level is missed, but the claim must include incident details and supporting information. The exact service-specific table still controls.
| Read this field | Question to ask | Why it matters |
|---|---|---|
| Applicable Period | Is it the calendar month, or the 30 days before the incident? | The same downtime can land in a different fee window. |
| Claim evidence | Do I need duration, affected resources, users and error details? | Missing information can cause a claim to be rejected. |
| Deadline | Is the claim due within 60 days or by the end of the following period? | A valid incident can still miss the written clock. |
| Credit ceiling | Is the maximum the fees for that service or resource? | The remedy may exclude lost revenue and other indirect loss. |
Worked reading, not a calculation: if a contract defines an applicable month, limits credits to fees for the affected service and requires a claim by the following period's end, do not turn a headline “99.9%” into a refund of the whole account. First identify the measured service, then preserve the required incident record.
Make a traceable incident note
- What failed? Name the service, tier, resource, users and time zone. Save the exact status or error evidence beside the contract version.
- What counts? Compare the event with the SLA's downtime definition and exclusions. Mark uncertainty instead of treating every slow response as downtime.
- What is the clock? Write the claim recipient, required fields, deadline and applicable fee period. Keep the date you sent the claim.
- What is the remedy? Record the service-credit formula, affected-fee base and cap. A credit can reduce a future bill without covering business interruption.
Return to the SaaS terms guide for renewal, export, suspension and liability questions. This page helps read existing wording; it does not monitor uptime or submit a claim.
Sources and limits
A provider SLA, not a worldwide rule
- Microsoft Licensing: Service Level Agreements (SLA) for Online Services. Page consulted November 7, 2026; English edition dated November 1, 2026.
- Microsoft Online Services consolidated SLA, English, November 2026. General definitions and claims section consulted November 7, 2026.
TermsHuman explains common contract language and risk patterns for education only. It is not a law firm, does not provide legal advice, and cannot tell you whether to sign. For material obligations, ask qualified counsel in your jurisdiction.