Merge pull request #29060 from rwestMSFT/rw-1114-ssms-f1-articles

Refresh SSMS F1 articles

Author: v-regandowner

docs/ssms/f1-help/connect-to-any-sql-server-component-from-sql-server-management-studio.md

@@ -1,10 +1,10 @@
 ---
 title: Connect to Any SQL Server Component
-description: "Connect to Any SQL Server Component from SQL Server Management Studio"
+description: Connect to Any SQL Server Component from SQL Server Management Studio.
 author: markingmyname
 ms.author: maghan
 ms.reviewer: randolphwest
-ms.date: 04/03/2023
+ms.date: 11/16/2023
 ms.service: sql
 ms.subservice: ssms
 ms.topic: ui-reference
@@ -16,22 +16,22 @@ helpviewer_keywords:
 ---
 # Connect to any SQL Server component from SQL Server Management Studio
 
-[!INCLUDE[SQL Server Azure SQL Database Synapse Analytics PDW](../../includes/applies-to-version/sql-asdb-asdbmi-asa-pdw.md)]
+[!INCLUDE [SQL Server Azure SQL Database Synapse Analytics PDW](../../includes/applies-to-version/sql-asdb-asdbmi-asa-pdw.md)]
 
-SQL Server Management Studio provides functionality for managing every component of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. Use Management Studio to connect to:
+SQL Server Management Studio provides functionality for managing every component of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)]. Use Management Studio to connect to:
 
-- An instance of the [!INCLUDE[ssDEnoversion](../../includes/ssdenoversion-md.md)].
+- An instance of the [!INCLUDE [ssDEnoversion](../../includes/ssdenoversion-md.md)].
 
-- [!INCLUDE[ssASnoversion](../../includes/ssasnoversion-md.md)].
+- [!INCLUDE [ssASnoversion](../../includes/ssasnoversion-md.md)].
 
-- [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)].
+- [!INCLUDE [ssISnoversion](../../includes/ssisnoversion-md.md)].
 
-- [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)].
+- [!INCLUDE [ssRSnoversion](../../includes/ssrsnoversion-md.md)].
 
-Although Management Studio allows you to work with queries without first establishing a connection to a data source, most other tasks require a connection. Management Studio provides the **Connect to Server** dialog box to configure connection properties to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] components. When Management Studio starts, it opens the **Connect to Server** dialog box and prompts you to connect to a server. The **Connect to Server** dialog box retains the connection settings from the last time it was used.
+Although Management Studio allows you to work with queries without first establishing a connection to a data source, most other tasks require a connection. Management Studio provides the **Connect to Server** dialog box to configure connection properties to [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] components. When Management Studio starts, it opens the **Connect to Server** dialog box and prompts you to connect to a server. The **Connect to Server** dialog box retains the connection settings from the last time it was used.
 
 > [!NOTE]  
-> This feature can be turned off so no connection is automatically initiated. For more information, see [Database Engine Service Startup Options](../../database-engine/configure-windows/database-engine-service-startup-options.md).
+> This feature can be turned off so no connection is automatically initiated. For more information, see [Database Engine Service startup options](../../database-engine/configure-windows/database-engine-service-startup-options.md).
 
 ## Save connections
 
@@ -43,9 +43,9 @@ When you register a server, Management Studio saves the connection information i
 
 ### Save connections in Solution Explorer
 
-Solution Explorer allows you to store related queries, scripts, connections, and other associated information in a project. Each script project contains a node called **Connections**, where you can save one or more connections. To add a connection, right-click **Connections**, and then select **New Connection**. To access a saved connection, expand **Connections** and double-click the connection Management Studio opens a query window associated with that connection. When saved, scripts retain their association to a specific connection.
+Solution Explorer allows you to store related queries, scripts, connections, and other associated information in a project. Each script project contains a node called **Connections**, where you can save one or more connections. To add a connection, right-click **Connections**, and then select **New Connection**. To access a saved connection, expand **Connections** and double-click the connection. Management Studio opens a query window associated with that connection. When saved, scripts retain their association to a specific connection.
 
-## See also
+## Related content
 
-- [Use SQL Server Management Studio](../sql-server-management-studio-ssms.md)
-- [Object Explorer](../../ssms/object/object-explorer.md)
+- [What is SQL Server Management Studio (SSMS)?](../sql-server-management-studio-ssms.md)
+- [Object Explorer](../object/object-explorer.md)

docs/ssms/f1-help/connect-to-microsoft-azure-storage.md

