Merge pull request #20893 from VanMSFT/vancontenthealth

Update content health

Author: PMEds28

docs/database-engine/configure-windows/configure-a-windows-firewall-for-database-engine-access.md

@@ -1,8 +1,8 @@
 ---
-title: "Configure a Windows Firewall for Database Engine Access | Microsoft Docs"
+title: "Configure a Windows Firewall for Database Engine Access"
 description: Find out how to configure a Windows firewall so that client computers can access an instance of the SQL Server Database Engine through the firewall.
 ms.custom: ""
-ms.date: "03/14/2017"
+ms.date: "12/16/2021"
 ms.prod: sql
 ms.prod_service: high-availability
 ms.reviewer: ""
@@ -36,59 +36,48 @@ ms.author: maghan
 > [!NOTE]  
 >  By default, [!INCLUDE[msCoName](../../includes/msconame-md.md)] Windows enables the Windows Firewall, which closes port 1433 to prevent Internet computers from connecting to a default instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] on your computer. Connections to the default instance using TCP/IP are not possible unless you reopen port 1433. The basic steps to configure the Windows firewall are provided in the following procedures. For more information, see the Windows documentation.  
   
- As an alternative to configuring [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] to listen on a fixed port and opening the port, you can list the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] executable (Sqlservr.exe) as an exception to the blocked programs. Use this method when you want to continue to use dynamic ports. Only one instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] can be accessed in this way.  
+ As an alternative to configuring [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] to listen on a fixed port and opening the port, you can list the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] executable (Sqlservr.exe) as an exception to the blocked programs. Use this method when you want to continue to use dynamic ports. Only one instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] can be accessed in this way.
 
- **In This Topic**  
-  
--   **Before you begin:**  
-  
-     [Security](#Security)  
-  
--   **To configure a Windows Firewall for Database Engine access, using:**  
-  
-     [SQL Server Configuration Manager](#SSMSProcedure)  
-  
-## Before You Begin  
+## Before you begin  
 
 ###  <a name="Security"></a> Security  
  Opening ports in your firewall can leave your server exposed to malicious attacks. Make sure that you understand firewall systems before you open ports. For more information, see [Security Considerations for a SQL Server Installation](../../sql-server/install/security-considerations-for-a-sql-server-installation.md)  
 
-##  <a name="SSMSProcedure"></a> Using SQL Server Configuration Manager  
- Applies to Windows Vista, Windows 7, and Windows Server 2008  
+##  <a name="SSMSProcedure"></a> Using SQL Server Configuration Manager
 
  The following procedures configure the Windows Firewall by using the Windows Firewall with Advanced Security Microsoft Management Console (MMC) snap-in. The Windows Firewall with Advanced Security only configures the current profile. For more information about the Windows Firewall with Advanced Security, see [Configure the Windows Firewall to Allow SQL Server Access](../../sql-server/install/configure-the-windows-firewall-to-allow-sql-server-access.md)  
 
 #### To open a port in the Windows firewall for TCP access  
 
-1.  On the **Start** menu, click **Run**, type **WF.msc**, and then click **OK**.  
+1.  On the **Start** menu, select **Run**, type **WF.msc**, and then select **OK**.  
 
-2.  In the **Windows Firewall with Advanced Security**, in the left pane, right-click **Inbound Rules**, and then click **New Rule** in the action pane.  
+2.  In the **Windows Firewall with Advanced Security**, in the left pane, right-click **Inbound Rules**, and then select **New Rule** in the action pane.  
 
-3.  In the **Rule Type** dialog box, select **Port**, and then click **Next**.  
+3.  In the **Rule Type** dialog box, select **Port**, and then select **Next**.  
 
-4.  In the **Protocol and Ports** dialog box, select **TCP**. Select **Specific local ports**, and then type the port number of the instance of the [!INCLUDE[ssDE](../../includes/ssde-md.md)], such as **1433** for the default instance. Click **Next**.  
+4.  In the **Protocol and Ports** dialog box, select **TCP**. Select **Specific local ports**, and then type the port number of the instance of the [!INCLUDE[ssDE](../../includes/ssde-md.md)], such as **1433** for the default instance. Select **Next**.  
 
-5.  In the **Action** dialog box, select **Allow the connection**, and then click **Next**.  
+5.  In the **Action** dialog box, select **Allow the connection**, and then select **Next**.  
 
-6.  In the **Profile** dialog box, select any profiles that describe the computer connection environment when you want to connect to the [!INCLUDE[ssDE](../../includes/ssde-md.md)], and then click **Next**.  
+6.  In the **Profile** dialog box, select any profiles that describe the computer connection environment when you want to connect to the [!INCLUDE[ssDE](../../includes/ssde-md.md)], and then select **Next**.  
 
-7.  In the **Name** dialog box, type a name and description for this rule, and then click **Finish**.  
+7.  In the **Name** dialog box, type a name and description for this rule, and then select **Finish**.  
 
 #### To open access to SQL Server when using dynamic ports  
 
-1.  On the **Start** menu, click **Run**, type **WF.msc**, and then click **OK**.  
+1.  On the **Start** menu, select **Run**, type **WF.msc**, and then select **OK**.  
 
-2.  In the **Windows Firewall with Advanced Security**, in the left pane, right-click **Inbound Rules**, and then click **New Rule** in the action pane.  
+2.  In the **Windows Firewall with Advanced Security**, in the left pane, right-click **Inbound Rules**, and then select **New Rule** in the action pane.  
 
-3.  In the **Rule Type** dialog box, select **Program**, and then click **Next**.  
+3.  In the **Rule Type** dialog box, select **Program**, and then select **Next**.  
 
-4.  In the **Program** dialog box, select **This program path**. Click **Browse**, and navigate to the instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] that you want to access through the firewall, and then click **Open**. By default, [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] is at **C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Binn\Sqlservr.exe**. Click **Next**.  
+4.  In the **Program** dialog box, select **This program path**. Select **Browse**, and navigate to the instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] that you want to access through the firewall, and then select **Open**. By default, [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] is at **C:\Program Files\Microsoft SQL Server\MSSQLXX.MSSQLSERVER\MSSQL\Binn\Sqlservr.exe**. Select **Next**. The `MSSQLXX` version will be specific to your version of SQL Server.
 
-5.  In the **Action** dialog box, select **Allow the connection**, and then click **Next**.  
+5.  In the **Action** dialog box, select **Allow the connection**, and then select **Next**.  
 
-6.  In the **Profile** dialog box, select any profiles that describe the computer connection environment when you want to connect to the [!INCLUDE[ssDE](../../includes/ssde-md.md)], and then click **Next**.  
+6.  In the **Profile** dialog box, select any profiles that describe the computer connection environment when you want to connect to the [!INCLUDE[ssDE](../../includes/ssde-md.md)], and then select **Next**.  
 
-7.  In the **Name** dialog box, type a name and description for this rule, and then click **Finish**.  
+7.  In the **Name** dialog box, type a name and description for this rule, and then select **Finish**.  
 
 ## See Also  
  [How to: Configure Firewall Settings (Azure SQL Database)](/azure/azure-sql/database/firewall-configure)