SLA for Azure Site Recovery
Last updated: May 2018
- For each Protected Instance configured for On-Premises-to-On-Premises Failover, we guarantee at least 99.9% availability of the Site Recovery service. Availability is calculated over a monthly billing cycle.
- For each Protected Instance configured for On-Premises-to-Azure planned and unplanned Failover, we guarantee a two-hour Recovery Time Objective.
- For each Protected Instance configured for Azure-to-Azure Failover, we guarantee a two-hour Recovery Time Objective.
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;
- That result from connecting to a serverless database that is pausing, paused or resuming.
- 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.
- Your initiated operations such as restart, stop, start, failover, scale compute, and scale storage that incur downtime are excluded from the uptime calculation.
- Monthly maintenance window that incurs a downtime to patch your server and infrastructure is excluded from the uptime calculation.
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.”
"Failover" is the process of transferring control, either simulated or actual, of a Protected Instance from a primary site to a secondary site.
"On-Premises-to-Azure Failover" is the Failover of a Protected Instance from a non-Azure primary site to an Azure secondary site.
"Azure-to-Azure Failover" is the Failover of a Protected Instance from an Azure primary site to an Azure secondary site.
"On-Premises-to-On-Premises Failover" is the Failover of a Protected Instance from a non-Azure primary site to a non-Azure secondary site.
"Protected Instance" refers to a virtual or physical machine configured for replication by the Site Recovery Service from a primary site to a secondary site. Protected Instances are enumerated in the Protected Items tab in the Recovery Services section of the Management Portal.
Monthly Uptime Calculation and Service Levels for On-Premises-to-On-Premises Failover
"Maximum Available Minutes" is the total number of minutes that a given Protected Instance has been configured for On-Premises-to-On-Premises replication by the Site Recovery Service during a billing month.
"Failover Minutes" is the total number of minutes in a billing month during which a Failover of a Protected Instance configured for On-Premises-to-On-Premises replication has been attempted but not completed.
"Downtime" is the total accumulated Failover Minutes in which the Failover of a Protected Instance is unsuccessful due to unavailability of the Site Recovery Service, provided that retries are continually attempted no less frequently than once every thirty minutes.
"Monthly Uptime Percentage" for On-Premises-to-On-Premises Failover of a specific Protected Instance in a given billing month is calculated as Maximum Available Minutes less Downtime divided by Maximum Available Minutes. Monthly Uptime Percentage is represented by the following formula:
Monthly Uptime % = (Maximum Available Minutes - Downtime) / Maximum Available Minutes X 100
The following Service Levels and Service Credits are applicable to Customer’s use of each Protected Instance within the Site Recovery Service for On-Premises-to-On-Premises Failover:
|Monthly Uptime Percentage||Service Credit|
Monthly Recovery Time Objective and Service Levels for On-Premises-to-Azure Failover
"Recovery Time Objective (RTO)" means the period of time beginning when Customer initiates a Failover of a Protected Instance experiencing either a planned or unplanned outage for On-Premises-to-Azure replication to the time when the Protected Instance is running as a virtual machine in Microsoft Azure, excluding any time associated with manual action or the execution of Customer scripts.
"Monthly Recovery Time Objective" for a specific Protected Instance configured for On-Premises-to-Azure replication in a given billing month is 2 hours.
The following Service Levels and Service Credits are applicable to Customer’s use of each Protected Instance within the Site Recovery Service for On-Premises-to-Azure Failover.
|Monthly Recovery Time Objective||Service Credit|
|> 2 hours||100%|
Monthly Recovery Time Objective and Service Levels for Azure-to-Azure Failover
"Recovery Time Objective (RTO)" means the period of time beginning when Customer initiates a Failover of a Protected Instance for Azure-to-Azure replication to the time when the Protected Instance is running as a virtual machine in secondary Azure region, excluding any time associated with manual action or the execution of Customer scripts.
"Monthly Recovery Time Objective" for a specific Protected Instance configured for Azure-to-Azure replication in a given billing month is 2 hours.
The following Service Levels and Service Credits are applicable to Customer’s use of each Protected Instance within the Site Recovery Service for Azure-to-Azure Failover.
|Monthly Recovery Time Objective||Service Credit|
|> 2 hours||100%|