@@ -1,9 +1,10 @@
 ---
 title: Connect to Microsoft Azure Storage
-description: "Connect to Microsoft Azure Storage"
+description: Connect to Microsoft Azure Storage.
 author: markingmyname
 ms.author: maghan
-ms.date: 07/12/2017
+ms.reviewer: randolphwest
+ms.date: 11/16/2023
 ms.service: sql
 ms.subservice: ssms
 ms.topic: ui-reference
@@ -13,24 +14,24 @@ f1_keywords:
 
 # Connect to Microsoft Azure Storage
 
-[!INCLUDE[SQL Server Azure SQL Database Synapse Analytics PDW](../../includes/applies-to-version/sql-asdb-asdbmi-asa-pdw.md)]
-Use the **Azure Storage Connection** dialog to specify a storage account and validate your connection to Azure.  
-  
+[!INCLUDE [SQL Server Azure SQL Database Synapse Analytics PDW](../../includes/applies-to-version/sql-asdb-asdbmi-asa-pdw.md)]
+
+Use the **Azure Storage Connection** dialog to specify a storage account and validate your connection to Azure.
+
 ## Options
 
-Specify the following information about your Azure account, and then select **Next** to continue.  
+Specify the following information about your Azure account, and then select **Next** to continue.
 
 1. **Storage Account** - Specify the storage account name.
 
