Updating SLA (#36974)

Author: MashaMSFT

azure-sql/azure-sql-iaas-vs-paas-what-is-overview.md

@@ -64,7 +64,7 @@ Spend more time innovating and less time patching, updating, and backing up your
 Azure constantly monitors your data for threats. With Azure SQL, you can:
 
 - Remediate potential threats in real time with intelligent [advanced threat detection](/azure/security/fundamentals/threat-detection#threat-protection-features-other-azure-services) and proactive vulnerability assessment alerts.
-- Get industry-leading, multi-layered protection with [built-in security controls](https://azure.microsoft.com/overview/security/) including T-SQL, authentication, networking, and key management.
+- Get industry-standard, multi-layered protection with [built-in security controls](https://azure.microsoft.com/overview/security/) including T-SQL, authentication, networking, and key management.
 - Take advantage of the most comprehensive [compliance](https://azure.microsoft.com/overview/trusted-cloud/compliance/) coverage of any cloud database service.
 
 ### Business motivations
@@ -73,7 +73,7 @@ There are several factors that can influence your decision to choose between the
 
 - [Cost](#cost): Both platform as a service (PaaS) and infrastructure as a service (IaaS) options include a base price that covers the underlying infrastructure and licensing. However, with the IaaS option you need to invest extra time and resources to manage your database, while in PaaS you get administration features included in the price. Both PaaS and IaaS options give you the ability to pause your resources to help reduce administration costs.
 - [Administration](#administration): PaaS options reduce the amount of time that you need to invest to administer the database. However, it also limits the range of custom administration tasks and scripts that you can perform or run. For example, CLR isn't supported with SQL Database, but is supported in SQL Managed Instance.
-- [Service-level agreement](#service-level-agreement-sla): Both IaaS and PaaS provide high industry-standard SLAs. PaaS options guarantee 99.99% SLA, while IaaS guarantees 99.95% SLA for the infrastructure, which means you also need to implement additional mechanisms to ensure the availability of your databases. You can attain 99.99% SLA by creating an additional SQL virtual machine, and implementing the [SQL Server Always On availability group](virtual-machines/windows/availability-group-azure-portal-configure.md) high availability solution.
+- [Service-level agreement](#service-level-agreement-sla): Both IaaS and PaaS provide high industry-standard SLAs. PaaS options have a higher guaranteed SLA than IaaS, especially when implementing zone redundancy for either [Azure SQL Database](database/high-availability-sla-local-zone-redundancy.md) or [Azure SQL Managed Instance](managed-instance/high-availability-sla-local-zone-redundancy.md). IaaS guarantees SLA for the infrastructure, which means you also need to implement additional mechanisms to ensure the availability of your databases. You can attain higher SLAs by creating an additional SQL virtual machine, and implementing the [SQL Server Always On availability group](virtual-machines/windows/availability-group-azure-portal-configure.md) high availability solution.
 - [Time to move to Azure](#market): SQL Server on Azure VMs are an exact match of your environment, so migration from on-premises to the Azure VM is no different than moving the databases from one on-premises server to another. SQL Managed Instance also enables easy migration; however, there might be some changes that you need to apply before your migration.
 
 ## Service comparison
@@ -129,7 +129,7 @@ In general, SQL Database and SQL Managed Instance can dramatically increase the
 
 | Azure SQL Database | Azure SQL Managed Instance | SQL Server on Azure VMs |
 | :--- | :--- | :--- |
-| Supports most on-premises database-level capabilities. The most commonly used SQL Server features are available.<br />99.995% availability guaranteed.<br />Built-in backups, patching, recovery.<br />Latest stable Database Engine version.<br />Ability to assign necessary resources (CPU/storage) to individual databases.<br />Built-in advanced intelligence and security.<br />Online change of resources (CPU/storage). | Supports almost all on-premises instance-level and database-level capabilities. High compatibility with SQL Server.<br />99.99% availability guaranteed.<br />Built-in backups, patching, recovery.<br />Latest stable Database Engine version.<br />Easy migration from SQL Server.<br />Private IP address within Azure Virtual Network.<br />Built-in advanced intelligence and security.<br />Online change of resources (CPU/storage). | You have full control over the SQL Server engine. Supports all on-premises capabilities.<br />Up to 99.99% availability.<br />Full parity with the matching version of on-premises SQL Server.<br />Easy migration from SQL Server.<br />Private IP address within Azure Virtual Network.<br />You have the ability to deploy application or services on the host where SQL Server is placed.<br />Manage your SQL Server VM from the Azure portal and unlock a number of additional benefits when you register with the [Windows SQL Server IaaS Agent extension](virtual-machines/windows/sql-server-iaas-agent-extension-automate-management.md). |
+| Supports most on-premises database-level capabilities. The most commonly used SQL Server features are available.<br /> [Enterprise class SLA](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services?lang=1) increased through [zone redundancy](database/high-availability-sla-local-zone-redundancy.md).<br />Built-in backups, patching, recovery.<br />Latest stable Database Engine version.<br />Ability to assign necessary resources (CPU/storage) to individual databases.<br />Built-in advanced intelligence and security.<br />Online change of resources (CPU/storage). | Supports almost all on-premises instance-level and database-level capabilities. High compatibility with SQL Server.<br /> [Enterprise class SLA](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services?lang=1) increased through [zone redundancy](managed-instance/high-availability-sla-local-zone-redundancy.md).<br />Built-in backups, patching, recovery.<br />Latest stable Database Engine version.<br />Easy migration from SQL Server.<br />Private IP address within Azure Virtual Network.<br />Built-in advanced intelligence and security.<br />Online change of resources (CPU/storage). | You have full control over the SQL Server engine. Supports all on-premises capabilities.<br />[Enterprise class SLA](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services?lang=1) increased through [availability zones or availability sets](virtual-machines/windows/business-continuity-high-availability-disaster-recovery-hadr-overview.md#important-considerations-for-sql-server-hadr-in-azure)<br />Full parity with the matching version of on-premises SQL Server.<br />Easy migration from SQL Server.<br />Private IP address within Azure Virtual Network.<br />You have the ability to deploy application or services on the host where SQL Server is placed.<br />Manage your SQL Server VM from the Azure portal and unlock a number of additional benefits when you register with the [Windows SQL Server IaaS Agent extension](virtual-machines/windows/sql-server-iaas-agent-extension-automate-management.md). |
 | Some SQL Server features aren't available. Migration from SQL Server might be challenging for existing applications with operating system or SQL Agent dependencies. <br />Configurable [maintenance windows](database/maintenance-window.md).<br />Compatibility with the SQL Server version can be achieved only using database compatibility levels.<br />Private IP address support with [Azure Private Link](database/private-endpoint-overview.md). | Very few SQL Server features aren't available in Azure SQL Managed Instance.<br />Configurable [maintenance windows](database/maintenance-window.md).<br />Compatibility with the SQL Server version can be achieved only using database compatibility levels. | You might use [manual or automated backups](virtual-machines/windows/backup-restore.md).<br />You need to implement your own High-Availability solution.<br />There's a downtime while changing the resources(CPU/storage) |
 | Databases of up to 128 TB. | Up to 16 TB. | SQL Server instances with up to 256 TB of storage. The instance can support as many databases as needed. |
 | On-premises application can access data in Azure SQL Database. | [Configure an existing virtual network for Azure SQL Managed Instance](managed-instance/vnet-existing-add-subnet.md) and connectivity to your on-premises environment using Azure Express Route or VPN Gateway. | With SQL virtual machines, you can have applications that run partly in the cloud and partly on-premises. For example, you can extend your on-premises network and Active Directory Domain to the cloud via [Azure Virtual Network](/azure/virtual-network/virtual-networks-overview). For more information on hybrid cloud solutions, see [Extending on-premises data solutions to the cloud](/azure/architecture/data-guide/scenarios/hybrid-on-premises-and-cloud). |
@@ -178,9 +178,9 @@ For many businesses, the decision to transition to a cloud service is as much ab
 
 For many IT departments, meeting up-time obligations of a service-level agreement (SLA) is a top priority. In this section, we look at what SLA applies to each database hosting option.
 
-For both **Azure SQL Database** and **Azure SQL Managed Instance**, Microsoft provides an availability SLA of 99.99%. For the latest information, see [Service-level agreement](https://azure.microsoft.com/support/legal/sla/azure-sql-database).
+For both **Azure SQL Database** and **Azure SQL Managed Instance**, Microsoft provides an [enterprise class availability SLA](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services?lang=1) which increases with zone redundancy for [Azure SQL Database](database/high-availability-sla-local-zone-redundancy.md) and [Azure SQL Managed Instance](managed-instance/high-availability-sla-local-zone-redundancy.md). For the latest information, see [Service-level agreement](https://azure.microsoft.com/support/legal/sla/azure-sql-database).
 
-For **SQL Server on Azure VMs**, Microsoft provides an availability SLA of 99.95% for two virtual machines in an availability set, or 99.99% for two virtual machines in different availability zones. This means that at least one of the two virtual machines is available for the given SLA, but it doesn't cover the processes (such as SQL Server) running on the VM. For the latest information, see the [VM SLA](https://azure.microsoft.com/support/legal/sla/virtual-machines/). For database high availability (HA) within VMs, you should configure one of the supported high availability options in SQL Server, such as [Always On availability groups](virtual-machines/windows/availability-group-azure-portal-configure.md). Using a supported high availability option doesn't provide an additional SLA, but allows you to achieve >99.99% database availability.
+For **SQL Server on Azure VMs**, Microsoft provides an [enterprise class availability SLA](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services?lang=1) for two virtual machines in an [availability set][availability zones or availability sets](virtual-machines/windows/business-continuity-high-availability-disaster-recovery-hadr-overview.md#high-availability-nodes-in-an-availability-set), which increases for two virtual machines in different [availability zones][availability zones or availability sets](virtual-machines/windows/business-continuity-high-availability-disaster-recovery-hadr-overview.md#high-availability-nodes-in-an-availability-zone). This means that at least one of the two virtual machines is available for the given SLA, but it doesn't cover the processes (such as SQL Server) running on the VM. For database high availability (HA) within VMs, you should configure one of the supported high availability options in SQL Server, such as [Always On availability groups](virtual-machines/windows/availability-group-azure-portal-configure.md). Using a supported high availability option doesn't provide an additional SLA, but allows you to achieve database availability in addition to the VM availability.
 
 <a id="market"></a> 
 

azure-sql/database/business-continuity-high-availability-disaster-recover-hadr-overview.md

@@ -49,14 +49,14 @@ In most cases, SQL Database handles disruptive events that might happen in a clo
 
 ## High Availability
 
-Azure SQL Database comes with a core resiliency and reliability promise that protects it against software or hardware failures. Database backups are automated to protect your data from corruption or accidental deletion. As a Platform-as-a-service (PaaS), the Azure SQL Database service provides availability as an off-the-shelf feature with an industry-leading availability SLA of 99.99%. 
+Azure SQL Database comes with a core resiliency and reliability promise that protects it against software or hardware failures. Database backups are automated to protect your data from corruption or accidental deletion. As a Platform-as-a-service (PaaS), the Azure SQL Database service provides availability as an off-the-shelf feature with an [enterprise class availability SLA](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services?lang=1). 
 
 To achieve high availability in the Azure cloud environment, enable [zone redundancy](high-availability-sla-local-zone-redundancy.md#zone-redundant-availability). With zone redundancy, the database or elastic pool uses [Azure availability zones](/azure/reliability/availability-zones-overview) to ensure resilience to zonal failures. 
 
 - Many Azure regions provide availability zones, which are separated groups of data centers within a region that have independent power, cooling, and networking infrastructure. 
 - Availability zones are designed to provide regional services, capacity, and high availability in the remaining zones if one zone experiences an outage. 
 
-By enabling zone redundancy, the database or elastic pool is resilient to zonal hardware and software failures and the recovery is transparent to applications. When high availability is enabled, the Azure SQL Database service is able to provide a higher availability SLA of 99.995%. 
+By enabling zone redundancy, the database or elastic pool is resilient to zonal hardware and software failures and the recovery is transparent to applications. When high availability is enabled, the Azure SQL Database service is able to provide a higher availability SLA. 
 
 ## Disaster recovery
 
@@ -98,9 +98,9 @@ From a database perspective, there are four major potential disruption scenarios
 
 | Business disruption scenario | Business continuity feature |
 |:--|:--|
-| Local hardware or software failures affecting the database node. | To mitigate local hardware and software failures, Azure SQL Database includes an [availability architecture](high-availability-sla-local-zone-redundancy.md), which guarantees automatic recovery from these failures with up to 99.99% availability SLA.|
+| Local hardware or software failures affecting the database node. | To mitigate local hardware and software failures, Azure SQL Database includes an [availability architecture](high-availability-sla-local-zone-redundancy.md), which guarantees automatic recovery from these failures with an [enterprise class SLA](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services?lang=1).|
 | Data corruption or deletion typically caused by an application bug or human error. Such failures are application-specific and typically can't be detected by the database service. | To protect your business from data loss, SQL Database automatically creates full database backups weekly, differential database backups every 12 or 24 hours, and transaction log backups every 5 - 10 minutes. By default, backups are stored in [geo-redundant storage](automated-backups-overview.md#backup-storage-redundancy) for seven days for all service tiers. All service tiers except Basic support a configurable backup retention period for [point-in-time restore (PITR)](recovery-using-backups.md#point-in-time-restore) of up to 35 days. You can [restore a deleted database](recovery-using-backups.md#restore-deleted-database) to the point at which it was deleted if the server hasn't been deleted, or if you've configured [long-term retention (LTR)](long-term-retention-overview.md).|
-| Rare datacenter or availability zone outage, possibly caused by a natural disaster event, configuration change, software bug, or hardware failure. | To mitigate datacenter or availability zone level outage, enable [zone redundancy](high-availability-sla-local-zone-redundancy.md#zone-redundant-availability) for the database or elastic pool to use [Azure Availability Zones](/azure/reliability/availability-zones-overview) and provide redundancy across multiple physical zones within an Azure region. Enabling zone redundancy ensures the database or elastic pool is resilient to zonal failures with up to 99.995% high availability SLA.|
+| Rare datacenter or availability zone outage, possibly caused by a natural disaster event, configuration change, software bug, or hardware failure. | To mitigate datacenter or availability zone level outage, enable [zone redundancy](high-availability-sla-local-zone-redundancy.md#zone-redundant-availability) for the database or elastic pool to use [Azure Availability Zones](/azure/reliability/availability-zones-overview) and provide redundancy across multiple physical zones within an Azure region. Enabling zone redundancy ensures the database or elastic pool is resilient to zonal failures to increase beyond the default [enterprise class SLA](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services?lang=1).|
 | Rare _regional outage_ affecting all availability zones and the datacenters comprising it, possibly caused by catastrophic natural disaster event. | To mitigate a region-wide outage, enable disaster recovery using one of the options: </br> - Continuous data synchronization options like [failover groups (recommended)](failover-group-sql-db.md) or [active geo-replication](active-geo-replication-overview.md) that allow you to create replicas in a secondary region for failover. </br> - Setting backup storage redundancy to geo-redundant backup storage to use [geo-restore](recovery-using-backups.md#geo-restore).|