20210519 1615

WilliamDAssafMSFT · WilliamDAssafMSFT · commit a89e2c7a90d4 · 2021-05-19T16:16:02.000-07:00
diff --git a/azure-sql/database/always-encrypted-enclaves-enable-sgx.md b/azure-sql/database/always-encrypted-enclaves-enable-sgx.md
@@ -1,7 +1,6 @@
 ---
-title: "Enable Intel SGX for your Azure SQL Database"
+title: "Enable Intel SGX for Always Encrypted"
 description: "Learn how to enable Intel SGX for Always Encrypted with secure enclaves in Azure SQL Database by selecting an SGX-enabled hardware generation."
-keywords: encrypt data, sql encryption, database encryption, sensitive data, Always Encrypted, secure enclaves, SGX, attestation
 services: sql-database
 ms.service: sql-database
 ms.subservice: security
@@ -12,7 +11,7 @@ ms.author: jaszymas
 ms.reviwer: vanto
 ms.date: 01/15/2021 
 ---
-# Enable Intel SGX for your Azure SQL Database 
+# Enable Intel SGX for Always Encrypted for your Azure SQL Database 
 
 [!INCLUDE[appliesto-sqldb](../includes/appliesto-sqldb.md)]
 
diff --git a/azure-sql/database/always-encrypted-enclaves-getting-started.md b/azure-sql/database/always-encrypted-enclaves-getting-started.md
@@ -1,7 +1,6 @@
 ---
-title: "Tutorial: Getting started with Always Encrypted with secure enclaves in Azure SQL Database"
+title: "Tutorial: Getting started with Always Encrypted with secure enclaves"
 description: This tutorial teaches you how to create a basic environment for Always Encrypted with secure enclaves in Azure SQL Database and how to encrypt data in-place, and issue rich confidential queries against encrypted columns using SQL Server Management Studio (SSMS). 
-keywords: encrypt data, sql encryption, database encryption, sensitive data, Always Encrypted, secure enclaves, SGX, attestation
 services: sql-database
 ms.service: sql-database
 ms.subservice: security
diff --git a/azure-sql/database/always-encrypted-enclaves-plan.md b/azure-sql/database/always-encrypted-enclaves-plan.md
@@ -1,7 +1,6 @@
 ---
 title: "Plan for Intel SGX enclaves and attestation in Azure SQL Database"
 description: "Plan the deployment of Always Encrypted with secure enclaves in Azure SQL Database."
-keywords: encrypt data, sql encryption, database encryption, sensitive data, Always Encrypted, secure enclaves, SGX, attestation
 services: sql-database
 ms.service: sql-database
 ms.subservice: security
diff --git a/azure-sql/database/cost-management.md b/azure-sql/database/cost-management.md
@@ -1,5 +1,5 @@
 ---
-title: Plan and manage costs for Azure SQL Database
+title: Plan and manage costs
 description: Learn how to plan for and manage costs for Azure SQL Database by using cost analysis in the Azure portal.
 author: WilliamDAssafMSFT
 ms.author: wiassaf
@@ -9,7 +9,6 @@ ms.topic: how-to
 ms.date: 01/15/2021
 ---
 
-
 # Plan and manage costs for Azure SQL Database
 
 This article describes how you plan for and manage costs for Azure SQL Database. First, you use the Azure pricing calculator to add Azure resources, and review the estimated costs. After you've started using Azure SQL Database resources, use Cost Management features to set budgets and monitor costs. You can also review forecasted costs and identify spending trends to identify areas where you might want to act. Costs for Azure SQL Database are only a portion of the monthly costs in your Azure bill. Although this article explains how to plan for and manage costs for Azure SQL Database, you're billed for all Azure services and resources used in your Azure subscription, including any third-party services.
diff --git a/azure-sql/database/purchasing-models.md b/azure-sql/database/purchasing-models.md
@@ -1,6 +1,6 @@
 ---
 title: Purchasing models
-titleSuffix: Azure SQL Database & Azure SQL Managed Instance 
+titleSuffix: Azure SQL Database & SQL Managed Instance
 description: Learn about the purchasing models that are available for Azure SQL Database and Azure SQL Managed Instance.  
 services: sql-database
 ms.service: sql-db-mi