-   >[!NOTE]
-   > You can only connect to [General-purpose Storage Accounts](/azure/storage/common/storage-introduction#azure-storage-services). Connecting to other types of storage accounts can result in an error similar to the following:
-   >
+   You can only connect to [General-purpose Storage Accounts](/azure/storage/common/storage-introduction#azure-storage-services). Connecting to other types of storage accounts can result in an error similar to the following example:
+
    > The value for one of the HTTP headers is not in the correct format. (Microsoft.SqlServer.StorageClient).
-   >
+   >  
    > The remote server returned an error: (400) Bad Request. (System)
 
-2. **Account Key** - Specify the account key for the specified storage account.  
-  
-3. **Use secure endpoints (HTTPS)** - This option utilizes encrypted communication and secure identification of a network web server.  
-  
-4. **Save account key** - This option saves your password in an encrypted file.  
+1. **Account Key** - Specify the account key for the specified storage account.
+
+1. **Use secure endpoints (HTTPS)** - This option utilizes encrypted communication and secure identification of a network web server.
+
+1. **Save account key** - This option saves your password in an encrypted file.

docs/ssms/f1-help/connect-to-server-additional-connection-parameters-page-database-engine.md

@@ -1,44 +1,44 @@
 ---
 title: Connect to Server (Additional Connection Parameters page) Database Engine
-description: "Connect to Server (Additional Connection Parameters page) Database Engine"
+description: Connect to Server (Additional Connection Parameters page) Database Engine.
 author: erinstellato-ms
 ms.author: erinstellato
 ms.reviewer: maghan, randolphwest
-ms.date: 11/06/2023
+ms.date: 11/16/2023
 ms.service: sql
 ms.subservice: ssms
 ms.topic: ui-reference
 f1_keywords:
   - "sql13.swb.connecttosqlserver.additionalconnparams.f1"
 ---
 
-# Connect to Server (Additional Connection Parameters Page) Database Engine
+# Connect to Server (Additional Connection Parameters page) - Database Engine
 
-[!INCLUDE[SQL Server Azure SQL Database Synapse Analytics PDW](../../includes/applies-to-version/sql-asdb-asdbmi-asa-pdw.md)]
+[!INCLUDE [SQL Server Azure SQL Database Synapse Analytics PDW](../../includes/applies-to-version/sql-asdb-asdbmi-asa-pdw.md)]
+
+Use this tab to enter advanced parameters when connecting to an instance of [!INCLUDE [msCoName](../../includes/msconame-md.md)] [!INCLUDE [ssDEnoversion](../../includes/ssdenoversion-md.md)] or registering [!INCLUDE [ssDE](../../includes/ssde-md.md)] in **Registered Servers**. **Connect** and **Options** only appear in this dialog box when connecting to an instance of the [!INCLUDE [ssDE](../../includes/ssde-md.md)]. **Test** and **Save** only appear in this dialog box when registering [!INCLUDE [ssDE](../../includes/ssde-md.md)]. Access this tab by selecting **Options >>** on the login tab.
 
-Use this tab to enter advanced parameters when connecting to an instance of [!INCLUDE[msCoName](../../includes/msconame-md.md)] [!INCLUDE[ssDEnoversion](../../includes/ssdenoversion-md.md)] or registering [!INCLUDE[ssDE](../../includes/ssde-md.md)] in **Registered Servers**. **Connect** and **Options** only appear in this dialog box when connecting to an instance of the [!INCLUDE[ssDE](../../includes/ssde-md.md)]. **Test** and **Save** only appear in this dialog box when registering [!INCLUDE[ssDE](../../includes/ssde-md.md)]. Access this tab by selecting **Options >>** on the login tab.
-  
 [!INCLUDE [entra-id-hard-coded](../../includes/entra-id-hard-coded.md)]
 
 ## Additional parameters
 
 The Additional Connection Parameters dialog box allows you to enter connection properties that don't have an equivalent option exposed in any other tab, usually to support an advanced scenario. The parameters entered in the Additional Connection Parameters dialog box are added to any options selected or altered in the **Login** and **Connection Properties** dialogs.
 
-> [!IMPORTANT]
-> Any parameters entered in this dialog box override selections made on the **Login** and **Connection Properties** dialogs.  Parameters are transmitted as clear text; don't include sensitive information in the dialog.
+> [!IMPORTANT]  
+> Any parameters entered in this dialog box override selections made on the **Login** and **Connection Properties** dialogs. Parameters are transmitted as clear text. Don't include sensitive information in the dialog.
 
-## Adding a parameter
+## Add a parameter
 
-Parameters are entered with the property name and followed by the value for the property. For scenarios that include Availability Groups, to connect to a secondary replica that supports read-intent so you can execute read-only queries, enter ```ApplicationIntent=ReadOnly```. If you connect to an Availability Group with replicas in multiple subnets and specify the Listener in the **Server name** dialog on the **Login** page, enter ```MultiSubnetFailover=True``` for faster detection of, and connection to, the (currently) active server.
+Parameters are entered with the property name and followed by the value for the property. For scenarios that include Availability Groups, to connect to a secondary replica that supports read-intent so you can execute read-only queries, enter `ApplicationIntent=ReadOnly`. If you connect to an Availability Group with replicas in multiple subnets and specify the Listener in the **Server name** dialog on the **Login** page, enter `MultiSubnetFailover=True` for faster detection of, and connection to, the (currently) active server.
 
-When entering multiple parameters, separate them with a semicolon. For example, ```ApplicationIntent=ReadOnly; InitialCatalog=WideWorldImporters```.
+When entering multiple parameters, separate them with a semicolon. For example, `ApplicationIntent=ReadOnly; InitialCatalog=WideWorldImporters`.
 
 For a complete list of parameters, see [Properties](/../../dotnet/api/microsoft.data.sqlclient.sqlconnectionstringbuilder?view=sqlclient-dotnet-standard-3.1&preserve-view=true#properties).
 
-> [!CAUTION]
-> Additional parameters are not typically required and exist to support advanced scenarios. If you determine that a connection is not working as expected, check the **Additional Connection Parameters** dialog to see if any unexpected options exist.  It is not uncommon that users enter options for testing purposes and then forget to remove them.
+> [!CAUTION]  
+> Additional parameters aren't typically required and exist to support advanced scenarios. If you determine that a connection isn't working as expected, check the **Additional Connection Parameters** dialog to see if any unexpected options exist. It isn't uncommon that users enter options for testing purposes and then forget to remove them.
 
-## See also  
+## Related content
 
-[Connect to Server (Login Page) Database Engine](connect-to-server-login-page-database-engine.md)
-[Connect to Server (Connection Properties Page) Database Engine](connect-to-server-connection-properties-page-database-engine.md)
+- [Connect to Server (Login page) - Database Engine](connect-to-server-login-page-database-engine.md)
+- [Connect to Server (Connection Properties page) - Database Engine](connect-to-server-connection-properties-page-database-engine.md)

docs/ssms/f1-help/connect-to-server-always-encrypted-page-database-engine.md

@@ -1,55 +1,57 @@
 ---
 title: Connect to Server (Always Encrypted Page) Database Engine
-description: "Connect to Server (Always Encrypted  Page) Database Engine"
+description: Connect to Server (Always Encrypted  Page) Database Engine.
 author: erinstellato-ms
 ms.author: erinstellato
 ms.reviewer: maghan, randolphwest
-ms.date: 11/03/2023
+ms.date: 11/16/2023
 ms.service: sql
 ms.subservice: ssms
 ms.topic: ui-reference
 f1_keywords:
   - "sql13.swb.connecttosqlserver.alwaysencrypted.f1"
 ---
 
-# Connect to Server (Always Encrypted Page) Database Engine
+# Connect to Server (Always Encrypted page) - Database Engine
 
 [!INCLUDE [SQL Server Azure SQL Database Azure SQL Managed Instance](../../includes/applies-to-version/sql-asdb-asdbmi.md)]
 
-Use this tab to view or specify Always Encrypted column encryption options when connecting to Azure SQL Database, Azure SQL Managed Instance, or SQL Server. Use this tab to view or specify Always Encrypted secure enclave options when connecting to Azure SQL Database or SQL Server.   Access this tab by selecting **Options >>** on the login tab.
+Use this tab to view or specify Always Encrypted column encryption options when connecting to Azure SQL Database, Azure SQL Managed Instance, or SQL Server. Use this tab to view or specify Always Encrypted secure enclave options when connecting to Azure SQL Database or SQL Server. Access this tab by selecting **Options >>** on the login tab.
+
+#### Enable Always Encrypted (column encryption)
 
-**Enable Always Encrypted (column encryption)**  
 By default, Always Encrypted is disabled for a database connection. Enabling Always Encrypted for a database connection instructs the .NET Framework Data Provider for SQL Server, used by SQL Server Management Studio (SSMS), to attempt to transparently:
 
 - Decrypt any values that are retrieved from encrypted columns and returned in query results.
 - Encrypt the values of the parameterized Transact-SQL variables that target encrypted database columns.
 
-SSMS uses the .NET Framework Data Provider for SQL Server. If you don't enable Always Encrypted for a connection, the .NET Framework Data Provider doesn't try to encrypt query parameters or decrypt results.  For more information, see [Query columns using Always Encrypted with SSMS](../../relational-databases/security/encryption/always-encrypted-query-columns-ssms.md).
+SSMS uses the .NET Framework Data Provider for SQL Server. If you don't enable Always Encrypted for a connection, the .NET Framework Data Provider doesn't try to encrypt query parameters or decrypt results. For more information, see [Query columns using Always Encrypted with SQL Server Management Studio](../../relational-databases/security/encryption/always-encrypted-query-columns-ssms.md).
+
+#### Enable secure enclaves
 
-**Enable secure enclaves**
 Enable this option when connecting to a database configured to use Always Encrypted with secure enclaves. For more information, see [Getting started using Always Encrypted with secure enclaves](/azure/azure-sql/database/always-encrypted-enclaves-getting-started).
 
 ## Enclave attestation
 
-**Protocol:**
+#### Protocol
+
 Select the attestation protocol to use when connecting to a database configured to use Always Encrypted with secure enclaves. The protocol value determines:
 
 - If the client app uses attestation, and, if so,
-- It specifies the type of the attestation service it uses.  
+- It specifies the type of the attestation service it uses.
 
 Available options are **None**,**Host Guardian Service**, and **Microsoft Azure Attestation**. For more information, see [Always Encrypted with secure enclaves](../../relational-databases/security/encryption/always-encrypted-enclaves.md#secure-enclave-attestation).
 
-**URL:**  
-Enter the configured URL for the selected attestation protocol.  The URL is specific to the type of enclave and SQL in use.
+#### URL
+
+Enter the configured URL for the selected attestation protocol. The URL is specific to the type of enclave and SQL in use.
 
 - [Azure SQL Database with SGX enclaves](/azure/azure-sql/database/always-encrypted-enclaves-configure-attestation#determine-the-attestation-url-for-your-attestation-policy)
 - [SQL Server](../../relational-databases/security/encryption/always-encrypted-enclaves-host-guardian-service-deploy.md)
 
-Attestation isn't supported for Azure SQL Database with VBS enclaves. The URL option is disabled if **None** is selected for **Protocol:**.
-
-## Next Steps
+Attestation isn't supported for Azure SQL Database with VBS enclaves. The URL option is disabled if **None** is selected for **Protocol**.
 
-For more examples on how to use Always Encrypted features with SSMS, review the following tutorials:
+## Related content
 
 - [Tutorial: Getting started using Always Encrypted with secure enclaves in SQL Server with attestation using HGS](../../relational-databases/security/tutorial-getting-started-with-always-encrypted-enclaves-hgs.md)
 - [Tutorial: Getting started using Always Encrypted with Intel SGX enclaves in Azure SQL Database](/azure/azure-sql/database/always-encrypted-enclaves-getting-started-sgx)