Merge pull request #29397 from MicrosoftDocs/main

PhilKang0704 · web-flow · commit a2dedc63bc5c · 2023-12-23T02:34:40.000+08:00
12/22/2023 AM Publish
diff --git a/azure-sql/database/standby-replica-how-to-configure.md b/azure-sql/database/standby-replica-how-to-configure.md
@@ -31,7 +31,7 @@ You designate a replica for standby when you configure a new [active geo-replica
 
 While active geo-replication supports adding four secondary replicas, you can only designate one secondary database replica for standby. Failover groups support one secondary database replica per primary database, and it can be either readable, or standby. 
 
-During planned or unplanned failover, the standby replica becomes the new primary and starts to incur regular vCore licensing costs while the original primary becomes the new standby secondary, and stops incurring vCore licensings costs. 
+During planned or unplanned failover, the standby replica becomes the new primary and starts to incur regular vCore licensing costs while the original primary becomes the new standby secondary, and stops incurring vCore licensing costs. 
 
 ## Cost benefit
 
@@ -210,7 +210,7 @@ To remove a standby replica with the Azure CLI, use [az sql db replica delete-li
 
 -  What are the approximate savings with a standby replica? 
 
-   Without licensing costs, a standby replica is about 35-40% less expensive than a regular fully readable secondary replica, though savings vary by region. For a more accurate price, use the [Azure Pricing Calculator](https://azure.microsoft.com/pricing/calculator/) and set the SQL license to _Azure Hybrid Benefit_.
+   Without licensing costs, a standby replica can save between 35 to 40 percent compared to a regular fully readable secondary replica, though savings vary by region. For accurate pricing, use the [Azure Pricing Calculator](https://azure.microsoft.com/pricing/calculator/) and set the SQL Server license to _Azure Hybrid Benefit_.
 
 - How many vCores will be license-free for the standby replica? 
 
diff --git a/docs/database-engine/configure-windows/certificate-requirements.md b/docs/database-engine/configure-windows/certificate-requirements.md
@@ -32,7 +32,7 @@ For using TLS for [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)]
 
 - When connecting to an availability group listener, the certificates that are provisioned for each participating server node in the failover cluster should also have a list of all availability group listeners set in the **Subject Alternate Name** of the certificate. For more information, see [Listeners and TLS/SSL certificates](../availability-groups/windows/listeners-client-connectivity-application-failover.md#SSLcertificates). For more information on SQL Always On, see [Connect to an Always On availability group listener](../availability-groups/windows/listeners-client-connectivity-application-failover.md).
 
-- The **Subject Alternate Name** should include all the names your clients may use to connect to a [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] instance.
+- The **Subject Alternate Name** should include all the names your clients may use to connect to a [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] instance. If using Availability Groups, the Subject Alternate Name should include the NetBIOS and Fully Qualified Domain Name (FQDN) of the localhost and created listeners.
 
 The client must be able to verify the ownership of the certificate used by the server. If the client has the public key certificate of the certification authority that signed the server certificate, no further configuration is necessary. Microsoft Windows includes the public key certificates of many certification authorities. If the server certificate was signed by a public or private certification authority for which the client doesn't have the public key certificate, you must install the public key certificate of the certification authority that signed the server certificate on each client that is going to connect to [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)].
 
diff --git a/docs/linux/includes/odbc-ubuntu.md b/docs/linux/includes/odbc-ubuntu.md
@@ -24,6 +24,12 @@ Use the following steps to install the **mssql-tools18** on Ubuntu.
 
 1. Register the Microsoft Ubuntu repository.
 
+   - For Ubuntu 22.04, use the following command:
+
+     ```bash
+     curl https://packages.microsoft.com/config/ubuntu/22.04/prod.list | sudo tee /etc/apt/sources.list.d/mssql-release.list
+     ```
+
    - For Ubuntu 20.04, use the following command:
 
      ```bash
diff --git a/docs/relational-databases/security/encryption/configure-always-encrypted-keys-using-ssms.md b/docs/relational-databases/security/encryption/configure-always-encrypted-keys-using-ssms.md
@@ -4,7 +4,7 @@ description: Learn how to provision column master keys and column encryption key
 author: jaszymas
 ms.author: jaszymas
 ms.reviewer: vanto
-ms.date: 04/15/2021
+ms.date: 12/21/2023
 ms.service: sql
 ms.subservice: security
 ms.topic: conceptual
@@ -16,47 +16,47 @@ helpviewer_keywords:
 monikerRange: "=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current"
 ---
 # Provision Always Encrypted keys using SQL Server Management Studio
+
 [!INCLUDE [SQL Server Azure SQL Database Azure SQL Managed Instance](../../../includes/applies-to-version/sql-asdb-asdbmi.md)]
 
-This article provides the steps to provision column master keys and column encryption keys for Always Encrypted using [SQL Server Management Studio (SSMS)](../../../ssms/download-sql-server-management-studio-ssms.md).
+This article provides the steps to provision column master keys and column encryption keys for Always Encrypted using SQL Server Management Studio (SSMS). Make sure you install [the latest general availability (GA) version of SSMS](../../../ssms/download-sql-server-management-studio-ssms.md) when provisioning encryption keys.
 
 For an overview of Always Encrypted key management, including best practice recommendations and important security considerations, see [Overview of key management for Always Encrypted](overview-of-key-management-for-always-encrypted.md).
 
-<a name="provisioncmk"></a>
 ## Provision Column Master Keys with the New Column Master Key Dialog
 
 The **New Column Master Key** dialog allows you to generate a column master key or pick an existing key in a key store, and create column master key metadata for the created or selected key in the database.
 
-1.	Using **Object Explorer**, navigate to the **Security>Always Encrypted Keys** folder under your database.
-2.	Right-click on the **Column Master Keys** folder and select **New Column Master Key...**. 
-3.	In the **New Column Master Key** dialog, enter the name of the column master key metadata object.
-4.	Select a key store:
-    - **Certificate Store - Current User** - indicates the Current User certificate store location in the Windows Certificate Store, which is your personal store. 
+1. Using **Object Explorer**, navigate to the **Security -> Always Encrypted Keys** node under your database.
+1. Right-click on the **Column Master Keys** node and select **New Column Master Key...**.
+1. In the **New Column Master Key** dialog, enter the name of the column master key metadata object.
+1. Select a key store:
+    - **Certificate Store - Current User** - indicates the Current User certificate store location in the Windows Certificate Store, which is your personal store.
     - **Certificate Store - Local computer** - indicates the Local computer certificate store location in the Windows Certificate Store. 
-    - **Azure Key Vault** -  you'll need to sign in to Azure (click **Sign in**). Once you sign in, you'll be able to pick one of your Azure subscriptions and a key vault or a managed HSM (requires SSMS 18.9 or later).
+    - **Azure Key Vault** -  you need to sign in to Azure (click **Sign in**). Once you sign in, you are able to select one of your Azure subscriptions and a key vault or a managed HSM (requires SSMS 18.9 or later).
         > [!NOTE]
         > The **New Column Master Key** dialog does not currently support key vaults using role permissions for authorization. Only key vaults using access policies are supported.
 
         > [!NOTE]
         > Using column master keys stored in a [managed HSM](/azure/key-vault/managed-hsm/overview) in Azure Key Vault requires SSMS 18.9 or a later version.
 
     - **Key Store Provider (KSP)** - indicates a key store that is accessible via a key store provider (KSP) that implements the Cryptography Next Generation (CNG) API. Typically, this type of a store is a hardware security module (HSM). After you select this option, you'll need to pick a KSP. **Microsoft Software Key Store Provider** is selected by default. If you want to use a column master key stored in an HSM, select a KSP for your device (it must be installed and configured on the computer before you open the dialog).
-    -	**Cryptographic Service Provider (CSP)** - a key store that is accessible via a cryptographic service provider (CSP) that implements the Cryptography API (CAPI). Typically, such a store is a hardware security module (HSM). After you select this option, you'll need to pick a CSP.  If you want to use a column master key stored in an HSM, select a CSP for your device (it must be installed and configured on the computer before you open the dialog).
-    
+    -	**Cryptographic Service Provider (CSP)** - a key store that is accessible via a cryptographic service provider (CSP) that implements the Cryptography API (CAPI). Typically, such a store is a hardware security module (HSM). After you select this option, you'll need to pick a CSP. If you want to use a column master key stored in an HSM, select a CSP for your device (it must be installed and configured on the computer before you open the dialog).
+
     > [!NOTE]
     > Since CAPI is a deprecated API, the Cryptographic Service Provider (CAPI) option is disabled by default. You can enable by creating the CAPI Provider Enabled DWORD value under the **[HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\sql13\Tools\Client\Always Encrypted]** key in Windows Registry, and setting it to 1. You should use CNG instead of CAPI, unless your key store does not support CNG.
-   
+
     For more information about the above key stores, see [Create and store column master keys for Always Encrypted](create-and-store-column-master-keys-always-encrypted.md).
 
-5. If you're using [!INCLUDE [sssql19-md](../../../includes/sssql19-md.md)] and your SQL Server instance is configured with a secure enclave, you can select the **Allow enclave computations** checkbox to make the master key enclave-enabled. See [Always Encrypted with secure enclaves](always-encrypted-enclaves.md) for details. 
+1. If you're using [!INCLUDE [sssql19-md](../../../includes/sssql19-md.md)] and your SQL Server instance is configured with a secure enclave, you can select the **Allow enclave computations** checkbox to make the master key enclave-enabled. See [Always Encrypted with secure enclaves](always-encrypted-enclaves.md) for details. 
 
     > [!NOTE]
     > The **Allow enclave computations** checkbox does not appear if your SQL Server instance is not correctly configured with a secure enclave.
 
-6.	Pick an existing key in your key store, or click the **Generate Key** or **Generate Certificate** button, to create a key in the key store. 
-7.	Click **OK** and the new key will show up in the list. 
+1. Pick an existing key in your key store, or click the **Generate Key** or **Generate Certificate** button, to create a key in the key store. 
+1. Click **OK** and the new key appears in the list.
 
-Once you complete the dialog, SQL Server Management Studio creates metadata for your column master key in the database. The dialog achieves this by generating and issuing a [CREATE COLUMN MASTER KEY (Transact-SQL)](../../../t-sql/statements/create-column-master-key-transact-sql.md) statement.
+Once you complete the dialog, SQL Server Management Studio creates metadata for your column master key in the database. The dialog generates and issues a [CREATE COLUMN MASTER KEY (Transact-SQL)](../../../t-sql/statements/create-column-master-key-transact-sql.md) statement.
 
 ::: moniker range=">=sql-server-ver15"
 
@@ -66,20 +66,19 @@ If you're configuring an enclave-enabled column master key, SSMS also signs the
 
 ### Permissions for provisioning a column master key
 
-You need the *ALTER ANY COLUMN MASTER KEY* database permission in the database for the dialog to create a column master key. You also need key store permissions to access and use your key column master key. For detailed information on key store permissions required for key management operations, go to [Create and store column master keys for Always Encrypted](create-and-store-column-master-keys-always-encrypted.md) and find a section relevant for your key store.
+You need the *ALTER ANY COLUMN MASTER KEY* database permission in the database for the dialog to create a column master key. You also need key store permissions to access and use your key column master key. For detailed information on key store permissions required for key management operations, see [Create and store column master keys for Always Encrypted](create-and-store-column-master-keys-always-encrypted.md) and review the section relevant for your key store.
 
-<a name="provisioncek"></a> 
 ## Provision Column Encryption Keys with the New Column Encryption Key Dialog
 
 The **New Column Encryption Key** dialog allows you to generate a column encryption key, encrypt it with a column master key, and create the column encryption key metadata in the database.
 
-1.	Using **Object Explorer**, navigate to the **Security/Always Encrypted Keys** folder under your database.
-2.	Right-click on the **Column Encryption Keys** folder and select **New Column Encryption Key...**. 
-3.	In the **New Column Encryption Key** dialog, enter the name of the column encryption key metadata object.
-4.	Select a metadata object that represents your column master key in the database.
-5.	Click **OK**. 
+1. Using **Object Explorer**, navigate to the **Security/Always Encrypted Keys** folder under your database.
+1. Right-click on the **Column Encryption Keys** folder and select **New Column Encryption Key...**.
+1. In the **New Column Encryption Key** dialog, enter the name of the column encryption key metadata object.
+1. Select a metadata object that represents your column master key in the database.
+1. Click **OK**.
 
-Once you complete the dialog, SQL Server Management Studio generates a new column encryption key and then it retrieves the metadata for the column master key you selected from the database. SSMS then uses the column master key metadata to contact the key store containing your column master key and encrypt the column encryption key. Finally, SSMS creates the metadata data for the new column encryption in the database by generating and issuing a [CREATE COLUMN ENCRYPTION KEY (Transact-SQL)](../../../t-sql/statements/create-column-encryption-key-transact-sql.md) statement.
+Once you complete the dialog, SQL Server Management Studio (SSMS) generates a new column encryption key.  SSMS then retrieves the metadata for the column master key you selected from the database. SSMS then uses the column master key metadata to contact the key store containing your column master key and encrypt the column encryption key. Finally, SSMS creates the metadata data for the new column encryption in the database by generating and issuing a [CREATE COLUMN ENCRYPTION KEY (Transact-SQL)](../../../t-sql/statements/create-column-encryption-key-transact-sql.md) statement.
 
 > [!NOTE]
 > Using column master keys stored in a [managed HSM](/azure/key-vault/managed-hsm/overview) in Azure Key Vault requires SSMS 18.9 or a later version.
@@ -93,13 +92,15 @@ You need the *ALTER ANY COLUMN ENCRYPTION KEY* and *VIEW ANY COLUMN MASTER KEY D
 The [Always Encrypted Wizard](always-encrypted-wizard.md) is a tool for encrypting, decrypting, and re-encrypting selected database columns. While it can use already configured keys, it also allows you to generate a new column master key and a new column encryption. 
 
 ## Next Steps
+
 - [Configure column encryption using Always Encrypted Wizard](always-encrypted-wizard.md)
 - [Configure column encryption using Always Encrypted with a DAC package](configure-always-encrypted-using-dacpac.md)
 - [Rotate Always Encrypted keys using SQL Server Management Studio](rotate-always-encrypted-keys-using-ssms.md)
 - [Develop applications using Always Encrypted](always-encrypted-client-development.md)
 - [Migrate data to or from columns using Always Encrypted with SQL Server Import and Export Wizard](always-encrypted-migrate-using-import-export-wizard.md)
 
 ## See Also
+
 - [Always Encrypted](always-encrypted-database-engine.md)
 - [Overview of key management for Always Encrypted](overview-of-key-management-for-always-encrypted.md)
 - [Create and store column master keys for Always Encrypted](create-and-store-column-master-keys-always-encrypted.md)
diff --git a/docs/ssms/general-user-interface-elements.md b/docs/ssms/general-user-interface-elements.md
@@ -1,9 +1,10 @@
 ---
 title: "General User Interface Elements"
 description: "General User Interface Elements"
-author: "markingmyname"
-ms.author: "maghan"
-ms.date: "01/19/2017"
+author: erinstellato-ms
+ms.author: erinstellato
+ms.reviewer: maghan
+ms.date: 12/21/2023
 ms.service: sql
 ms.subservice: ssms
 ms.topic: ui-reference
@@ -23,7 +24,7 @@ The **Editor**, the **Properties** window, and the **Toolbox** are some of the b
 Describes the dialog box that provides information about SQL Server Management Studio and about the computer that it is running on.  
   
 [SQL Server Management Studio Web Browser](../ssms/sql-server-management-studio-web-browser.md)  
-Describes how SQL Server Management Studio hosts a Web browser in a document window.  
+Describes how SQL Server Management Studio invokes a web browser.  
   
 [External Tools Dialog Box](../ssms/external-tools-dialog-box.md)  
 Allows you to add tools to the **Tools** menu that are not part of SQL Server Management Studio.  
diff --git a/docs/ssms/sql-server-management-studio-web-browser.md b/docs/ssms/sql-server-management-studio-web-browser.md
@@ -1,9 +1,10 @@
 ---
 title: Web Browser
 description: "SQL Server Management Studio Web Browser"
-author: markingmyname
-ms.author: maghan
-ms.date: 01/19/2017
+author: erinstellato-ms
+ms.author: erinstellato
+ms.reviewer: maghan
+ms.date: 12/21/2023
 ms.service: sql
 ms.subservice: ssms
 ms.topic: ui-reference
@@ -17,8 +18,17 @@ helpviewer_keywords:
 
 [!INCLUDE[SQL Server Azure SQL Database Synapse Analytics PDW](../includes/applies-to-version/sql-asdb-asdbmi-asa-pdw.md)]
 
-SQL Server Management Studio hosts a version of Microsoft Internet Explorer. This Web browser allows you to browse URLs, and view MSDN Library help topics without leaving SQL Server Management Studio. You can access the Web browser by pointing to **Web Browser** on the **View** menu, and then clicking **Show Browser**.
+SQL Server Management Studio (SSMS) can invoke a web browser through menu items, when selecting a URL in the query editor, or when using Microsoft Entra authentication.  
+
+## Web browser configuration
+
+To control what browser is invoked from SSMS, change the setting, **Use system default web browser**. Within **Tools > Options**, select **Azure Services**, and within **Miscellaneous**, alter the setting.
+
+- The default value for **Use system default web browser** is *False* starting with SSMS 19.1. When set to *False*, SSMS uses the default browser configured for the user's workstation. This value isn't changed when upgrading from an earlier version of SSMS to version 19.1 or higher.  
+
+- For SSMS 19.0.2 and below, the default value is *True*. When set to *True*, SSMS invokes Microsoft Internet Explorer for Microsoft Entra authentication. Internet Explorer was retired in June 2022. If you encounter an error message titled `Unsupported browser`, change **Use system default web browser** to *False* and configure the default browser for the workstation.
 
 ## See Also
 
-[General User Interface Elements](../ssms/general-user-interface-elements.md)
+- [General User Interface Elements](../ssms/general-user-interface-elements.md)
+- [Options (Azure Services)](menu-help/options-azure-services.md)
diff --git a/docs/ssms/support-policy.md b/docs/ssms/support-policy.md