diff --git a/azure-sql/database/service-tiers-sql-database-vcore.md b/azure-sql/database/service-tiers-sql-database-vcore.md
@@ -1,6 +1,5 @@
 ---
-title: vCore purchasing model overview
-titleSuffix: Azure SQL Database 
+title: vCore purchase model
 description: The vCore purchasing model lets you independently scale compute and storage resources, match on-premises performance, and optimize price for Azure SQL Database
 services: sql-database
 ms.service: sql-database
@@ -11,10 +10,12 @@ ms.author: wiassaf
 ms.reviewer: sashan, moslake
 ms.date: 05/18/2021
 ---
-# vCore model overview - Azure SQL Database 
+# vCore purchase model overview - Azure SQL Database 
 [!INCLUDE[appliesto-sqldb](../includes/appliesto-sqldb.md)]
 
-The virtual core (vCore) purchasing model used by Azure SQL Database provides several benefits:
+This article reviews the vCore purchase model for [Azure SQL Database](sql-database-paas-overview.md). For more information on choosing between the vCore and DTU purchase models, see [Choose between the vCore and DTU purchasing models](purchasing-models.md).
+
+The virtual core (vCore) purchase model used by Azure SQL Database provides several benefits over the DTU purchase model:
 
 - Higher compute, memory, I/O, and storage limits.
 - Control over the hardware generation to better match compute and memory requirements of the workload.
@@ -23,7 +24,7 @@ The virtual core (vCore) purchasing model used by Azure SQL Database provides se
 
 ## Service tiers
 
-Service tier options in the vCore model include General Purpose, Business Critical, and Hyperscale. The service tier generally defines the storage architecture, space and I/O limits, and business continuity options related to availability and disaster recovery.
+Service tier options in the vCore purchase model include General Purpose, Business Critical, and Hyperscale. The service tier generally defines the storage architecture, space and I/O limits, and business continuity options related to availability and disaster recovery.
 
 |**Use case**|**General Purpose**|**Business Critical**|**Hyperscale**|
 |---|---|---|---|
diff --git a/azure-sql/database/service-tiers-vcore.md b/azure-sql/database/service-tiers-vcore.md
@@ -1,6 +1,6 @@
 ---
-title: vCore purchasing model overview
-titleSuffix: Azure SQL Database & Azure SQL Managed Instance 
+title: vCore purchase model
+titleSuffix: Azure SQL Database & SQL Managed Instance 
 description: The vCore purchasing model lets you independently scale compute and storage resources, match on-premises performance, and optimize price for Azure SQL Database and Azure SQL Managed Instance.
 services: sql-database
 ms.service: sql-db-mi
@@ -10,19 +10,24 @@ author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: sashan, moslake
 ms.date: 05/18/2021
+ROBOTS: NOINDEX 
 ---
 # vCore model overview - Azure SQL Database and Azure SQL Managed Instance 
 [!INCLUDE[appliesto-sqldb-sqlmi](../includes/appliesto-sqldb-sqlmi.md)]
 
 The virtual core (vCore) purchasing model used by Azure SQL Database and Azure SQL Managed Instance provides several benefits:
 
-- Higher compute, memory, I/O, and storage limits.
 - Control over the hardware generation to better match compute and memory requirements of the workload.
 - Pricing discounts for [Azure Hybrid Benefit (AHB)](../azure-hybrid-benefit.md) and [Reserved Instance (RI)](reserved-capacity-overview.md).
 - Greater transparency in the hardware details that power the compute, that facilitates planning for migrations from on-premises deployments.
+- In the case of Azure SQL Database, vCore purchasing model provides higher compute, memory, I/O, and storage limits than the DTU model.
+
+For more information on choosing between the vCore and DTU purchase models, see [Choose between the vCore and DTU purchasing models](purchasing-models.md).
 
 ## Service tiers
 
+The following articles provide specific information on the vCore purchase model in each product.
+
 - For information on Azure SQL Database service tiers for the vCore model, see [vCore model overview - Azure SQL Database](service-tiers-sql-database-vcore.md).
 - For information on Azure SQL Managed Instance service tiers for the vCore model, see [vCore model overview - Azure SQL Managed Instance](../managed-instance/service-tiers-managed-instance-vcore.md).
 
