Update driver-feature-matrix.md

Update connect-with-strict-encryption.md

Update what-s-new-in-sql-server-2022.md

Update certificate-overview.md

Update what-s-new-in-sql-server-2022.md

Update encryption-and-certificate-validation.md

Update release-notes-for-oledb-driver-for-sql-server.md

Update protocols-for-mssqlserver-properties-flags-tab.md

Update and rename tds-8-and-tls-1-3.md to tds-8.md

Create tls-1-3.md

Update toc.yml

Add files via upload

Delete openpublishing.redirection.json

Add files via upload

Add files via upload

Update tds-8.md

fix redirect

fix redirect

Author: srdan-bozovic-msft

.openpublishing.redirection.json

@@ -59638,6 +59638,7 @@
     {
       "source_path": "docs/relational-databases/errors-events/mssqlserver-53-database-engine-error.md",
       "redirect_url": "/troubleshoot/sql/connect/network-related-or-instance-specific-error-occurred-while-establishing-connection",
+      "redirect_document_id": false
     },
     {
       "source_path": "azure-sql/database/sql-vulnerability-assessment.md",
@@ -59704,6 +59705,11 @@
       "redirect_url": "/sql/relational-databases/system-tables/msrepl-agent-jobs-transact-sql",
       "redirect_document_id": false
     },
