SLA for Azure SQL Database
Last updated: November 2020
Azure SQL Database is a fully managed relational database with built-in regional high availability and turnkey geo-replication to any Azure region. It includes intelligence to support self-driving features such as performance tuning, threat monitoring, and vulnerability assessments and provides fully automated patching and updating of the code base.
- Azure SQL Database Business Critical or Premium tiers configured as Zone Redundant Deployments have an availability guarantee of at least 99.995%.
- Azure SQL Database Business Critical or Premium tiers not configured for Zone Redundant Deployments, General Purpose, Standard, or Basic tiers, or Hyperscale tier with two or more replicas have an availability guarantee of at least 99.99%.
- Azure SQL Database Hyperscale tier with one replica has an availability guarantee of at least 99.95% and 99.9% for zero replicas.
- Azure SQL Database Business Critical tier configured with geo-replication has a guarantee of Recovery point objective (RPO) of 5 sec for 100% of deployed hours.
- Azure SQL Database Business Critical tier configured with geo-replication has a guarantee of Recovery time objective (RTO) of 30 sec for 100% of deployed hours.
This Service Level Agreement for Microsoft Online Services (this “SLA”) is a part of your Microsoft volume licensing agreement (the “Agreement”). Capitalized terms used but not defined in this SLA will have the meaning assigned to them in the Agreement. This SLA applies to the Microsoft Online Services listed herein (a “Service” or the “Services”), but does not apply to separately branded services made available with or connected to the Services or to any on-premises software that is part of any Service.
If we do not achieve and maintain the Service Levels for each Service as described in this SLA, then you may be eligible for a credit towards a portion of your monthly service fees. We will not modify the terms of your SLA during the initial term of your subscription; however, if you renew your subscription, the version of this SLA that is current at the time of renewal will apply throughout your renewal term. We will provide at least 90 days’ notice for adverse material changes to this SLA.
"Applicable Monthly Period" means, for a calendar month in which a Service Credit is owed, the number of days that you are a subscriber for a Service.
"Applicable Monthly Service Fees" means the total fees actually paid by you for a Service that are applied to the month in which a Service Credit is owed.
"Downtime" is defined for each Service in the Services Specific Terms below.
"Error Code" means an indication that an operation has failed, such as an HTTP status code in the 5xx range.
"External Connectivity" is bi-directional network traffic over supported protocols such as HTTP and HTTPS that can be sent and received from a public IP address.
"Incident" means (i) any single event, or (ii) any set of events, that result in Downtime.
"Management Portal" means the web interface, provided by Microsoft, through which customers may manage the Service.
"Service Credit" is the percentage of the Applicable Monthly Service Fees credited to you following Microsoft’s claim approval.
"Service Level" means the performance metric(s) set forth in this SLA that Microsoft agrees to meet in the delivery of the Services.
"Service Resource" means an individual resource available for use within a Service.
"Success Code" means an indication that an operation has succeeded, such as an HTTP status code in the 2xx range.
"Support Window" refers to the period of time during which a Service feature or compatibility with a separate product or service is supported.
In order for Microsoft to consider a claim, you must submit the claim to customer support at Microsoft Corporation including all information necessary for Microsoft to validate the claim, including but not limited to: (i) a detailed description of the Incident; (ii) information regarding the time and duration of the Downtime; (iii) the number and location(s) of affected users (if applicable); and (iv) descriptions of your attempts to resolve the Incident at the time of occurrence.
For a claim related to Microsoft Azure, we must receive the claim within two months of the end of the billing month in which the Incident that is the subject of the claim occurred. For claims related to all other Services, we must receive the claim by the end of the calendar month 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.
We will evaluate all information reasonably available to us and make a good faith determination of whether a Service Credit is owed. We will use commercially reasonable efforts to process claims during the subsequent month and within forty-five (45) days of receipt. You must be in compliance with the Agreement in order to be eligible for a Service Credit. If we determine that a Service Credit is owed to you, we will apply the Service Credit to your Applicable Monthly Service Fees.
If you purchased more than one Service (not as a suite), then you may submit claims pursuant to the process described above as if each Service were covered by an individual SLA. For example, if you purchased both Exchange Online and SharePoint Online (not as part of a suite), and during the term of the subscription an Incident caused Downtime for both Services, then you could be eligible for two separate Service Credits (one for each Service), by submitting two claims under this SLA. In the event that more than one Service Level for a particular Service is not met because of the same Incident, you must choose only one Service Level under which to make a claim based on the Incident. Unless as otherwise provided in a specific SLA, only one Service Credit is permitted per Service for an Applicable Monthly Period.
Service Credits are your sole and exclusive remedy for any performance or availability issues for any Service under the Agreement and this SLA. You may not unilaterally offset your Applicable Monthly Service Fees for any performance or availability issues.
Service Credits apply only to fees paid for the particular Service, Service Resource, or Service tier for which a Service Level has not been met. In cases where Service Levels apply to individual Service Resources or to separate Service tiers, Service Credits apply only to fees paid for the affected Service Resource or Service tier, as applicable. The Service Credits awarded in any billing month for a particular Service or Service Resource will not, under any circumstance, exceed your monthly service fees for that Service or Service Resource, as applicable, in the billing month.
If you purchased Services as part of a suite or other single offer, the Applicable Monthly Service Fees and Service Credit for each Service will be pro-rated.
If you purchased a Service from a reseller, you will receive a service credit directly from your reseller and the reseller will receive a Service Credit directly from us. The Service Credit will be based on the estimated retail price for the applicable Service, as determined by us in our reasonable discretion.
This SLA and any applicable Service Levels do not apply to any performance or availability issues:
- Due to factors outside our reasonable control (for example, natural disaster, war, acts of terrorism, riots, government action, or a network or device failure external to our data centers, including at your site or between your site and our data center);
- That result from the use of services, hardware, or software not provided by us, including, but not limited to, issues resulting from inadequate bandwidth or related to third-party software or services;
- Caused by your use of a Service after we advised you to modify your use of the Service, if you did not modify your use as advised;
- During or with respect to preview, pre-release, beta or trial versions of a Service, feature or software (as determined by us) or to purchases made using Microsoft subscription credits;
- That result from your unauthorized action or lack of action when required, or from your employees, agents, contractors, or vendors, or anyone gaining access to our network by means of your passwords or equipment, or otherwise resulting from your failure to follow appropriate security practices;
- That result from your failure to adhere to any required configurations, use supported platforms, follow any policies for acceptable use, or your use of the Service in a manner inconsistent with the features and functionality of the Service (for example, attempts to perform operations that are not supported) or inconsistent with our published guidance;
- That result from faulty input, instructions, or arguments (for example, requests to access files that do not exist);
- That result from your attempts to perform operations that exceed prescribed quotas or that resulted from our throttling of suspected abusive behavior;
- Due to your use of Service features that are outside of associated Support Windows; or
- For licenses reserved, but not paid for, at the time of the Incident.
Services purchased through Open, Open Value, and Open Value Subscription volume licensing agreements, and Services in an Office 365 Small Business Premium suite purchased in the form of a product key are not eligible for Service Credits based on service fees. For these Services, any Service Credit that you may be eligible for will be credited in the form of service time (i.e., days) as opposed to service fees, and any references to “Applicable Monthly Service Fees” is deleted and replaced by “Applicable Monthly Period.”
"Availability Zone" is a fault-isolated area within an Azure region, providing redundant power, cooling, and networking.
"Database" means any Microsoft Azure SQL Database created in any of the Service tiers and deployed either as a single database or in an Elastic Pool.
"Zone Redundant Deployment" is a Database that is deployed across multiple Availability Zones.
"Primary" means any Database that has active geo-replication relationship with a Database in other Azure regions. Primary can process read and write requests from the application.
"Secondary" means any Database that maintains asynchronous geo-replication relationship with a Primary in another Azure region and can be used as a failover target. Secondary can process read-only requests from applications.
"Compliant Secondary" means any Secondary that is created with the same configuration and in the same service tier as the Primary. If the Secondary is created in an elastic pool, it is considered Compliant if both Primary and Secondary are created in elastic pools with matching configurations and with density not exceeding 250 databases for a compliant configuration.
Monthly Uptime Calculation and Service Levels for Azure SQL Database Service
"Deployment Minutes" is the total number of minutes that a given Database has been operational in Microsoft Azure during a billing month.
"Maximum Available Minutes" is the sum of all Deployment Minutes for a given Microsoft Azure subscription during a billing month.
"Downtime" is the total accumulated Deployment Minutes across all Databases in a given Microsoft Azure subscription during which the Database is unavailable. A minute is considered unavailable for a given Database if all continuous attempts by Customer to establish a connection to the Database within the minute fail.
"Monthly Uptime Percentage" for a given Database is calculated as Maximum Available Minutes less Downtime divided by Maximum Available Minutes in a billing month for a given Microsoft Azure subscription. Monthly Uptime Percentage is represented by the following formula:
Monthly Uptime %= 100 * (Maximum Available Minutes-Downtime) / Maximum Available Minutes
The following Service Levels and Service Credits are applicable to Customer’s use of the Business critical or Premium tiers of the SQL Database Service configured for Zone Redundant Deployments:
|Monthly Uptime Percentage||Service Credit|
The following Service Levels and Service Credits are applicable to Customer’s use of the Business critical or Premium tiers of the SQL Database Service not configured for Zone Redundant Deployments:
|Monthly Uptime Percentage||Service Credit|
The following Service Levels and Service Credits are applicable to Customer’s use of the General purpose, Standard or Basic tiers of the SQL Database Service:
|Monthly Uptime Percentage||Service Credit|
The following Service Levels and Service Credits are applicable to Customer’s use of the Hyperscale tier of the SQL Database Service.
|Provisioned Replicas||Monthly Uptime Percentage||Service Credit|
Recovery Point Objective (RPO)
"Geo-Replication Link" is a programmatic object representing a connection between a specific Primary and the Secondary.
"Geo-Replication Lag" is a time span from the point of transaction commit on the Primary and the acknowledgement by the Secondary that the transaction log update has been persisted.
"Replication Lag Check" is a programmatic method of obtaining the Geo-Replication Lag value for a specific Geo-Replication Link.
"Recovery Point Objective (RPO)" means a Geo-Replication Lag not to exceed 5 seconds.
"N" is the number of Replication Lag Check for a given Geo-Replication Link in a given hour.
"S" is the lag-sorted set of Replication Lag Check results in ascending order for a given Geo-Replication Link in a given hour.
"Ordinal Rank" is the 99th percentile using the nearest rank method represented by the following formula:
Ordinal Rank = (99 / 100) * N
"P99 Replication Lag" is the value at the Ordinal Rank of S.
"Deployment Hours" is the total number of hours that a given Compliant Secondary has been operational for a given Microsoft Azure subscription during a billing month.
"Excessive Lag Hours" is the total number of one-hour intervals during which Replication Lag Check resulted in a P99 Replication Lag greater than or equal to RPO for a given Microsoft Azure subscription during a billing month. If the number of Replication Lag Checks in a given one-hour interval is zero, the Excessive Lag Hours for that interval is 0.
"Monthly RPO Attainment Percentage" for a given Database deployment is calculated using the following formula:
100% - (Excessive Lag Hours / Deployment hours) *100
The following Service Levels and Service Credits are applicable to Customer’s use of the active geo-replication feature with Business Critical tier of Azure SQL Database service with a Compliant Secondary:
|Operation||RPO||Monthly RPO attainment percentage||Service credit|
|GEO-REPLICATION||5 sec||< 100%||10% of total monthly cost of Compliant Secondary|
Recovery Time Objective (RTO)
"Unplanned Failover" is an action initiated by Customer when the Primary is offline to enable a Compliant Secondary as Primary.
"Recovery Time" is the time elapsed from the Unplanned Failover until the Secondary is acting as the Primary.
"Recovery Time Objective (RTO)" means a maximum allowed Recovery Time not to exceed 30 seconds.
"Non-compliant Unplanned Failover" is an Unplanned Failover that failed to complete within the RTO.
"Monthly RTO Attainment Percentage" for a given Database deployment, in a billing month for a given subscription is represented by the following formula:
(Total number of Unplanned Failovers – Total number of Non-compliant Unplanned Failovers) / Total number of Unplanned Failovers* 100
The following Service Levels and Service Credits are applicable to Customer’s use of the active geo-replication feature with Business Critical service tier of SQL Database service with a Compliant Secondary:
|Operation||RTO||Monthly RTO attainment percentage||Service credit|
|UNPLANNED FAILOVER OF SINGLE DATABASE||30 sec||< 100%||100% of total monthly cost of Compliant Secondary|
1.5 Last updated: November 2020
Release notes: Removed managed instance into a separate SLA for Azure SQL Managed Instance.
1.4 Last updated: July 2019
1.3 Last updated: July 2019
Release notes: Expanded SLA to include guarantees for RPO and RTO. Addition of guarantees for availability <95%.
1.2 Last updated: May 2019
Release notes: Expanded SLA to cover Business Critical, Premium, and Hyperscale tiers of SQL Database. Removed references to Web and Business Tiers, since they have been retired.
1.1 Last updated: May 2016
Release notes: Revised to reflect the general availability of Elastic Database on 5/1/2016
1.0 Last updated: May 2015