diff --git a/openmetadata-docs/content/openmetadata/connectors/database/mssql/index.md b/openmetadata-docs/content/openmetadata/connectors/database/mssql/index.md
index ddf3e812100..8e68a00e665 100644
--- a/openmetadata-docs/content/openmetadata/connectors/database/mssql/index.md
+++ b/openmetadata-docs/content/openmetadata/connectors/database/mssql/index.md
@@ -8,6 +8,7 @@ slug: /openmetadata/connectors/database/mssql
 In this section, we provide guides and references to use the MSSQL connector.
 
 Configure and schedule MSSQL metadata and profiler workflows from the OpenMetadata UI:
+- [Remote-Connection]() 
 - [Requirements](#requirements)
 - [Metadata Ingestion](#metadata-ingestion)
 - [Query Usage and Lineage Ingestion](#query-usage-and-lineage-ingestion)
@@ -43,6 +44,42 @@ To deploy OpenMetadata, check the <a href="/deployment">Deployment</a> guides.
 To run the Ingestion via the UI you'll need to use the OpenMetadata Ingestion Container, which comes shipped with
 custom Airflow plugins to handle the workflow deployment.
 
+### For Remote Connection
+
+#### 1. SQL Server running
+
+Make sure the SQL server that you are trying to connect is in running state.
+
+#### 2. Allow remote connection on MSSMS(Microsoft SQL Server Management Studio)
+
+This step allow the sql server to accept remote connection request.
+
+<Image
+src="/images/openmetadata/connectors/mssql/remote-connection.png"
+alt="Remote Connection"
+caption="Rm"
+/>
+
+#### 3. Configure Windows Firewall 
+
+If you are using SQL server on windows, you must configure the firewall on the computer running SQL Server to allow access.
+
+- Step 1: On the Start menu, select Run, type WF.msc, and then select OK.
+
+Step 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.
+
+Step 3: In the Rule Type dialog box, select Port, and then select Next.
+
+Step 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 Database Engine, such as 1433 for the default instance. Select Next.
+
+Step 5: In the Action dialog box, select Allow the connection, and then select Next.
+
+Step 6: In the Profile dialog box, select any profiles that describe the computer connection environment when you want to connect to the Database Engine, and then select Next.
+
+Step 7: In the Name dialog box, type a name and description for this rule, and then select Finish.
+
+For details step please refer the this [link](https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/configure-a-windows-firewall-for-database-engine-access?view=sql-server-ver15).
+
 ## Metadata Ingestion
 
 ### 1. Visit the Services Page
diff --git a/openmetadata-docs/images/openmetadata/connectors/mssql/remote-connection.png b/openmetadata-docs/images/openmetadata/connectors/mssql/remote-connection.png
new file mode 100644
index 00000000000..433456a7b57
Binary files /dev/null and b/openmetadata-docs/images/openmetadata/connectors/mssql/remote-connection.png differ