@@ -32,8 +37,11 @@ To get started, see:
 - [Creating a SQL Database using the Azure portal](single-database-create-quickstart.md)
 - [Creating a SQL Managed Instance using the Azure portal](../managed-instance/instance-create-quickstart.md)
 
-For pricing details, see the [Azure SQL Database pricing page](https://azure.microsoft.com/pricing/details/sql-database/single/).
-
+- For pricing details, see 
+    - [Azure SQL Database pricing page](https://azure.microsoft.com/pricing/details/sql-database/single/)
+    - [Azure SQL Managed Instance single instance pricing page](https://azure.microsoft.com/pricing/details/azure-sql-managed-instance/single/)
+    - [Azure SQL Managed Instance pools pricing page](https://azure.microsoft.com/pricing/details/azure-sql-managed-instance/pools/)
+    
 For details about the specific compute and storage sizes available in the general purpose and business critical service tiers, see:
 
 - [vCore-based resource limits for Azure SQL Database](resource-limits-vcore-single-databases.md).
diff --git a/azure-sql/glossary-terms.md b/azure-sql/glossary-terms.md
@@ -1,6 +1,6 @@
 ---
 title: Glossary of terms 
-titleSuffix: Azure SQL 
+titleSuffix: Azure SQL Database & SQL Managed Instance 
 description: A glossary of terms for working with Azure SQL Database, Azure SQL Managed Instance, and SQL on Azure VM. 
 services: sql-database
 ms.service: sql-db-mi
diff --git a/azure-sql/managed-instance/frequently-asked-questions-faq.md b/azure-sql/managed-instance/frequently-asked-questions-faq.md
@@ -1,6 +1,5 @@
 ---
 title: Frequently asked questions (FAQ)
-titleSuffix: Azure SQL Managed Instance 
 description: Azure SQL Managed Instance frequently asked questions (FAQ)
 services: sql-database
 ms.service: sql-managed-instance
diff --git a/azure-sql/managed-instance/service-tiers-managed-instance-vcore.md b/azure-sql/managed-instance/service-tiers-managed-instance-vcore.md
@@ -1,6 +1,5 @@
 ---
-title: Azure SQL Managed Instance vCore purchasing model overview
-titleSuffix: Azure SQL Managed Instance compute hardware
+title: vCore purchase model
 description: The vCore purchasing model lets you independently scale compute and storage resources, match on-premises performance, and optimize price for Azure SQL Managed Instance.
 services: sql-database
 ms.service: sql-managed-instance
@@ -14,15 +13,17 @@ ms.date: 05/18/2021
 # Azure SQL Managed Instance - Compute Hardware in the vCore Service Tier
 [!INCLUDE[appliesto-sqlmi](../includes/appliesto-sqlmi.md)]
 
-The virtual core (vCore) purchasing model used by Azure SQL Managed Instance has following characteristics:
+This article reviews the vCore purchase model for [Azure SQL Managed Instance](sql-managed-instance-paas-overview.md). For more information on choosing between the vCore and DTU purchase models, see [Choose between the vCore and DTU purchasing models](purchasing-models.md).
+
+The virtual core (vCore) purchase model used by Azure SQL Managed Instance has following characteristics:
 
 - Control over the hardware generation to better match compute and memory requirements of the workload.
 - Pricing discounts for [Azure Hybrid Benefit (AHB)](../azure-hybrid-benefit.md) and [Reserved Instance (RI)](../database/reserved-capacity-overview.md).
 - Greater transparency in the hardware details that power the compute, that facilitates planning for migrations from on-premises deployments.
 
 ## <a id="compute-tiers"></a>Service tiers
 
-Service tier options in the vCore model include General Purpose and Business Critical. The service tier generally defines the storage architecture, space and I/O limits, and business continuity options related to availability and disaster recovery.
+Service tier options in the vCore purchase model include General Purpose and Business Critical. The service tier generally defines the storage architecture, space and I/O limits, and business continuity options related to availability and disaster recovery.
 
 |**Use case**|**General Purpose**|**Business Critical**|
 |---|---|---|