+    {
+      "source_path": "docs/relational-databases/security/networking/tds-8-and-tls-1-3.md",
+      "redirect_url": "/sql/relational-databases/security/networking/tds-8",
+      "redirect_document_id": false
+    },
     {
       "source_path": "docs/ssms/object/filter-settings-object-explorer-and-utility-explorer.md",
       "redirect_url": "/sql/ssms/release-notes-ssms",

docs/connect/driver-feature-matrix.md

@@ -46,7 +46,7 @@ We wish all drivers supported every feature and spend effort to ensure feature p
 | [Table-Valued Parameters (TVP)](../relational-databases/tables/use-table-valued-parameters-database-engine.md) | [Yes](ado-net/sql/table-valued-parameters.md) | [Yes](ado-net/sql/table-valued-parameters.md) | [Yes](/dotnet/framework/data/adonet/sql/table-valued-parameters) | [Yes](/dotnet/framework/data/adonet/sql/table-valued-parameters) |
 | [MultiSubnetFailover](../relational-databases/native-client/features/sql-server-native-client-support-for-high-availability-disaster-recovery.md#connecting-with-multisubnetfailover) | [Yes](ado-net/sql/sqlclient-support-high-availability-disaster-recovery.md#connecting-with-multisubnetfailover) | [Yes](ado-net/sql/sqlclient-support-high-availability-disaster-recovery.md#connecting-with-multisubnetfailover) | [Yes](/dotnet/api/system.data.sqlclient.sqlconnectionstringbuilder.multisubnetfailover?view=netcore-1.0&preserve-view=true) | [Yes](/dotnet/api/system.data.sqlclient.sqlconnectionstringbuilder.multisubnetfailover?view=netframework-4.8&preserve-view=true) |
 | [Transparent Network IP Resolution](odbc/using-transparent-network-ip-resolution.md) | | [Yes](/dotnet/api/microsoft.data.sqlclient.sqlconnection.connectionstring?view=sqlclient-dotnet-1.1&preserve-view=true) | | [Yes](/dotnet/api/system.data.sqlclient.sqlconnection.connectionstring?view=netframework-4.8&preserve-view=true) |
-| [TDS 8.0 (strict encryption) and TLS 1.3](../relational-databases/security/networking/tds-8-and-tls-1-3.md) | Yes (v5.1+) | Yes (v5.1+) | | |
+| [TDS 8.0 (strict encryption) and TLS 1.3](../relational-databases/security/networking/tds-8.md) | Yes (v5.1+) | Yes (v5.1+) | | |
 
 | <a id="table2"></a>Feature | [ODBC Driver for SQL Server on Windows](odbc/microsoft-odbc-driver-for-sql-server.md) | [ODBC Driver for SQL Server on Linux and macOS](odbc/microsoft-odbc-driver-for-sql-server.md) | [JDBC Driver for SQL Server](jdbc/microsoft-jdbc-driver-for-sql-server.md) | [OLE DB Driver for SQL Server](oledb/oledb-driver-for-sql-server.md) |
 | :-- | :-- | :-- | :-- | :-- |
@@ -66,7 +66,7 @@ We wish all drivers supported every feature and spend effort to ensure feature p
 | [Table-Valued Parameters (TVP)](../relational-databases/tables/use-table-valued-parameters-database-engine.md) | [Yes](../relational-databases/native-client-odbc-table-valued-parameters/table-valued-parameters-odbc.md) | [Yes](../relational-databases/native-client-odbc-table-valued-parameters/table-valued-parameters-odbc.md) | [Yes](jdbc/using-table-valued-parameters.md) (v6.0+) | [Yes](oledb/ole-db-table-valued-parameters/table-valued-parameters-ole-db.md) |
 | [MultiSubnetFailover](../relational-databases/native-client/features/sql-server-native-client-support-for-high-availability-disaster-recovery.md#connecting-with-multisubnetfailover) | [Yes](../relational-databases/native-client/features/sql-server-native-client-support-for-high-availability-disaster-recovery.md#connecting-with-multisubnetfailover) | [Yes](../relational-databases/native-client/features/sql-server-native-client-support-for-high-availability-disaster-recovery.md#connecting-with-multisubnetfailover) | [Yes](jdbc/jdbc-driver-support-for-high-availability-disaster-recovery.md) | [Yes](oledb/features/oledb-driver-for-sql-server-support-for-high-availability-disaster-recovery.md#connecting-with-multisubnetfailover) |
 | [Transparent Network IP Resolution](odbc/using-transparent-network-ip-resolution.md) | [Yes](odbc/using-transparent-network-ip-resolution.md) (v13.0+) | [Yes](odbc/using-transparent-network-ip-resolution.md) (v13.1+) | [Yes](jdbc/setting-the-connection-properties.md) (v6.0+) | [Yes](oledb/features/using-transparent-network-ip-resolution.md) (v18.4+) |
-| [TDS 8.0 (strict encryption) and TLS 1.3](../relational-databases/security/networking/tds-8-and-tls-1-3.md) | Yes (v18.0+) | Yes (v18.0+) | Yes (v11.2+) | Yes (v19.2+) |
+| [TDS 8.0 (strict encryption) and TLS 1.3](../relational-databases/security/networking/tds-8.md) | Yes (v18.0+) | Yes (v18.0+) | Yes (v11.2+) | Yes (v19.2+) |
 
 | <a id="table3"></a>Feature | [Drivers for PHP for SQL Server on Windows](php/microsoft-php-driver-for-sql-server.md)<sup>[1](#note1)</sup> | [Drivers for PHP for SQL Server on Linux and macOS](php/microsoft-php-driver-for-sql-server.md)<sup>[1](#note1)</sup> | [Tedious (Node.js)](node-js/node-js-driver-for-sql-server.md) | [pyODBC (Python)](python/pyodbc/python-sql-driver-pyodbc.md)<sup>[1](#note1)</sup> |
 | :-- | :-- | :-- | :-- | :-- |
@@ -86,7 +86,7 @@ We wish all drivers supported every feature and spend effort to ensure feature p
 | [Table-Valued Parameters (TVP)](../relational-databases/tables/use-table-valued-parameters-database-engine.md) | [Yes](php/use-table-valued-parameters.md) (v5.10+) | [Yes](php/use-table-valued-parameters.md) (v5.10+) | [Yes](https://tediousjs.github.io/tedious/parameters.html) | Yes |
 | [MultiSubnetFailover](../relational-databases/native-client/features/sql-server-native-client-support-for-high-availability-disaster-recovery.md#connecting-with-multisubnetfailover) | [Yes](php/php-driver-for-sql-server-support-for-high-availability-disaster-recovery.md) | [Yes](php/php-driver-for-sql-server-support-for-high-availability-disaster-recovery.md) | | [Yes](../relational-databases/native-client/features/sql-server-native-client-support-for-high-availability-disaster-recovery.md#connecting-with-multisubnetfailover) |
 | [Transparent Network IP Resolution](odbc/using-transparent-network-ip-resolution.md) | [Yes](php/php-driver-for-sql-server-support-for-high-availability-disaster-recovery.md) | [Yes](php/php-driver-for-sql-server-support-for-high-availability-disaster-recovery.md) | | [Yes](odbc/using-transparent-network-ip-resolution.md) |
-| [TDS 8.0 (strict encryption) and TLS 1.3](../relational-databases/security/networking/tds-8-and-tls-1-3.md) | Yes (v5.10+) | Yes (v5.10+) | | Yes |
+| [TDS 8.0 (strict encryption) and TLS 1.3](../relational-databases/security/networking/tds-8.md) | Yes (v5.10+) | Yes (v5.10+) | | Yes |
 
 <a id="note1"></a><sup>1</sup> Since these drivers rely on the Microsoft ODBC Driver for SQL Server, a version of that driver that supports the feature must also be used.
 

docs/connect/oledb/features/encryption-and-certificate-validation.md

@@ -64,7 +64,7 @@ The following table describes the resulting encryption and validation:
 > The preceding table only provides a guide on the system behavior under different configurations. For secure connectivity, ensure that the client and server both require encryption (for server-side configuration, see [Configure encryption settings in SQL Server](../../../database-engine/configure-windows/configure-sql-server-encryption.md#step-2-configure-encryption-settings-in-sql-server)). Also ensure that the server has a verifiable certificate, and that the **`TrustServerCertificate`** setting on the client is set to FALSE.
 
 > [!NOTE]
-> Starting from version 19.2 of the OLE DB driver, TDS 8.0 connections can be configured to use TLS 1.3. For more information, see [TLS 1.3 support](../../../relational-databases/security/networking/tds-8-and-tls-1-3.md).
+> Starting from version 19.2 of the OLE DB driver, TDS 8.0 connections can be configured to use TLS 1.3. For more information, see [TLS 1.3 support](../../../relational-databases/security/networking/tls-1-3.md).
 
 ### Major version 18 with new authentication methods
 

docs/connect/oledb/release-notes-for-oledb-driver-for-sql-server.md

@@ -84,7 +84,7 @@ If you need to download the installer in a language other than the one detected
 
 | Feature added | Details |
 | :------------ | :------ |
-| Support for TLS 1.3 | TDS 8.0 connections can now be configured to use TLS 1.3. For more details, see [TLS 1.3 support](../../relational-databases/security/networking/tds-8-and-tls-1-3.md). |
+| Support for TLS 1.3 | TDS 8.0 connections can now be configured to use TLS 1.3. For more details, see [TLS 1.3 support](../../relational-databases/security/networking/tls-1-3.md). |
 | Support for the `Server Certificate` connection string keyword, and the `SSPROP_INIT_SERVER_CERTIFICATE` initialization property | The user may now specify the path to a certificate file to match against the SQL Server TLS/SSL certificate. <br/><br/>For more information, see: [Using connection string keywords](applications/using-connection-string-keywords-with-oledb-driver-for-sql-server.md). |
 
 ## 19.1.0

docs/database-engine/configure-windows/certificate-overview.md

@@ -27,7 +27,7 @@ Enabling TLS encryption increases the security of data transmitted across networ
 - Packets sent from the instance of SQL Server to the application must be encrypted by the server TLS stack and decrypted by the client TLS stack.
 
 > [!IMPORTANT]  
-> Starting with SQL Server 2016 (13.x), Secure Sockets Layer (SSL) has been discontinued. Use TLS (TLS 1.2 is recommended) instead. For more information, see [KB3135244 - TLS 1.2 support for Microsoft SQL Server](https://support.microsoft.com/topic/kb3135244-tls-1-2-support-for-microsoft-sql-server-e4472ef8-90a9-13c1-e4d8-44aad198cdbe). SQL Server 2022 introduces support for TLS 1.3. For more information, see [TDS 8.0 and TLS 1.3 support](../../relational-databases/security/networking/tds-8-and-tls-1-3.md).
+> Starting with SQL Server 2016 (13.x), Secure Sockets Layer (SSL) has been discontinued. Use TLS (TLS 1.2 is recommended) instead. For more information, see [KB3135244 - TLS 1.2 support for Microsoft SQL Server](https://support.microsoft.com/topic/kb3135244-tls-1-2-support-for-microsoft-sql-server-e4472ef8-90a9-13c1-e4d8-44aad198cdbe). SQL Server 2022 introduces support for TLS 1.3. For more information, see [TLS 1.3 support](../../relational-databases/security/networking/tls-1-3.md).
 > If no matching protocols exist between the client and server computer, you can run into the error described in [An existing connection was forcibly closed by the remote host](/troubleshoot/sql/connect/tls-exist-connection-closed).
 
 ## Digital certificate overview
@@ -55,4 +55,4 @@ To prove that a certificate holder is who they claim to be, the certificate must
 | --- | --- | --- | --- |
 | Certificate subject match | The certificate's **Subject** field contains the common name (CN) of the host. For example, the certificate that's issued to `www.contoso.com` can be used for the web site `https://www.contoso.com`. | - Compatible with all clients, devices, and services.<br /><br />- Compartmentalization. Revoking the certificate for a host doesn't affect other hosts. | - Number of certificates required. You can only use the certificate for the specified host. For example, you can't use the `www.contoso.com` certificate for `ftp.contoso.com`, even when the services are installed on the same server.<br /><br />- Complexity. On a web server, each certificate requires its own IP address binding. |
 | Certificate subject alternative name (SAN) match | In addition to the **Subject** field, the certificate's **Subject Alternative Name** field contains a list of multiple host names. For example:<br />`www.contoso.com`<br />`ftp.contoso.com`<br />`ftp.eu.fabirkam.net` | - Convenience. You can use the same certificate for multiple hosts in multiple, separate domains.<br /><br />- Most clients, devices, and services support SAN certificates.<br /><br />- Auditing and security. You know exactly which hosts are capable of using the SAN certificate. | - More planning required. You need to provide the list of hosts when you create the certificate.<br /><br />- Lack of compartmentalization. You can't selectively revoke certificates for some of the specified hosts without affecting all of the hosts in the certificate. |
-| Wildcard certificate match | The certificate's **Subject** field contains the common name as the wildcard character (*) plus a single domain or subdomain. For example, `*.contoso.com` or `*.eu.contoso.com`. The `*.contoso.com` wildcard certificate can be used for:<br />`www.contoso.com`<br />`ftp.contoso.com`<br />`mail.contoso.com` | Flexibility. You don't need to provide a list of hosts when you request the certificate, and you can use the certificate on any number of hosts that you may need in the future. | - You can't use wildcard certificates with other top-level domains (TLDs). For example, you can't use the `*.contoso.com` wildcard certificate for `*.contoso.net` hosts.<br /><br />- You can only use wildcard certificates for host names at the level of the wildcard. For example, you can't use the `*.contoso.com` certificate for `www.eu.contoso.com`. Or, you can't use the `*.eu.contoso.com` certificate for `www.uk.eu.contoso.com`.<br /><br />- Older clients, devices, applications, or services might not support wildcard certificates.<br /><br />- Wildcards aren't available with Extended Validation (EV) certificates.<br /><br />- Careful auditing and control are required. If the wildcard certificate is compromised, it affects every host in the specified domain. |
+| Wildcard certificate match | The certificate's **Subject** field contains the common name as the wildcard character (*) plus a single domain or subdomain. For example, `*.contoso.com` or `*.eu.contoso.com`. The `*.contoso.com` wildcard certificate can be used for:<br />`www.contoso.com`<br />`ftp.contoso.com`<br />`mail.contoso.com` | Flexibility. You don't need to provide a list of hosts when you request the certificate, and you can use the certificate on any number of hosts that you may need in the future. | - You can't use wildcard certificates with other top-level domains (TLDs). For example, you can't use the `*.contoso.com` wildcard certificate for `*.contoso.net` hosts.<br /><br />- You can only use wildcard certificates for host names at the level of the wildcard. For example, you can't use the `*.contoso.com` certificate for `www.eu.contoso.com`. Or, you can't use the `*.eu.contoso.com` certificate for `www.uk.eu.contoso.com`.<br /><br />- Older clients, devices, applications, or services might not support wildcard certificates.<br /><br />- Wildcards aren't available with Extended Validation (EV) certificates.<br /><br />- Careful auditing and control are required. If the wildcard certificate is compromised, it affects every host in the specified domain. |

docs/relational-databases/security/networking/connect-with-strict-encryption.md

@@ -28,7 +28,7 @@ In this article, we'll show you how to connect to [!INCLUDE [sssql22-md](../../.
 
 ## Connect to SQL Server using a .NET application
 
-For information on building and connecting to SQL Server using the `strict` encryption type, see [Connection String Syntax](/dotnet/framework/data/adonet/connection-string-syntax) on how to properly build the connection string. For more information on the new connection string properties, see [Additional changes to connection string encryption properties](./tds-8-and-tls-1-3.md#additional-changes-to-connection-string-encryption-properties).
+For information on building and connecting to SQL Server using the `strict` encryption type, see [Connection String Syntax](/dotnet/framework/data/adonet/connection-string-syntax) on how to properly build the connection string. For more information on the new connection string properties, see [Additional changes to connection string encryption properties](./tds-8.md#additional-changes-to-connection-string-encryption-properties).
 
 ## Connect using an ODBC DSN
 
@@ -90,4 +90,4 @@ If you see `SSL certificate validation failed`, validate that:
 
 ## See also
 
-- [TDS 8.0 and TLS 1.3 support](tds-8-and-tls-1-3.md)
+- [TDS 8.0](tds-8.md)