Updates to ADS connection docs and SSMS rel notes

Author: erinstellato-ms

docs/azure-data-studio/azure-connectivity.md

@@ -4,7 +4,7 @@ description: Explains the Azure connection options available in Azure Data Studi
 author: erinstellato-ms
 ms.author: erinstellato
 ms.reviewer: maghan, randolphwest
-ms.date: 03/22/2023
+ms.date: 06/06/2023
 ms.service: azure-data-studio
 ms.topic: "overview"
 ---
@@ -76,9 +76,6 @@ Azure Data Studio supports Azure Active Directory (Azure AD) authentication with
 
 :::image type="content" source="media/azure-connectivity/national-clouds.png" alt-text="Screenshot of Azure authentication National Clouds.":::
 
-> [!NOTE]  
-> Only one National Cloud can be enabled in a session.
-
 ## Azure resource configuration
 
 These settings apply filters on Azure resources and tenants.
@@ -184,13 +181,35 @@ If the user application is running in an environment behind a proxy, user authen
 
 As a cross-platform application, ADS proxy resolution fetches the proxy from either setting within the application, or through environment variables. The aim is to avoid interaction with system settings, which can vary significantly on different operating systems.
 
+### Issue: Azure Core extension is disabled
+
+Azure Core extension is `@builtin` extension in Azure Data Studio, please ensure it's not disabled or uninstalled accidentally. This extension is required to be able to authenticate Azure accounts and connect to resources with Azure MFA authentication.
+
+:::image type="content" source="media/azure-connectivity/azure-connectivity-azure-core-extension.png" alt-text="Screenshot of built-in Azure Core extension.":::
+
+### Issue: System CA certificates are expired
+
+Azure Data Studio's default behavior includes validating system's root CA certificates when making REST API calls using HTTPS Protocol. This is controlled by the below setting that is enabled by default:
+
+:::image type="content" source="media/azure-connectivity/azure-connectivity-system-certificates.png" alt-text="Screenshot of system certificates setting.":::
+
+```
+"http.systemCertificates": true
+```
+
+If a system's Root CA certificate is expired, authentication requests to Azure Active Directory will fail and an error like below would be captured in 'Azure Account' logs:
+
+`error: certificate is expired`
+
+To mitigate this error, you should remove any expired Root CA Certificates or disable the setting to not validate system certificates.
+
 ## Capture logs for Azure authentication
 
 Azure Data Studio captures Error events for Azure account activity by default. To enable more detailed traces, users can modify these settings:
 
 ### Azure: Logging level
 
