adding connection section

dzsquared · dzsquared · commit cd989ddc857b · 2022-11-09T09:09:22.000-08:00
diff --git a/docs/tools/sqlpackage/troubleshooting-issues-and-performance-with-sqlpackage.md b/docs/tools/sqlpackage/troubleshooting-issues-and-performance-with-sqlpackage.md
@@ -75,6 +75,21 @@ sqlpackage.exe /at:$AccessToken
 sqlpackage.exe /at:$($AccessToken_Object.Token) 
 ```
 
+### Connection
+
+If SqlPackage is failing to connect, the server may not have encryption enabled or the configured certificate may not be issued from a trusted certificate authority (such as a self-signed certificate).  You can change the SqlPackage command to either connect without encryption or to trust the server certificate.  The [best practice](../../relational-databases/security/securing-sql-server.md) is to ensure that a trusted encrypted connection to the server can be established.
+- Connect without encryption: /SourceEncryptConnection=False or /TargetEncryptConnection=False
+- Trust server certificate: /SourceTrustServerCertificate=True or /TargetTrustServerCertificate=True
+
+You may see any of the following warning messages when connecting to a SQL instance, indicating that command line parameters may require changes to connect to the server:
+
+```bash
+The settings for connection encryption or server certificate trust may lead to connection failure if the server is not properly configured.
+The connection string provided contains encryption settings which may lead to connection failure if the server is not properly configured.
+```
+
+More information about the connection security changes in SqlPackage is available in this [blog post](https://aka.ms/dacfx-connection).
+
 ## Diagnostics
 Logs are essential to troubleshooting. Capture the diagnostic logs to a file with the `/DiagnosticsFile:<filename>` parameter.
 
