diff --git a/docs/2014/analysis-services/analysis-services.md b/docs/2014/analysis-services/analysis-services.md
index 5dfca715b9d..782c35f8244 100644
--- a/docs/2014/analysis-services/analysis-services.md
+++ b/docs/2014/analysis-services/analysis-services.md
@@ -30,7 +30,7 @@ Documentation is separated by version. You are currently in SQL Server 2014 Anal
- To learn more about SQL Server 2012 and earlier, see [SQL Server previous versions documentation](https://docs.microsoft.com/previous-versions/sql/).
- To learn more about SQL Server 2014, see [Books Online for SQL Server 2014](../2014-toc/books-online-for-sql-server-2014.md)
- To learn more about SQL Server 2016 and later, see [Microsoft SQL documentation](https://docs.microsoft.com/sql/).
-- To learn more about Azure Analysis Services, see [Azure Analysis Services Documentation](https://docs.microsoft.com/en-us/azure/analysis-services/).
+- To learn more about Azure Analysis Services, see [Azure Analysis Services Documentation](https://docs.microsoft.com/azure/analysis-services/).
## Analysis Services workflow
diff --git a/docs/2014/database-engine/transparent-data-encryption-with-azure-sql-database.md b/docs/2014/database-engine/transparent-data-encryption-with-azure-sql-database.md
index 02e0b957d51..c04961b32f6 100644
--- a/docs/2014/database-engine/transparent-data-encryption-with-azure-sql-database.md
+++ b/docs/2014/database-engine/transparent-data-encryption-with-azure-sql-database.md
@@ -24,12 +24,12 @@ manager: craigg
||
|-|
-|**Applies to**: [!INCLUDE[sqldbesa](../includes/sqldbesa-md.md)] ([Preview in some regions](http://azure.microsoft.com/documentation/articles/sql-database-preview-whats-new/?WT.mc_id=TSQL_GetItTag)).|
+|**Applies to**: [!INCLUDE[sqldbesa](../includes/sqldbesa-md.md)] ([Preview in some regions](https://azure.microsoft.com/documentation/articles/sql-database-preview-whats-new/?WT.mc_id=TSQL_GetItTag)).|
> [!IMPORTANT]
-> This is currently a preview feature. I acknowledge and agree that implementation of [!INCLUDE[ssSDS](../includes/sssds-md.md)] transparent data encryption in my database(s) is subject to the preview terms in my license agreement (e.g. the Enterprise Agreement, Microsoft Azure Agreement, or Microsoft Online Subscription Agreement), as well as any applicable [Supplemental Terms of Use for Microsoft Azure Preview](http://azure.microsoft.com/support/legal/preview-supplemental-terms/).
+> This is currently a preview feature. I acknowledge and agree that implementation of [!INCLUDE[ssSDS](../includes/sssds-md.md)] transparent data encryption in my database(s) is subject to the preview terms in my license agreement (e.g. the Enterprise Agreement, Microsoft Azure Agreement, or Microsoft Online Subscription Agreement), as well as any applicable [Supplemental Terms of Use for Microsoft Azure Preview](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
- The preview of status of TDE applies even in the subset of geographic regions where version family V12 of [!INCLUDE[ssSDS](../includes/sssds-md.md)] is announced as now being in general availability status. TDE for [!INCLUDE[ssSDS](../includes/sssds-md.md)] is not intended for use in production databases until [!INCLUDE[msCoName](../includes/msconame-md.md)] announces that TDE is promoted from preview to GA. For more information about [!INCLUDE[ssSDS](../includes/sssds-md.md)] V12, see [What's new in Azure SQL Database](http://azure.microsoft.com/documentation/articles/sql-database-preview-whats-new/).
+ The preview of status of TDE applies even in the subset of geographic regions where version family V12 of [!INCLUDE[ssSDS](../includes/sssds-md.md)] is announced as now being in general availability status. TDE for [!INCLUDE[ssSDS](../includes/sssds-md.md)] is not intended for use in production databases until [!INCLUDE[msCoName](../includes/msconame-md.md)] announces that TDE is promoted from preview to GA. For more information about [!INCLUDE[ssSDS](../includes/sssds-md.md)] V12, see [What's new in Azure SQL Database](https://azure.microsoft.com/documentation/articles/sql-database-preview-whats-new/).
## Permissions
To sign up for the preview and to configure TDE through the Azure portal, by using the REST API, or by using PowerShell, you must be connected as the Azure Owner, Contributor, or SQL Security Manager.
@@ -87,7 +87,7 @@ manager: craigg
3. To monitor the progress of encryption on [!INCLUDE[ssSDS](../includes/sssds-md.md)], database users with the **VIEW DATABASE STATE** permission can query the `encryption_state` column of the [sys.dm_database_encryption_keys](/sql/relational-databases/system-dynamic-management-views/sys-dm-database-encryption-keys-transact-sql) view.
## Enabling TDE on SQL Database by Using PowerShell
- Using the Azure PowerShell you can run the following command to turn TDE on/off. You do have to connect your account to the PS window before running the command. The following steps, assume you have already signed up for the preview. For additional information about PowerShell, see [How to install and configure Azure PowerShell](http://azure.microsoft.com/documentation/articles/powershell-install-configure/).
+ Using the Azure PowerShell you can run the following command to turn TDE on/off. You do have to connect your account to the PS window before running the command. The following steps, assume you have already signed up for the preview. For additional information about PowerShell, see [How to install and configure Azure PowerShell](https://azure.microsoft.com/documentation/articles/powershell-install-configure/).
1. To enable TDE, return the TDE status, and view the encryption activity.
diff --git a/docs/2014/integration-services/control-flow/azure-hdinsight-create-cluster-task.md b/docs/2014/integration-services/control-flow/azure-hdinsight-create-cluster-task.md
index defc516878d..93f98fb62d7 100644
--- a/docs/2014/integration-services/control-flow/azure-hdinsight-create-cluster-task.md
+++ b/docs/2014/integration-services/control-flow/azure-hdinsight-create-cluster-task.md
@@ -19,7 +19,7 @@ The **Azure HDInsight Create Cluster Task** enables an SSIS package to create an
> [!NOTE]
> - Creating a new HDInsight cluster may take 10~20 minutes.
-> - There is a cost associated with creating and running an Azure HDInsight cluster. See [HDInsight Pricing](http://azure.microsoft.com/en-us/pricing/details/hdinsight/) for details.
+> - There is a cost associated with creating and running an Azure HDInsight cluster. See [HDInsight Pricing](https://azure.microsoft.com/pricing/details/hdinsight/) for details.
To add an **Azure HDInsight Create Cluster Task**, drag-drop it to the SSIS Designer, and double-click or right-click and click **Edit** to see the following **Azure HDInsight Create Cluster Task Editor** dialog box.
diff --git a/docs/2014/master-data-services/master-data-services-overview-mds.md b/docs/2014/master-data-services/master-data-services-overview-mds.md
index 304e74919f8..f3fef594f58 100644
--- a/docs/2014/master-data-services/master-data-services-overview-mds.md
+++ b/docs/2014/master-data-services/master-data-services-overview-mds.md
@@ -19,7 +19,7 @@ manager: craigg
|||
|-|-|
-||Do you want to try out SQL Server 2016? Sign up for Microsoft Azure, and then go **[Here](https://azure.microsoft.com/en-us/marketplace/partners/microsoft/sqlserver2016rtmenterprisewindowsserver2012r2/?wt.mc_id=sqL16_vm)** to spin up a Virtual Machine with SQL Server 2016 already installed. You can delete the Virtual Machine when you're finished.|
+||Do you want to try out SQL Server 2016? Sign up for Microsoft Azure, and then go **[Here](https://azure.microsoft.com/marketplace/partners/microsoft/sqlserver2016rtmenterprisewindowsserver2012r2/?wt.mc_id=sqL16_vm)** to spin up a Virtual Machine with SQL Server 2016 already installed. You can delete the Virtual Machine when you're finished.|
For example, your online product model may contain entities such as product, color, and style. The color entity may contain members for the colors red, silver, and black.
diff --git a/docs/2014/relational-databases/backup-restore/enable-sql-server-managed-backup-to-microsoft-azure.md b/docs/2014/relational-databases/backup-restore/enable-sql-server-managed-backup-to-microsoft-azure.md
index 051ad3dc614..8ccb6ddad62 100644
--- a/docs/2014/relational-databases/backup-restore/enable-sql-server-managed-backup-to-microsoft-azure.md
+++ b/docs/2014/relational-databases/backup-restore/enable-sql-server-managed-backup-to-microsoft-azure.md
@@ -37,7 +37,7 @@ manager: craigg
1. **Create a Microsoft Azure storage account:** The backups are stored in the Microsoft Azure storage service. You must first create a Microsoft Azure storage account, if you do not already have an account.
- - SQL Server 2014 uses page blobs, which are different than block and append blobs. Therefore you must create a general purpose account, and not a blob account. For more information, see [About Azure storage accounts](http://azure.microsoft.com/documentation/articles/storage-create-storage-account/).
+ - SQL Server 2014 uses page blobs, which are different than block and append blobs. Therefore you must create a general purpose account, and not a blob account. For more information, see [About Azure storage accounts](https://azure.microsoft.com/documentation/articles/storage-create-storage-account/).
- Make a note of the storage account name, and the access keys. The storage account name and access key information is used to create a SQL Credential. The SQL Credential is used to authenticate to the storage account.
2. **Create a SQL Credential:** Create a SQL Credential using the name of the storage account as the Identity and the storage access key as the password.
@@ -156,7 +156,7 @@ manager: craigg
1. **Create a Microsoft Azure storage account:** The backups are stored in the Microsoft Azure storage service. You must first create a Microsoft Azure storage account, if you do not already have an account.
- - SQL Server 2014 uses page blobs, which are different than block and append blobs. Therefore you must create a general purpose account, and not a blob account. For more information, see [About Azure storage accounts](http://azure.microsoft.com/documentation/articles/storage-create-storage-account/).
+ - SQL Server 2014 uses page blobs, which are different than block and append blobs. Therefore you must create a general purpose account, and not a blob account. For more information, see [About Azure storage accounts](https://azure.microsoft.com/documentation/articles/storage-create-storage-account/).
- Make a note of the storage account name, and the access keys. The storage account name and access key information is used to create a SQL Credential. The SQL Credential is used to authenticate to the storage account.
2. **Create a SQL Credential:** Create a SQL Credential using the name of the storage account as the Identity and the storage access key as the password.
diff --git a/docs/2014/relational-databases/databases/sql-server-data-files-in-microsoft-azure.md b/docs/2014/relational-databases/databases/sql-server-data-files-in-microsoft-azure.md
index 1aab68cab84..d34d8d27399 100644
--- a/docs/2014/relational-databases/databases/sql-server-data-files-in-microsoft-azure.md
+++ b/docs/2014/relational-databases/databases/sql-server-data-files-in-microsoft-azure.md
@@ -37,10 +37,10 @@ manager: craigg
### Windows Azure Storage Concepts
When using SQL Server Data Files in Windows Azure feature, you need to create a storage account and a container in Windows Azure. Then, you need to create a SQL Server credential, which includes information on the policy of the container as well as a shared access signature that is necessary to access the container.
- In Windows Azure, a storage account represents the highest level of the namespace for accessing Blobs. A storage account can contain an unlimited number of containers, as long as their total size is under 500 TB. For the latest information on storage limits, see [Azure Subscription and Service Limits, Quotas, and Constraints](http://azure.microsoft.com/documentation/articles/azure-subscription-service-limits/). A container provides a grouping of a set of Blobs. All Blobs must be in a container. An account can contain an unlimited number of containers. Similarly, a container can store an unlimited number of Blobs as well. There are two types of blobs that can be stored in Windows Azure Storage: block and page blobs. This new feature uses Page blobs, which can be up to 1TB in size, and are more efficient when ranges of bytes in a file are modified frequently. You can access Blobs using the following URL format: `http://storageaccount.blob.core.windows.net//`.
+ In Windows Azure, a storage account represents the highest level of the namespace for accessing Blobs. A storage account can contain an unlimited number of containers, as long as their total size is under 500 TB. For the latest information on storage limits, see [Azure Subscription and Service Limits, Quotas, and Constraints](https://azure.microsoft.com/documentation/articles/azure-subscription-service-limits/). A container provides a grouping of a set of Blobs. All Blobs must be in a container. An account can contain an unlimited number of containers. Similarly, a container can store an unlimited number of Blobs as well. There are two types of blobs that can be stored in Windows Azure Storage: block and page blobs. This new feature uses Page blobs, which can be up to 1TB in size, and are more efficient when ranges of bytes in a file are modified frequently. You can access Blobs using the following URL format: `http://storageaccount.blob.core.windows.net//`.
### Windows Azure Billing Considerations
- Estimating the cost of using Windows Azure Services is an important matter in the decision making and planning process. When storing SQL Server data files in Windows Azure Storage, you need to pay costs associated with storage and transactions. In addition, the implementation of SQL Server Data Files in Windows Azure Storage feature requires a renewal of Blob lease every 45 to 60 seconds implicitly. This also results in transaction costs per database file, such as .mdf or .ldf. Based on our estimations, the cost of renewing leases for two database files (.mdf and .ldf) would be about 2 cents per month according to the current pricing model. We recommend that you use the information on the [Azure Pricing](http://azure.microsoft.com/pricing/) page to help estimate the monthly costs associated with the use of Windows Azure Storage and Windows Azure Virtual Machines.
+ Estimating the cost of using Windows Azure Services is an important matter in the decision making and planning process. When storing SQL Server data files in Windows Azure Storage, you need to pay costs associated with storage and transactions. In addition, the implementation of SQL Server Data Files in Windows Azure Storage feature requires a renewal of Blob lease every 45 to 60 seconds implicitly. This also results in transaction costs per database file, such as .mdf or .ldf. Based on our estimations, the cost of renewing leases for two database files (.mdf and .ldf) would be about 2 cents per month according to the current pricing model. We recommend that you use the information on the [Azure Pricing](https://azure.microsoft.com/pricing/) page to help estimate the monthly costs associated with the use of Windows Azure Storage and Windows Azure Virtual Machines.
### SQL Server Concepts
When using this new enhancement, you are required to do the followings:
diff --git a/docs/2014/relational-databases/in-memory-oltp/in-memory-oltp-in-memory-optimization.md b/docs/2014/relational-databases/in-memory-oltp/in-memory-oltp-in-memory-optimization.md
index a94ec750dcc..a6b3040be60 100644
--- a/docs/2014/relational-databases/in-memory-oltp/in-memory-oltp-in-memory-optimization.md
+++ b/docs/2014/relational-databases/in-memory-oltp/in-memory-oltp-in-memory-optimization.md
@@ -20,7 +20,7 @@ manager: craigg
|||
|-|-|
-||Do you want to try out SQL Server 2016? Sign up for Microsoft Azure, and then go **[Here](https://azure.microsoft.com/en-us/marketplace/partners/microsoft/sqlserver2016rtmenterprisewindowsserver2012r2/?wt.mc_id=sqL16_vm)** to spin up a Virtual Machine with SQL Server 2016 already installed. You can delete the Virtual Machine when you're finished.|
+||Do you want to try out SQL Server 2016? Sign up for Microsoft Azure, and then go **[Here](https://azure.microsoft.com/marketplace/partners/microsoft/sqlserver2016rtmenterprisewindowsserver2012r2/?wt.mc_id=sqL16_vm)** to spin up a Virtual Machine with SQL Server 2016 already installed. You can delete the Virtual Machine when you're finished.|
To use [!INCLUDE[hek_2](../../../includes/hek-2-md.md)], you define a heavily accessed table as memory optimized. Memory-optimized-tables are fully transactional, durable, and are accessed using [!INCLUDE[tsql](../../../includes/tsql-md.md)] in the same way as disk-based tables. A query can reference both memory-optimized tables and disk-based tables. A transaction can update data in memory-optimized tables and disk-based tables. Stored procedures that only reference memory-optimized tables can be natively compiled into machine code for further performance improvements. The [!INCLUDE[hek_2](../../../includes/hek-2-md.md)] engine is designed for extremely high session concurrency for OLTP type of transactions driven from a highly scaled-out middle-tier. To achieve this, it uses latch-free data structures and optimistic, multi-version concurrency control. The result is predictable, sub-millisecond low latency and high throughput with linear scaling for database transactions. The actual performance gain depends on many factors, but 5-to-20 times performance improvements are common.
diff --git a/docs/2014/relational-databases/performance/monitoring-performance-by-using-the-query-store.md b/docs/2014/relational-databases/performance/monitoring-performance-by-using-the-query-store.md
index 111739445d8..0fc4c368c31 100644
--- a/docs/2014/relational-databases/performance/monitoring-performance-by-using-the-query-store.md
+++ b/docs/2014/relational-databases/performance/monitoring-performance-by-using-the-query-store.md
@@ -19,7 +19,7 @@ manager: craigg
|**Applies to**: [!INCLUDE[sqldbesa](../../includes/sqldbesa-md.md)] ([Get it](http://azure.micosoft.com/documentation/articles/sql-database-preview-whats-new/?WT.mc_id=TSQL_GetItTag)).|
> [!IMPORTANT]
-> This is currently a preview feature. To use the Query Store you must acknowledge and agree that implementation of Query Store is subject to the preview terms in your license agreement (e.g. the Enterprise Agreement, Microsoft Azure Agreement, or Microsoft Online Subscription Agreement), as well as any applicable [Supplemental Terms of Use for Microsoft Azure Preview](http://azure.microsoft.com/en-us/support/legal/preview-supplemental-terms/).
+> This is currently a preview feature. To use the Query Store you must acknowledge and agree that implementation of Query Store is subject to the preview terms in your license agreement (e.g. the Enterprise Agreement, Microsoft Azure Agreement, or Microsoft Online Subscription Agreement), as well as any applicable [Supplemental Terms of Use for Microsoft Azure Preview](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
## Enabling the Query Store
Query Store is not active for new databases by default.
diff --git a/docs/2014/relational-databases/security/encryption/transparent-data-encryption.md b/docs/2014/relational-databases/security/encryption/transparent-data-encryption.md
index 0527ea3adf0..2aa5c7218c2 100644
--- a/docs/2014/relational-databases/security/encryption/transparent-data-encryption.md
+++ b/docs/2014/relational-databases/security/encryption/transparent-data-encryption.md
@@ -38,9 +38,9 @@ manager: craigg
**Information applicable to [!INCLUDE[ssSDS](../../../includes/sssds-md.md)]**
- When using TDE with [!INCLUDE[sqldbesa](../../../includes/sqldbesa-md.md)] V12 ([Preview in some regions](http://azure.microsoft.com/documentation/articles/sql-database-preview-whats-new/?WT.mc_id=TSQL_GetItTag)) the server-level certificate stored in the master database is automatically created for you by [!INCLUDE[ssSDS](../../../includes/sssds-md.md)]. To move a TDE database on [!INCLUDE[ssSDS](../../../includes/sssds-md.md)] you must decrypt the database, move the database, and then re-enable TDE on the destination [!INCLUDE[ssSDS](../../../includes/sssds-md.md)]. For step-by-step instructions for TDE on [!INCLUDE[ssSDS](../../../includes/sssds-md.md)], see [Transparent Data Encryption with Azure SQL Database](../../../database-engine/transparent-data-encryption-with-azure-sql-database.md).
+ When using TDE with [!INCLUDE[sqldbesa](../../../includes/sqldbesa-md.md)] V12 ([Preview in some regions](https://azure.microsoft.com/documentation/articles/sql-database-preview-whats-new/?WT.mc_id=TSQL_GetItTag)) the server-level certificate stored in the master database is automatically created for you by [!INCLUDE[ssSDS](../../../includes/sssds-md.md)]. To move a TDE database on [!INCLUDE[ssSDS](../../../includes/sssds-md.md)] you must decrypt the database, move the database, and then re-enable TDE on the destination [!INCLUDE[ssSDS](../../../includes/sssds-md.md)]. For step-by-step instructions for TDE on [!INCLUDE[ssSDS](../../../includes/sssds-md.md)], see [Transparent Data Encryption with Azure SQL Database](../../../database-engine/transparent-data-encryption-with-azure-sql-database.md).
- The preview of status of TDE applies even in the subset of geographic regions where version family V12 of [!INCLUDE[ssSDS](../../../includes/sssds-md.md)] is announced as now being in general availability status. TDE for [!INCLUDE[ssSDS](../../../includes/sssds-md.md)] is not intended for use in production databases until [!INCLUDE[msCoName](../../../includes/msconame-md.md)] announces that TDE is promoted from preview to GA. For more information about [!INCLUDE[ssSDS](../../../includes/sssds-md.md)] V12, see [What's new in Azure SQL Database](http://azure.microsoft.com/documentation/articles/sql-database-preview-whats-new/).
+ The preview of status of TDE applies even in the subset of geographic regions where version family V12 of [!INCLUDE[ssSDS](../../../includes/sssds-md.md)] is announced as now being in general availability status. TDE for [!INCLUDE[ssSDS](../../../includes/sssds-md.md)] is not intended for use in production databases until [!INCLUDE[msCoName](../../../includes/msconame-md.md)] announces that TDE is promoted from preview to GA. For more information about [!INCLUDE[ssSDS](../../../includes/sssds-md.md)] V12, see [What's new in Azure SQL Database](https://azure.microsoft.com/documentation/articles/sql-database-preview-whats-new/).
**Information applicable to [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)]**
diff --git a/docs/2014/relational-databases/security/security-center-for-sql-server-database-engine-and-azure-sql-database.md b/docs/2014/relational-databases/security/security-center-for-sql-server-database-engine-and-azure-sql-database.md
index a879dabdb2a..194f6385b21 100644
--- a/docs/2014/relational-databases/security/security-center-for-sql-server-database-engine-and-azure-sql-database.md
+++ b/docs/2014/relational-databases/security/security-center-for-sql-server-database-engine-and-azure-sql-database.md
@@ -26,7 +26,7 @@ manager: craigg
|Authentication: Who are you?|Authorization: What can you do?|Encryption: Storing Secret Data|Connection Security: Restricting and Securing|Auditing: Recording Access|
|----------------------------------|-------------------------------------|-------------------------------------|---------------------------------------------------|--------------------------------|
-|**Who Authenticates?**
[](https://msdn.microsoft.com/library/ms144284.aspx)
[](https://msdn.microsoft.com/library/ms144284.aspx)
**Where Authenticated?**
[](https://msdn.microsoft.com/library/aa337562.aspx)
[](https://msdn.microsoft.com/library/ff929188.aspx)
**Using Other Identities**
[](https://msdn.microsoft.com/library/ms161950.aspx)
[](https://msdn.microsoft.com/library/ms181362.aspx)
[](https://msdn.microsoft.com/library/ms181362.aspx)
|**Granting, Revoking, and Denying Permissions**
[](https://msdn.microsoft.com/library/ms190401.aspx)
[](https://msdn.microsoft.com/library/ms191291.aspx)
[](https://msdn.microsoft.com/library/ms191291.aspx)
**Security by Roles**
[](https://msdn.microsoft.com/library/ms188659.aspx)
[](https://msdn.microsoft.com/library/ms189121.aspx)
`Restricting Data Access to Selected Data Elements`
[](https://msdn.microsoft.com/library/ms175503.aspx)
[](https://msdn.microsoft.com/library/dn765131.aspx)
[](http://azure.microsoft.com/documentation/articles/sql-database-dynamic-data-masking-get-started/)
[](https://msdn.microsoft.com/library/ms181700.aspx)
|**Encrypting Files**
[](https://support.microsoft.com/en-us/kb/2855131)
[](https://msdn.microsoft.com/library/dd163562.aspx)
[](https://msdn.microsoft.com/library/bb934049.aspx)
[](https://msdn.microsoft.com/library/dn449489.aspx)
**Encrypting Sources**
[](https://msdn.microsoft.com/library/bb895340.aspx)
[](http://azure.microsoft.com/documentation/articles/key-vault-get-started/)
**Column, Data & Key Encryption**
[](https://msdn.microsoft.com/library/ms188061.aspx)
[](https://msdn.microsoft.com/library/ms174361.aspx)
[](https://msdn.microsoft.com/library/ms186950.aspx)
[](https://msdn.microsoft.com/library/ms190357.aspx)|**Firewall Protection**
[](https://msdn.microsoft.com/library/ms175043.aspx)
[](https://msdn.microsoft.com/library/azure/ee621782.aspx)
[](https://msdn.microsoft.com/library/azure/ee621782.aspx)
**Encrypting Data in Transit**
[](https://msdn.microsoft.com/library/ms191192.aspx)
[](https://msdn.microsoft.com/library/ms191192.aspx)
|**Automated Auditing**
[](https://msdn.microsoft.com/library/cc280386.aspx)
[](http://azure.microsoft.com/documentation/articles/sql-database-auditing-get-started/)
**Custom Audit**
[](https://msdn.microsoft.com/library/ms175941.aspx)
**Compliance**
[](http://azure.microsoft.com/support/trust-center/services/)
|
+|**Who Authenticates?**
[](https://msdn.microsoft.com/library/ms144284.aspx)
[](https://msdn.microsoft.com/library/ms144284.aspx)
**Where Authenticated?**
[](https://msdn.microsoft.com/library/aa337562.aspx)
[](https://msdn.microsoft.com/library/ff929188.aspx)
**Using Other Identities**
[](https://msdn.microsoft.com/library/ms161950.aspx)
[](https://msdn.microsoft.com/library/ms181362.aspx)
[](https://msdn.microsoft.com/library/ms181362.aspx)
|**Granting, Revoking, and Denying Permissions**
[](https://msdn.microsoft.com/library/ms190401.aspx)
[](https://msdn.microsoft.com/library/ms191291.aspx)
[](https://msdn.microsoft.com/library/ms191291.aspx)
**Security by Roles**
[](https://msdn.microsoft.com/library/ms188659.aspx)
[](https://msdn.microsoft.com/library/ms189121.aspx)
`Restricting Data Access to Selected Data Elements`
[](https://msdn.microsoft.com/library/ms175503.aspx)
[](https://msdn.microsoft.com/library/dn765131.aspx)
[](https://azure.microsoft.com/documentation/articles/sql-database-dynamic-data-masking-get-started/)
[](https://msdn.microsoft.com/library/ms181700.aspx)
|**Encrypting Files**
[](https://support.microsoft.com/en-us/kb/2855131)
[](https://msdn.microsoft.com/library/dd163562.aspx)
[](https://msdn.microsoft.com/library/bb934049.aspx)
[](https://msdn.microsoft.com/library/dn449489.aspx)
**Encrypting Sources**
[](https://msdn.microsoft.com/library/bb895340.aspx)
[](https://azure.microsoft.com/documentation/articles/key-vault-get-started/)
**Column, Data & Key Encryption**
[](https://msdn.microsoft.com/library/ms188061.aspx)
[](https://msdn.microsoft.com/library/ms174361.aspx)
[](https://msdn.microsoft.com/library/ms186950.aspx)
[](https://msdn.microsoft.com/library/ms190357.aspx)|**Firewall Protection**
[](https://msdn.microsoft.com/library/ms175043.aspx)
[](https://msdn.microsoft.com/library/azure/ee621782.aspx)
[](https://msdn.microsoft.com/library/azure/ee621782.aspx)
**Encrypting Data in Transit**
[](https://msdn.microsoft.com/library/ms191192.aspx)
[](https://msdn.microsoft.com/library/ms191192.aspx)
|**Automated Auditing**
[](https://msdn.microsoft.com/library/cc280386.aspx)
[](https://azure.microsoft.com/documentation/articles/sql-database-auditing-get-started/)
**Custom Audit**
[](https://msdn.microsoft.com/library/ms175941.aspx)
**Compliance**
[](https://azure.microsoft.com/support/trust-center/services/)
|
## Links to Specific Related Topics
 **Authentication: Who are you?**
@@ -102,7 +102,7 @@ manager: craigg
- [Row-Level Security](https://msdn.microsoft.com/library/azure/dn765131.aspx)
-- [Dynamic Data Masking](http://azure.microsoft.com/documentation/articles/sql-database-dynamic-data-masking-get-started/)
+- [Dynamic Data Masking](https://azure.microsoft.com/documentation/articles/sql-database-dynamic-data-masking-get-started/)
- [Signed Objects](/sql/t-sql/statements/add-signature-transact-sql)
@@ -126,7 +126,7 @@ manager: craigg
- [SQL Server Audit (Database Engine)](auditing/sql-server-audit-database-engine.md)
-- [SQL Database Auditing](http://azure.microsoft.com/documentation/articles/sql-database-auditing-get-started/)
+- [SQL Database Auditing](https://azure.microsoft.com/documentation/articles/sql-database-auditing-get-started/)
**Custom Audit Implementation**
@@ -139,7 +139,7 @@ manager: craigg
**SQL Database**
-- [Microsoft Azure Trust Center: Compliance by Feature](http://azure.microsoft.com/support/trust-center/services/)
+- [Microsoft Azure Trust Center: Compliance by Feature](https://azure.microsoft.com/support/trust-center/services/)
## See Also
[Securing SQL Server](securing-sql-server.md)
diff --git a/docs/2014/sql-server/failover-clusters/windows/force-a-wsfc-cluster-to-start-without-a-quorum.md b/docs/2014/sql-server/failover-clusters/windows/force-a-wsfc-cluster-to-start-without-a-quorum.md
index 80ab8b4ed10..13ece40da8c 100644
--- a/docs/2014/sql-server/failover-clusters/windows/force-a-wsfc-cluster-to-start-without-a-quorum.md
+++ b/docs/2014/sql-server/failover-clusters/windows/force-a-wsfc-cluster-to-start-without-a-quorum.md
@@ -116,7 +116,7 @@ net.exe start clussvc /forcequorum
## Related Content
-- [View Events and Logs for a Failover Cluster](https://technet.microsoft.com/en-us/library/cc772342\(WS.10\).aspx)
+- [View Events and Logs for a Failover Cluster](https://technet.microsoft.com/library/cc772342\(WS.10\).aspx)
- [Get-ClusterLog Failover Cluster Cmdlet](https://technet.microsoft.com/library/ee461045.aspx)
diff --git a/docs/2014/sql-server/install/are-you-upgrading-from-sql-server-2005.md b/docs/2014/sql-server/install/are-you-upgrading-from-sql-server-2005.md
index 321454e3720..e647016c65f 100644
--- a/docs/2014/sql-server/install/are-you-upgrading-from-sql-server-2005.md
+++ b/docs/2014/sql-server/install/are-you-upgrading-from-sql-server-2005.md
@@ -40,7 +40,7 @@ manager: craigg
|Non-relational solution|Benefits|
|------------------------------|--------------|
-|**Azure DocumentDB**
Consider this option for modern, scalable, mobile and web applications that use JSON data and require a combination of robust querying and transactional data processing.
For more info, see [DocumentDB](https://azure.microsoft.com/en-us/services/documentdb/).|Your documents are indexed and you can use familiar SQL syntax to query them.
The database is schema-free.
You can add properties to documents without having to rebuild indexes.
You get JSON and JavaScript support right inside the database engine.
You get native support for geospatial data and integration with other Azure Services including Azure Search, HDInsight, and Data Factory.
You get low latency, high performance storage with reserved throughput levels.|
+|**Azure DocumentDB**
Consider this option for modern, scalable, mobile and web applications that use JSON data and require a combination of robust querying and transactional data processing.
For more info, see [DocumentDB](https://azure.microsoft.com/services/documentdb/).|Your documents are indexed and you can use familiar SQL syntax to query them.
The database is schema-free.
You can add properties to documents without having to rebuild indexes.
You get JSON and JavaScript support right inside the database engine.
You get native support for geospatial data and integration with other Azure Services including Azure Search, HDInsight, and Data Factory.
You get low latency, high performance storage with reserved throughput levels.|
|**Azure table storage**
Consider this option to store petabytes of semi-structured data in a cost-effective solution.
For more info, see [Table Storage](https://azure.microsoft.com/services/storage/tables/).|You can evolve your apps and your table schema without taking the data offline.
You can scale up without sharding your dataset.
You get geo-redundant storage that replicates data across multiple regions.|
To download the report "Migrating from SQL Server 2005" by Directions on Microsoft, which contains more details about the upgrade options, [click here](https://info.microsoft.com/CO-SQL-CNTNT-FY16-09Sep-14-ModernizationDirOnMFST-Register.html) (not on the thumbnail image below).
diff --git a/docs/2014/tutorials/lesson-1-create-windows-azure-storage-account-and-container.md b/docs/2014/tutorials/lesson-1-create-windows-azure-storage-account-and-container.md
index 443bd876731..4207ae13a24 100644
--- a/docs/2014/tutorials/lesson-1-create-windows-azure-storage-account-and-container.md
+++ b/docs/2014/tutorials/lesson-1-create-windows-azure-storage-account-and-container.md
@@ -31,7 +31,7 @@ manager: craigg
-2. Use the step by step instructions to [create a storage account](http://azure.microsoft.com/documentation/articles/storage-create-storage-account/). Note that when creating a storage account to be used for the SQL Server Data Files in Windows Azure feature, you should unselect or disable the geo-replication. This is because write order is not guaranteed for multiple blobs participating in geo-replication. If a storage account is geo-replicated and recovery is required, a corruption occurs.
+2. Use the step by step instructions to [create a storage account](https://azure.microsoft.com/documentation/articles/storage-create-storage-account/). Note that when creating a storage account to be used for the SQL Server Data Files in Windows Azure feature, you should unselect or disable the geo-replication. This is because write order is not guaranteed for multiple blobs participating in geo-replication. If a storage account is geo-replicated and recovery is required, a corruption occurs.
diff --git a/docs/big-data-cluster/concept-data-persistence.md b/docs/big-data-cluster/concept-data-persistence.md
index 6dbd7c323af..7ebcaadac21 100644
--- a/docs/big-data-cluster/concept-data-persistence.md
+++ b/docs/big-data-cluster/concept-data-persistence.md
@@ -55,7 +55,7 @@ Deployment of big data cluster will use persistent storage to store data, metada
AKS comes with [two built-in storage classes](https://docs.microsoft.com/azure/aks/azure-disks-dynamic-pv) **default** and **managed-premium** along with dynamic provisioner for them. You can specify either of those or create your own storage class for deploying big data cluster with persistent storage enabled. By default, the built in cluster configuration file for aks *aks-dev-test* comes with persistent storage configurations to use **default** storage class.
> [!WARNING]
-> Persistent volumes created with the built-in storage classes **default** and **managed-premium** have a reclaim policy of *Delete*. So at the time the you delete the SQL Server big data cluster, persistent volume claims get deleted and then persistent volumes as well. You can create custom storage classes using **azure-disk** privioner with a *Retain* reclaim policy as shown in [this](https://docs.microsoft.com/en-us/azure/aks/concepts-storage#storage-classes) article.
+> Persistent volumes created with the built-in storage classes **default** and **managed-premium** have a reclaim policy of *Delete*. So at the time the you delete the SQL Server big data cluster, persistent volume claims get deleted and then persistent volumes as well. You can create custom storage classes using **azure-disk** privioner with a *Retain* reclaim policy as shown in [this](https://docs.microsoft.com/azure/aks/concepts-storage#storage-classes) article.
## Minikube storage class
diff --git a/docs/big-data-cluster/deploy-notebooks.md b/docs/big-data-cluster/deploy-notebooks.md
index 1dd164e488a..dfc413789cf 100644
--- a/docs/big-data-cluster/deploy-notebooks.md
+++ b/docs/big-data-cluster/deploy-notebooks.md
@@ -17,7 +17,7 @@ ms.technology: big-data-cluster
[!INCLUDE[sql-server-2019](../includes/sssqlv15-md.md)] provides an extension for Azure Data Studio that includes deployment notebooks. A deployment notebook includes documentation and code that you can use in Azure Data Studio to create a SQL Server big data cluster.
-Originally implemented as an open source project, [notebooks](notebooks-guidance.md) have been implemented into [Azure Data Studio](http://docs.microsoft.com/sql/azure-data-studio/download). You can use markdown for text in the text cells and one of the available kernels to write code in the code cells.
+Originally implemented as an open source project, [notebooks](notebooks-guidance.md) have been implemented into [Azure Data Studio](https://docs.microsoft.com/sql/azure-data-studio/download). You can use markdown for text in the text cells and one of the available kernels to write code in the code cells.
You can use notebooks to deploy big data clusters for [!INCLUDE[sql-server-2019](../includes/sssqlv15-md.md)].
diff --git a/docs/big-data-cluster/manage-notebooks.md b/docs/big-data-cluster/manage-notebooks.md
index f9843ad7033..790c8e3bd66 100644
--- a/docs/big-data-cluster/manage-notebooks.md
+++ b/docs/big-data-cluster/manage-notebooks.md
@@ -17,7 +17,7 @@ ms.technology: big-data-cluster
[!INCLUDE[sql-server-2019](../includes/sssqlv15-md.md)] provides an extension for Azure Data Studio that includes notebooks. A notebook includes documentation and code that you can use in Azure Data Studio to manage big data clusters for SQL Server.
-Originally implemented as an open source project, [notebooks](notebooks-guidance.md) have been implemented into [Azure Data Studio](http://docs.microsoft.com/sql/azure-data-studio/download). You can use markdown for text in the text cells and one of the available kernels to write code in the code cells.
+Originally implemented as an open source project, [notebooks](notebooks-guidance.md) have been implemented into [Azure Data Studio](https://docs.microsoft.com/sql/azure-data-studio/download). You can use markdown for text in the text cells and one of the available kernels to write code in the code cells.
You can use notebooks to deploy big data clusters for [!INCLUDE[sql-server-2019](../includes/sssqlv15-md.md)].
diff --git a/docs/big-data-cluster/spark-history-server.md b/docs/big-data-cluster/spark-history-server.md
index e54abff22f6..4580b8cce6a 100644
--- a/docs/big-data-cluster/spark-history-server.md
+++ b/docs/big-data-cluster/spark-history-server.md
@@ -198,5 +198,5 @@ The Spark History Server has the following known issues:
## Next steps
-* [Get started with SQL Server big data clusters](https://docs.microsoft.com/en-us/sql/big-data-cluster/deploy-get-started?view=sqlallproducts-allversions)
+* [Get started with SQL Server big data clusters](https://docs.microsoft.com/sql/big-data-cluster/deploy-get-started?view=sqlallproducts-allversions)
* [Configure Spark settings](https://docs.microsoft.com/azure/hdinsight/spark/apache-spark-settings)
diff --git a/docs/database-engine/configure-windows/troubleshoot-connecting-to-the-sql-server-database-engine.md b/docs/database-engine/configure-windows/troubleshoot-connecting-to-the-sql-server-database-engine.md
index 467dd9b3fa1..35e1412395b 100644
--- a/docs/database-engine/configure-windows/troubleshoot-connecting-to-the-sql-server-database-engine.md
+++ b/docs/database-engine/configure-windows/troubleshoot-connecting-to-the-sql-server-database-engine.md
@@ -176,7 +176,7 @@ Both of these problems are related to the SQL Server Browser service, which prov
* Start the SQL Server Browser service. See the instructions to [start browser in SQL Server Configuration Manager](#startbrowser).
* The SQL Server Browser service is being blocked by the firewall. Open UDP port 1434 in the firewall. Go back to the section [Opening a Port in the Firewall](#opening-a-port-in-the-firewall). Make sure you are opening a UDP port, not a TCP port.
* The UDP port 1434 information is being blocked by a router. UDP communication (user datagram protocol) is not designed to pass through routers. This keeps the network from getting filled with low-priority traffic. You might be able to configure your router to forward UDP traffic, or you can decide to always provide the port number when you connect.
- * If the client computer is using Windows 7 or Windows Server 2008, (or a more recent operating system,) the UDP traffic might be dropped by the client operating system because the response from the server is returned from a different IP address than was queried. This is a security feature blocking "loose source mapping." For more information, see the **Multiple Server IP Addresses** section of the Books Online topic [Troubleshooting: Timeout Expired](http://msdn.microsoft.com/library/ms190181.aspx). This is an article from SQL Server 2008 R2, but the principals still apply. You might be able to configure the client to use the correct IP address, or you can decide to always provide the port number when you connect.
+ * If the client computer is using Windows 7 or Windows Server 2008, (or a more recent operating system,) the UDP traffic might be dropped by the client operating system because the response from the server is returned from a different IP address than was queried. This is a security feature blocking "loose source mapping." For more information, see the **Multiple Server IP Addresses** section of the Books Online topic [Troubleshooting: Timeout Expired](https://msdn.microsoft.com/library/ms190181.aspx). This is an article from SQL Server 2008 R2, but the principals still apply. You might be able to configure the client to use the correct IP address, or you can decide to always provide the port number when you connect.
3. Once you can connect using the IP address (or IP address and instance name for a named instance), attempt to connect using the computer name (or computer name and instance name for a named instance). Put `tcp:` in front of the computer name to force a TCP/IP connection. For example, for the default instance on a computer named `ACCNT27`, use `tcp:ACCNT27` For a named instance called `PAYROLL`, on that computer use `tcp:ACCNT27\PAYROLL` If you can connect using the IP address but not using the computer name, then you have a name resolution problem. Go back to the section **Testing TCP/IP Connectivity**, section 4.
diff --git a/docs/database-engine/discontinued-database-engine-functionality-in-sql-server-2016.md b/docs/database-engine/discontinued-database-engine-functionality-in-sql-server-2016.md
index aca72b7398b..4cd9f7c7b49 100644
--- a/docs/database-engine/discontinued-database-engine-functionality-in-sql-server-2016.md
+++ b/docs/database-engine/discontinued-database-engine-functionality-in-sql-server-2016.md
@@ -49,7 +49,7 @@ ms.author: mikeray
## Previous Versions
-- [Discontinued Database Engine Functionality in SQL Server 2014](http://docs.microsoft.com/sql/database-engine/discontinued-database-engine-functionality-in-sql-server-2016?view=sql-server-2014)
+- [Discontinued Database Engine Functionality in SQL Server 2014](https://docs.microsoft.com/sql/database-engine/discontinued-database-engine-functionality-in-sql-server-2016?view=sql-server-2014)
## See Also
[Deprecated Database Engine Features in SQL Server 2016](../database-engine/deprecated-database-engine-features-in-sql-server-2016.md)
diff --git a/docs/dma/dma-commandline.md b/docs/dma/dma-commandline.md
index cea88ccc40a..e7b3be8f709 100644
--- a/docs/dma/dma-commandline.md
+++ b/docs/dma/dma-commandline.md
@@ -203,7 +203,7 @@ Configuration file contents when using source connections:
```
-
+
name
Source Platform
TargetPlatform
@@ -222,7 +222,7 @@ Configuration file contents when using source connections:
Configuration file contents when importing feature discovery report:
```
-
+
name
path\to\featurediscoveryfile.json
path\to\resultfile.json
diff --git a/docs/includes/azure-sql-db-repl-for-more-information.md b/docs/includes/azure-sql-db-repl-for-more-information.md
index 36cd788ae9e..250e1a6b34e 100644
--- a/docs/includes/azure-sql-db-repl-for-more-information.md
+++ b/docs/includes/azure-sql-db-repl-for-more-information.md
@@ -1 +1 @@
-Publisher and distributor databases on Azure SQL Database require [Managed Instance](https://docs.microsoft.com/azure/sql-database/sql-database-managed-instance) for more information, see [Replication with Azure SQL Database](http://docs.microsoft.com/sql/relational-databases/replication/replication-to-sql-database).
\ No newline at end of file
+Publisher and distributor databases on Azure SQL Database require [Managed Instance](https://docs.microsoft.com/azure/sql-database/sql-database-managed-instance) for more information, see [Replication with Azure SQL Database](https://docs.microsoft.com/sql/relational-databases/replication/replication-to-sql-database).
\ No newline at end of file
diff --git a/docs/includes/ctp-support-exclusion.md b/docs/includes/ctp-support-exclusion.md
index a3bb163e2fa..5eb74a6b451 100644
--- a/docs/includes/ctp-support-exclusion.md
+++ b/docs/includes/ctp-support-exclusion.md
@@ -11,7 +11,7 @@ CTP 3.2 enables the following scenarios:
## Support
-SQL Server 2019 CTP 3.2 is preview software. It is not publicly supported for operations. Customers who are in the [SQL Early Adopter Program](http://aka.ms/sqleap), may have support to run SQL Server 2019 CTP 3.2 by special agreement, in consultation with Microsoft.
+SQL Server 2019 CTP 3.2 is preview software. It is not publicly supported for operations. Customers who are in the [SQL Early Adopter Program](https://aka.ms/sqleap), may have support to run SQL Server 2019 CTP 3.2 by special agreement, in consultation with Microsoft.
Limited support for customers not in the early adoption program may be found at one of the following locations:
diff --git a/docs/integration-services/scale-out/scale-out-support-for-high-availability.md b/docs/integration-services/scale-out/scale-out-support-for-high-availability.md
index 872ff0a5477..df28432fda2 100644
--- a/docs/integration-services/scale-out/scale-out-support-for-high-availability.md
+++ b/docs/integration-services/scale-out/scale-out-support-for-high-availability.md
@@ -92,7 +92,7 @@ Call the stored procedure `[catalog].[update_logdb_info]` with the following par
On Azure virtual machines, this configuration step requires additional steps. A full explanation of these concepts and these steps is beyond the scope of this article.
-1. You have to set up an Azure domain. Windows Server Failover Clustering requires all computers in the cluster to be members of the same domain. For more info, see [Enable Azure Active Directory Domain Services using the Azure portal](https://docs.microsoft.com/en-us/azure/active-directory-domain-services/create-instance).
+1. You have to set up an Azure domain. Windows Server Failover Clustering requires all computers in the cluster to be members of the same domain. For more info, see [Enable Azure Active Directory Domain Services using the Azure portal](https://docs.microsoft.com/azure/active-directory-domain-services/create-instance).
2. You have to set up an Azure load balancer. This is a requirement for the availability group listener. For more info, see [Tutorial: Load balance internal traffic with Basic Load Balancer to VMs using the Azure portal](https://docs.microsoft.com/azure/load-balancer/tutorial-load-balancer-basic-internal-portal).
diff --git a/docs/linux/sql-server-linux-kubernetes-deploy.md b/docs/linux/sql-server-linux-kubernetes-deploy.md
index 84c530e973e..2d78da7d7e9 100644
--- a/docs/linux/sql-server-linux-kubernetes-deploy.md
+++ b/docs/linux/sql-server-linux-kubernetes-deploy.md
@@ -30,7 +30,7 @@ On Kubernetes, the deployment includes a SQL Server operator, the SQL Server con
> [!NOTE]
> You can use any type of Kubernetes cluster. To create a Kubernetes cluster on Azure Kubernetes Service (AKS), see [Create an AKS cluster](https://docs.microsoft.com/azure/aks/create-cluster).
>
-> Use the latest version of Kubernetes. The specific version depends on your subscription and region. See [Supported Kubernetes versions in AKS](https://docs.microsoft.com/en-us/azure/aks/supported-kubernetes-versions).
+> Use the latest version of Kubernetes. The specific version depends on your subscription and region. See [Supported Kubernetes versions in AKS](https://docs.microsoft.com/azure/aks/supported-kubernetes-versions).
>
> The following script creates a four-node Kubernetes cluster in Azure. Before you run the script replace `` with the latest available version. For example `1.12.5`.
>
diff --git a/docs/master-data-services/install-windows/secure-a-master-data-manager-web-application.md b/docs/master-data-services/install-windows/secure-a-master-data-manager-web-application.md
index 40083e80706..cff6b60ca7e 100644
--- a/docs/master-data-services/install-windows/secure-a-master-data-manager-web-application.md
+++ b/docs/master-data-services/install-windows/secure-a-master-data-manager-web-application.md
@@ -55,7 +55,7 @@ ms.author: lle
12. Change `` to `` to prevent issues that may appear in the Silverlight client.
-13. Save and close the file. If you get an error, it could be because you have UAC enabled. For more information, see [Turn off User Account Control](http://technet.microsoft.com/library/cc709691\(WS.10\).aspx). Users should now be able to use HTTPS to access the site.
+13. Save and close the file. If you get an error, it could be because you have UAC enabled. For more information, see [Turn off User Account Control](https://technet.microsoft.com/library/cc709691\(WS.10\).aspx). Users should now be able to use HTTPS to access the site.
## See Also
diff --git a/docs/relational-databases/security/tutorial-getting-started-with-always-encrypted-enclaves.md b/docs/relational-databases/security/tutorial-getting-started-with-always-encrypted-enclaves.md
index 7abf3933a1a..5206634a9b6 100644
--- a/docs/relational-databases/security/tutorial-getting-started-with-always-encrypted-enclaves.md
+++ b/docs/relational-databases/security/tutorial-getting-started-with-always-encrypted-enclaves.md
@@ -31,15 +31,15 @@ To get started with Always Encrypted with secure enclaves, you need at least two
- [!INCLUDE [sssqlv15-md](../../includes/sssqlv15-md.md)] or later.
- Windows 10 Enterprise version 1809, or Windows Server 2019 Datacenter.
-- If your SQL Server computer is a physical machine, it must meet the [Hyper-V Hardware Requirements](https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/reference/hyper-v-requirements#hardware-requirements):
+- If your SQL Server computer is a physical machine, it must meet the [Hyper-V Hardware Requirements](https://docs.microsoft.com/virtualization/hyper-v-on-windows/reference/hyper-v-requirements#hardware-requirements):
- 64-bit Processor with Second Level Address Translation (SLAT)
- CPU support for VM Monitor Mode Extension (VT-c on Intel CPUs)
- Virtualization support enabled (Intel VT-x or AMD-V)
- If your SQL Server computer is a virtual machine, the VM must be configured to support Virtualization Based Security.
- - On Hyper-V 2016 or later, use a generation 1 VM and [enable nested virtualization extensions](https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/user-guide/nested-virtualization#configure-nested-virtualization) on the VM processor, or use a generation 2 VM. For more information about VM generations see [Should I create a generation 1 or 2 virtual machine in Hyper-V?](https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/plan/should-i-create-a-generation-1-or-2-virtual-machine-in-hyper-v).
+ - On Hyper-V 2016 or later, use a generation 1 VM and [enable nested virtualization extensions](https://docs.microsoft.com/virtualization/hyper-v-on-windows/user-guide/nested-virtualization#configure-nested-virtualization) on the VM processor, or use a generation 2 VM. For more information about VM generations see [Should I create a generation 1 or 2 virtual machine in Hyper-V?](https://docs.microsoft.com/windows-server/virtualization/hyper-v/plan/should-i-create-a-generation-1-or-2-virtual-machine-in-hyper-v).
- In Azure, make sure you're running a VM size that supports one of the following:
- - Nested virtualization, for example the Dv3 and Ev3 series VMs. See [Create a nesting capable Azure VM](https://docs.microsoft.com/en-us/azure/virtual-machines/windows/nested-virtualization#create-a-nesting-capable-azure-vm).
- - Generation 2 VMs, for example: the Dsv3 or Esv3 series VMs. See [Support for generation 2 VMs on Azure](https://docs.microsoft.com/en-us/azure/virtual-machines/windows/generation-2).
+ - Nested virtualization, for example the Dv3 and Ev3 series VMs. See [Create a nesting capable Azure VM](https://docs.microsoft.com/azure/virtual-machines/windows/nested-virtualization#create-a-nesting-capable-azure-vm).
+ - Generation 2 VMs, for example: the Dsv3 or Esv3 series VMs. See [Support for generation 2 VMs on Azure](https://docs.microsoft.com/azure/virtual-machines/windows/generation-2).
- On VMWare vSphere 6.7 or later, enable Virtualization Based Security support for the VM as described in the [VMware documentation](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vm_admin.doc/GUID-C2E78F3E-9DE2-44DB-9B0A-11440800AADD.html).
- Other hypervisors and public clouds may support using Always Encrypted with secure enclaves in a VM as long as virtualization extensions (sometimes called nested virtualization) are exposed to the VM. Check your virtualization solution?s documentation for compatibility and configuration instructions.
- [SQL Server Management Studio (SSMS) 18.0 or later](../../ssms/download-sql-server-management-studio-ssms.md).
diff --git a/docs/reporting-services/mobile-reports/sql-server-mobile-reports-end-to-end-walk-through.md b/docs/reporting-services/mobile-reports/sql-server-mobile-reports-end-to-end-walk-through.md
index 77c427ffa33..0765b275af9 100644
--- a/docs/reporting-services/mobile-reports/sql-server-mobile-reports-end-to-end-walk-through.md
+++ b/docs/reporting-services/mobile-reports/sql-server-mobile-reports-end-to-end-walk-through.md
@@ -33,7 +33,7 @@ To follow along, you need these products:
* OR: World Wide Importers sample database, available from the [Microsoft SQL Server Samples](../../sample/microsoft-sql-server-samples.md) page.
* To view the result:
* [Sign up for the Power BI service](https://go.microsoft.com/fwlink/?LinkID=513879) and
- * [Download the Power BI mobile app](https://docs.microsoft.com/en-us/power-bi/consumer/mobile/mobile-apps-for-mobile-devices) to your mobile device: iOS, Android phone, or Windows 10 device.
+ * [Download the Power BI mobile app](https://docs.microsoft.com/power-bi/consumer/mobile/mobile-apps-for-mobile-devices) to your mobile device: iOS, Android phone, or Windows 10 device.
## Create a shared data source
diff --git a/docs/sql-server/sql-server-privacy.md b/docs/sql-server/sql-server-privacy.md
index 7777c5b3281..6e3d04e10df 100644
--- a/docs/sql-server/sql-server-privacy.md
+++ b/docs/sql-server/sql-server-privacy.md
@@ -17,7 +17,7 @@ ms.author: aliceku
This article summarizes Internet-enabled features that can collect and send anonymous feature usage and diagnostic data to Microsoft. SQL Server may collect standard computer information and data about usage and performance may be transmitted to Microsoft and analyzed for purposes of improving the quality, security, and reliability of the product. This article serves as an addendum to the overall [Microsoft Privacy Statement](https://go.microsoft.com/fwlink/?LinkId=521839). The data classification in this article only applies to versions of the SQL Server on-premises product. It does not apply to the items:
- Azure SQL Database
-- [SQL Server Management Studio (SSMS)](https://docs.microsoft.com/en-us/sql/ssms/sql-server-management-studio-telemetry-ssms?view=sql-server-2017)
+- [SQL Server Management Studio (SSMS)](https://docs.microsoft.com/sql/ssms/sql-server-management-studio-telemetry-ssms?view=sql-server-2017)
- SQL Server Data Tools (SSDT)
- Azure Data Studio
- Database Migration Assistant
diff --git a/docs/sql-server/sql-server-ver15-release-notes.md b/docs/sql-server/sql-server-ver15-release-notes.md
index f13d77d6cc5..d310f70061a 100644
--- a/docs/sql-server/sql-server-ver15-release-notes.md
+++ b/docs/sql-server/sql-server-ver15-release-notes.md
@@ -60,7 +60,7 @@ Complete details about support and licensing for CTP releases are in `license_Ev
## Updated compiler
-- **Issue and customer impact**: [!INCLUDE[SQL Server 2019](../includes/sssqlv15-md.md)] is built with an updated compiler. CTP 2.1 had a known issue where results for floating point and other conversion scenarios may have returned a different value than previous versions because of the updated compiler. CTP 2.2 includes work to ensure that the affected scenarios return the same results as previous versions of [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)]. As of CTP 3.2 release we do not know any remaining issues. Please report any result anomalies compared to [!INCLUDE[ss2017](../includes/sssqlv14-md.md)] to [[!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] team](http://aka.ms/sqlfeedback) immediately.
+- **Issue and customer impact**: [!INCLUDE[SQL Server 2019](../includes/sssqlv15-md.md)] is built with an updated compiler. CTP 2.1 had a known issue where results for floating point and other conversion scenarios may have returned a different value than previous versions because of the updated compiler. CTP 2.2 includes work to ensure that the affected scenarios return the same results as previous versions of [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)]. As of CTP 3.2 release we do not know any remaining issues. Please report any result anomalies compared to [!INCLUDE[ss2017](../includes/sssqlv14-md.md)] to [[!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] team](https://aka.ms/sqlfeedback) immediately.
- **Workaround**: N/A
diff --git a/docs/sql-server/usage-and-diagnostic-data-configuration-for-sql-server.md b/docs/sql-server/usage-and-diagnostic-data-configuration-for-sql-server.md
index ccdc290fd02..22cb980c291 100644
--- a/docs/sql-server/usage-and-diagnostic-data-configuration-for-sql-server.md
+++ b/docs/sql-server/usage-and-diagnostic-data-configuration-for-sql-server.md
@@ -139,7 +139,7 @@ The procedure to turn this feature on or off is dependent on the OS version. To
- Windows Server 2016 and Windows 10
- [Configure Windows diagnostic data in your organization](https://docs.microsoft.com/en-us/windows/privacy/configure-windows-diagnostic-data-in-your-organization)
+ [Configure Windows diagnostic data in your organization](https://docs.microsoft.com/windows/privacy/configure-windows-diagnostic-data-in-your-organization)
- Windows Server 2008 R2 and Windows 7
[WER Settings](/windows/desktop/wer/wer-settings)
diff --git a/docs/sql-server/what-s-new-in-sql-server-ver15-prerelease.md b/docs/sql-server/what-s-new-in-sql-server-ver15-prerelease.md
index dc254af36ea..b1a1a05bfd8 100644
--- a/docs/sql-server/what-s-new-in-sql-server-ver15-prerelease.md
+++ b/docs/sql-server/what-s-new-in-sql-server-ver15-prerelease.md
@@ -554,7 +554,7 @@ Resumable online index create supports the follow scenarios:
In case of an index create failure, without this feature an online index create operation must be executed again and the operation must be restarted from the beginning.
-With this release, we extend the resumable functionality adding this feature to available [resumable online index rebuild](http://azure.microsoft.com/blog/modernize-index-maintenance-with-resumable-online-index-rebuild/).
+With this release, we extend the resumable functionality adding this feature to available [resumable online index rebuild](https://azure.microsoft.com/blog/modernize-index-maintenance-with-resumable-online-index-rebuild/).
In addition, this feature can be set as the default for a specific database using [database scoped default setting for online and resumable DDL operations](../t-sql/statements/alter-database-scoped-configuration-transact-sql.md).
diff --git a/docs/ssms/sql-server-management-studio-telemetry-ssms.md b/docs/ssms/sql-server-management-studio-telemetry-ssms.md
index cb07c1e3955..b18e93aeb11 100644
--- a/docs/ssms/sql-server-management-studio-telemetry-ssms.md
+++ b/docs/ssms/sql-server-management-studio-telemetry-ssms.md
@@ -59,4 +59,4 @@ To opt in or out of usage data collection for SSMS:
## See also
- [Configure usage and diagnostic data collection for SQL Server](../sql-server/usage-and-diagnostic-data-configuration-for-sql-server.md)
-- [Local audit for SQL Server usage and diagnostic data collection](http://msdn.microsoft.com/library/mt743085.aspx)
\ No newline at end of file
+- [Local audit for SQL Server usage and diagnostic data collection](https://msdn.microsoft.com/library/mt743085.aspx)
\ No newline at end of file