-This setting configures the logging level for information from Azure core that can be captured in Azure Data Studio. Change it to *Verbose* or *All* to capture detailed logs that can be useful to diagnose authentication failures. For more information, see [Debug Trace Logging](https://github.com/microsoft/azuredatastudio/wiki/Debug-Trace-Logging) to learn how to capture logging information.
+This setting configures the logging level for information from Azure core that can be captured in Azure Data Studio. Change it to *Verbose* or *All* to capture detailed logs that can be useful to diagnose authentication failures. For more information, see [Azure Data Studio logs and location](troubleshooting.md#azure-data-studio-logs-and-location) to learn how to capture logging information.
 
 `Settings.json`
 
@@ -240,4 +259,4 @@ Execute this command from **Command Palette (Ctrl/CMD + Shift + P)** to clear ac
 
 Execute this command from **Command Palette (Ctrl/CMD + Shift + P)** to remove all linked Azure accounts from Azure Data Studio:
 
-**Clear all saved accounts (clearSavedAccounts)**
+**Clear all saved accounts (clearSavedAccounts)**

docs/azure-data-studio/media/azure-connectivity/azure-connectivity-azure-core-extension.png

@@ -4,7 +4,7 @@ description: "Learn how to get logs and troubleshoot Azure Data Studio, which is
 author: dzsquared
 ms.author: drskwier
 ms.reviewer: hanqin, maghan
-ms.date: 11/24/2020
+ms.date: 06/06/2023
 ms.service: azure-data-studio
 ms.topic: conceptual
 ms.custom: updatefrequency5
@@ -24,41 +24,42 @@ File a single issue per problem and feature request.
 * Don't enumerate multiple bugs or feature requests in the same issue.
 * Don't add your issue as a comment to an existing issue unless it's for the identical input. Many issues look similar, but have different causes.
 
-The more information you can provide, the more likely someone will be successful reproducing the issue and finding a fix. 
+The more information you can provide, the more likely someone will be successful reproducing the issue and finding a fix.
 
 Include the following information with each issue:
 
 * Version of Azure Data Studio
 * Reproducible steps (1... 2... 3...) and what you expected versus what you actually saw. 
 * Images, animations, or a link to a video. Images and animations illustrate repro-steps but don't replace them.
-* A code snippet that demonstrates the issue or a link to a code repository we can easily pull down onto our machine to recreate the issue. 
+* A code snippet that demonstrates the issue or a link to a code repository we can easily pull down onto our machine to recreate the issue.
 
 > [!NOTE]
->  Because we need to copy and paste the code snippet, including a code snippet as a media file (i.e. .gif) is not sufficient. 
+>  Because we need to copy and paste the code snippet, including a code snippet as a media file (i.e. .gif) is not sufficient.
 
 * Errors in the Dev Tools Console (Help | Toggle Developer Tools)
 
 Please remember to do the following:
 
-* Search the issue repository to see if there exists a duplicate. 
-* Simplify your code around the issue so we can better isolate the problem. 
+* Search the issue repository to see if the same issue already exists.
+* Simplify your code around the issue so we can better isolate the problem.
 
 Don't feel bad if we can't reproduce the issue and ask for more information!
 
 ## How to set the logging level
 
 ### Azure Data Studio
-Run the `Developer: Set Log Level...` command to select the log level for the current session. This value is NOT persisted over multiple sessions - so if you restart Azure Data Studio it will revert back to the default `Info` level. 
+Run the `Developer: Set Log Level...` command to select the log level for the current session. This value is NOT persisted over multiple sessions - so if you restart Azure Data Studio it will revert back to the default `Info` level.
 
-If you want to enable debug logging for startup then set the log level to `Debug` and run the `Developer: Reload Window` command
+If you want to enable debug logging for startup then set the log level to `Debug` and run the `Developer: Reload Window` command.
 
 ### MSSQL (Built-In Extension)
 
 If the `Mssql: Log Debug Info` user setting is set to true, then debug log info will be sent to the `MSSQL` output channel.
 
 The `Mssql: Tracing Level` user setting is used to control the verbosity of the logging.
 
-## Debug log location
+## Azure Data Studio logs and location
+
 From Azure Data Studio, run the `Developer: Open Logs Folder` command to open the path to the logs. There's many different types of log files that write there, a few of the commonly used ones are:
 
 1. `renderer#.log` (for example, renderer1.log) - this file is the log file for the main process.
@@ -68,7 +69,7 @@ From Azure Data Studio, run the `Developer: Open Logs Folder` command to open th
    * sqltools.log is the log for SQL Tools Service
 1. `exthost#/output_logging_#######` - these folders contain the messages displayed in the `Output` panel in Azure Data Studio. Each file is named `#-<Channel Name>` so for example the `Notebooks` output channel may output to a file named `3-Notebooks.log`.
 
-If you are asked to provide logs, zip up the entire folder to ensure that the correct logs are included. 
+If you are asked to provide logs, zip up the entire folder to ensure that the correct logs are included.
 
 ## Next Steps
 - [Report an issue](https://github.com/Microsoft/azuredatastudio/issues)

docs/azure-data-studio/media/azure-connectivity/azure-connectivity-system-certificates.png

@@ -4,7 +4,7 @@ description: Release notes for SQL Server Management Studio (SSMS).
 author: erinstellato-ms
 ms.author: erinstellato
 ms.reviewer: maghan
-ms.date: 06/02/2023
+ms.date: 06/06/2023
 ms.service: sql
 ms.subservice: ssms
 ms.topic: conceptual
@@ -38,7 +38,7 @@ SSMS 19.1 is the latest general availability (GA) release of SSMS. If you need a
 | Azure Data Studio installation integration | The installation of SSMS installs Azure Data Studio 1.44. |
 | Always Encrypted | Added support for secure enclaves and in-place encryption in the Always Encrypted Wizard. See [Configure column encryption using Always Encrypted Wizard](/sql/relational-databases/security/encryption/always-encrypted-wizard). |
 | Azure SQL Managed Instance | Introduced visibility to the status of the Distributed Transaction Coordinator (DTC) service for Azure SQL Managed Instance. Object Explorer can be used to determine if DTC is enabled on the Azure SQL Managed Instance (within the Management node). See [Distributed Transaction Coordinator (DTC) for Azure SQL Managed Instance](/azure/azure-sql/managed-instance/distributed-transaction-coordinator-dtc). |
-| Backup/Restore | Added capability to restore backup files from Amazon S3 storage to SQL Server 2022 and Azure SQL Managed Instance. |
+| Backup/Restore | Added capability to restore backup files from S3-compatible storage to SQL Server 2022 and Azure SQL Managed Instance. |
 | General SSMS | Updated File Version for ssms.exe to align with product version. |
 | General SSMS | Removed deprecated hardware from the list of available service-level objects. |
 | General SSMS | Changed the system browser setting, within **Tools > Options > Azure Services**, to default to True. The external browser will be used, instead of the legacy embedded browser. |