This is an outdated version of this SLA. Click here to view the current version of this SLA.
SLA for Storage Accounts
Last updated: December 2017
- We guarantee that at least 99.99% (99.9% for Cool Access Tier) of the time, we will successfully process requests to read data from Read Access-Geo Redundant Storage (RA-GRS) Accounts, provided that failed attempts to read data from the primary region are retried on the secondary region.
- We guarantee that at least 99.9% (99% for Cool Access Tier) of the time, we will successfully process requests to read data from Locally Redundant Storage (LRS), Zone Redundant Storage (ZRS), and Geo Redundant Storage (GRS) Accounts.
- We guarantee that at least 99.9% (99% for Cool Access Tier) of the time, we will successfully process requests to write data to Locally Redundant Storage (LRS), Zone Redundant Storage (ZRS), and Geo Redundant Storage (GRS) Accounts and Read Access-Geo Redundant Storage (RA-GRS) Accounts.
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.”
"Average Error Rate" for a billing month is the sum of Error Rates for each hour in the billing month divided by the total number of hours in the billing month.
"Blob Storage Account" is a storage account specialized for storing data as blobs and provides the ability to specify an access tier indicating how frequently the data in that account is accessed.
"Cool Access Tier" is an attribute of a blob or account indicating it is infrequently accessed and has a lower availability service level than blobs in Hot Access Tier.
"Hot Access Tier" is an attribute of a blob or account indicating it is frequently accessed.
"Excluded Transactions" are storage transactions that do not count toward either Total Storage Transactions or Failed Storage Transactions. Excluded Transactions include pre-authentication failures; authentication failures; attempted transactions for storage accounts over their prescribed quotas; creation or deletion of containers, file shares, tables, or queues; clearing of queues; and copying blobs or files between storage accounts.
"Error Rate" is the total number of Failed Storage Transactions divided by the Total Storage Transactions during a set time interval (currently set at one hour). If the Total Storage Transactions in a given one-hour interval is zero, the error rate for that interval is 0%.
"Failed Storage Transactions" is the set of all storage transactions within Total Storage Transactions that are not completed within the Maximum Processing Time associated with their respective transaction type, as specified in the table below. Maximum Processing Time includes only the time spent processing a transaction request within the Storage Service and does not include any time spent transferring the request to or from the Storage Service.
|Transaction Types||Maximum Processing Time|
|PutBlob and GetBlob (includes blocks and pages)
Get Valid Page Blob Ranges
|Two (2) seconds multiplied by the number of MBs transferred in the course of processing the request.|
|PutFile and GetFile||Two (2) seconds multiplied by the number of MBs transferred in the course of processing the request.|
|Copy Blob||Ninety (90) seconds (where the source and destination blobs are within the same storage account).|
|Copy File||Ninety (90) seconds (where the source and destination files are within the same storage account).|
|Sixty (60) seconds.|
|Ten (10) seconds (to complete processing or return a continuation)|
|Batch Table Operations||Thirty (30) seconds|
|All Single Entity Table Operations
All other Blob, File and Message Operations
|Two (2) seconds|
These figures represent maximum processing times. Actual and average times are expected to be much lower.
Failed Storage Transactions do not include:
- Transaction requests that are throttled by the Storage Service due to a failure to obey appropriate back-off principles.
- Transaction requests having timeouts set lower than the respective Maximum Processing Times specified above.
- Read transactions requests to RA-GRS Accounts for which you did not attempt to execute the request against Secondary Region associated with the storage account if the request to the Primary Region was not successful.
- Read transaction requests to RA-GRS Accounts that fail due to Geo-Replication Lag.
"Geo Replication Lag" for GRS and RA-GRS Accounts is the time it takes for data stored in the Primary Region of the storage account to replicate to the Secondary Region of the storage account. Because GRS and RA-GRS Accounts are replicated asynchronously to the Secondary Region, data written to the Primary Region of the storage account will not be immediately available in the Secondary Region. You can query the Geo Replication Lag for a storage account, but Microsoft does not provide any guarantees as to the length of any Geo Replication Lag under this SLA.
"Geographically Redundant Storage (GRS) Account" is a storage account for which data is replicated synchronously within a Primary Region and then replicated asynchronously to a Secondary Region. You cannot directly read data from or write data to the Secondary Region associated with GRS Accounts.
"Locally Redundant Storage (LRS) Account" is a storage account for which data is replicated synchronously only within a Primary Region.
"Primary Region" is a geographical region in which data within a storage account is located, as selected by you when creating the storage account. You may execute write requests only against data stored within the Primary Region associated with storage accounts.
"Read Access Geographically Redundant Storage (RA-GRS) Account" is a storage account for which data is replicated synchronously within a Primary Region and then replicated asynchronously to a Secondary Region. You can directly read data from, but cannot write data to, the Secondary Region associated with RA-GRS Accounts.
"Secondary Region" is a geographical region in which data within a GRS or RA-GRS Account is replicated and stored, as assigned by Microsoft Azure based on the Primary Region associated with the storage account. You cannot specify the Secondary Region associated with storage accounts.
"Total Storage Transactions" is the set of all storage transactions, other than Excluded Transactions, attempted within a one-hour interval across all storage accounts in the Storage Service in a given subscription.
"Zone Redundant Storage (ZRS) Account" is a storage account for which data is replicated across multiple facilities. These facilities may be within the same geographical region or across two geographical regions.
Monthly Uptime Percentage: Monthly Uptime Percentage is calculated using the following formula:
100% - Average Error Rate
Service Credit – Hot Blobs in LRS, ZRS, GRS and RA-GRS (write requests) Accounts:
|Monthly Uptime Percentage||Service Credit|
Service Credit – Hot Blobs in RA-GRS (read requests) Accounts:
|Monthly Uptime Percentage||Service Credit|
Service Credit – Cool Blobs in LRS, GRS, RA-GRS (write requests) Accounts:
|Monthly Uptime Percentage||Service Credit|
Service Credit – Cool Blobs in RA-GRS (read requests) Accounts:
|Monthly Uptime Percentage||Service Credit|
1.5 Last updated: June 2019
Release notes: Addition of files in storage accounts to the list of features covered by uptime guarantee.
1.4 Last updated: March 2019
Release notes: Updated SLA for the newly introduced Block Blob Storage Accounts.
1.3 Last updated: December 2017
Release notes: Updated “Cool Access Tier” and added “Hot Access Tier” definitions.
1.2 Last updated: April 2017
Release notes: Updated SLA to reflect guarantees for Azure File Storage.
1.1 Last updated: April 2016
Release notes: Updated SLA for the newly introduced Blob Storage Accounts with the Cool Access Tier.
1.0 Last updated: May 2015