Merge pull request #35775 from rwestMSFT/rw-1106-fix-alt-text

[SCOPED] Fix alt-text for SSMS references

Author: rwestMSFT

azure-sql/database/high-cpu-diagnose-troubleshoot.md

@@ -294,7 +294,7 @@ Select **Configure** in the top right of the pane to select a different time per
 
 Select a bar in the chart to drill in and see queries running in a specific time period. The **Top Resource Consuming Queries** pane will open. Alternately, you can open **Top Resource Consuming Queries** from the Query Store node under your database in Object Explorer directly.
 
-:::image type="content" source="media/high-cpu-diagnose-troubleshoot/ssms-query-store-top-resource-consuming-queries.png" alt-text="Screenshot shows the Top Resource Consuming Queries pane for Query Store in S S M S." lightbox="media/high-cpu-diagnose-troubleshoot/ssms-query-store-top-resource-consuming-queries.png":::
+:::image type="content" source="media/high-cpu-diagnose-troubleshoot/ssms-query-store-top-resource-consuming-queries.png" alt-text="Screenshot shows the Top Resource Consuming Queries pane for Query Store in SSMS." lightbox="media/high-cpu-diagnose-troubleshoot/ssms-query-store-top-resource-consuming-queries.png":::
 
 In the default view, the **Top Resource Consuming Queries** pane shows queries by **Duration (ms)**. Duration might sometimes be lower than CPU time: queries using parallelism might use much more CPU time than their overall duration. Duration might also be higher than CPU time if wait times are significant. To see queries by CPU time, select the **Metric** dropdown list at the top left of the pane and select **CPU Time(ms)**.
 

azure-sql/includes/sql-managed-instance/azure-sql-managed-instance-link-check-network.md

@@ -26,7 +26,7 @@ To test network connectivity between SQL Server and SQL Managed Instance in SSMS
 1. Connect to the instance that will be the primary replica in SSMS. 
 1. In **Object Explorer**, expand databases, and right-click the database you intend to link with the secondary. Select **Tasks** > **Azure SQL Managed Instance link** > **Test Connection** to open the **Network Checker** wizard: 
 
-   :::image type="content" source="../../managed-instance/media/managed-instance-link-preparation/test-connection-in-ssms.png" alt-text="Screenshot of object explorer in S S M S, with test connection selected in the database link right-click menu.":::
+   :::image type="content" source="../../managed-instance/media/managed-instance-link-preparation/test-connection-in-ssms.png" alt-text="Screenshot of object explorer in SSMS, with test connection selected in the database link right-click menu.":::
 
 1. Select **Next** on the **Introduction** page of the **Network Checker** wizard.
 1. If all requirements are met on the **Prerequisites** page, select **Next**. Otherwise resolve any unmet prerequisites, and then select **Re-run Validation**. 
@@ -189,7 +189,7 @@ Use SQL Server Agent on SQL Server to run connectivity tests from SQL Server to
 
 1. Run the script and check the results. You should see results such as the following example:
 
-   :::image type="content" source="../../managed-instance/media/managed-instance-link-preparation/test-connectivity-results.png" alt-text="Screenshot that shows the output with the test results in S S M S.":::
+   :::image type="content" source="../../managed-instance/media/managed-instance-link-preparation/test-connectivity-results.png" alt-text="Screenshot that shows the output with the test results in SSMS.":::
 
 1. Verify the results:
 

azure-sql/managed-instance/managed-instance-link-configure-how-to-ssms.md

@@ -123,7 +123,7 @@ After the link is created, your database is replicated to the secondary replica.
 
 On either replica, use **Object Explorer** in SSMS to view the **Synchronized** state of the replicated database. 
 
-:::image type="content" source="./media/managed-instance-link-configure-how-to-ssms/check-replicated-database-on-sql-server.png" alt-text="Screenshot that shows the state of the SQL Server database and distributed availability group in S S M S.":::
+:::image type="content" source="./media/managed-instance-link-configure-how-to-ssms/check-replicated-database-on-sql-server.png" alt-text="Screenshot that shows the state of the SQL Server database and distributed availability group in SSMS.":::
 
 Expand **Always On High Availability** and **Availability Groups** to view the distributed availability group created for each link. 
 

azure-sql/managed-instance/managed-instance-link-preparation.md

@@ -198,7 +198,7 @@ DBCC TRACESTATUS;
 
 Your SQL Server version should be one of the supported versions applied with the appropriate service updates, the Always On availability groups feature should be enabled, and you should have the trace flags `-T1800` and `-T9567` enabled. The following screenshot is an example of the expected outcome for a properly configured SQL Server instance:
 
-:::image type="content" source="media/managed-instance-link-preparation/ssms-results-expected-outcome.png" alt-text="Screenshot that shows the expected outcome in S S M S.":::
+:::image type="content" source="media/managed-instance-link-preparation/ssms-results-expected-outcome.png" alt-text="Screenshot that shows the expected outcome in SSMS.":::
 
 ## Configure network connectivity
 

docs/relational-databases/security/sql-data-discovery-and-classification.md

@@ -42,7 +42,7 @@ The classification includes two metadata attributes:
 
 2. In the SSMS **Object Explorer**, select the database that you would like to classify and choose **Tasks** > **Data Discovery and Classification** > **Classify Data...**.
 
-   ![Screenshot showing the S S M S Object Explorer with Tasks > Data Discovery and Classification > Classify Data... selected.][0]
+   ![Screenshot showing the SSMS Object Explorer with Tasks > Data Discovery and Classification > Classify Data... selected.][0]
 
 3. The classification engine scans your database for columns (based on column names only) containing potentially sensitive data and provides a list of **recommended column classifications**:
 
@@ -68,7 +68,7 @@ The classification includes two metadata attributes:
 
 4. To display the classified columns, select appropriate **schema** and corresponding **table** from the drop-down, then select **Load Columns**.
 
-   :::image type="content" source="media/sql-data-discovery-and-classification/data-classification-load-columns.png" alt-text="screenshot of S S M S data classification loading classified columns.":::
+   :::image type="content" source="media/sql-data-discovery-and-classification/data-classification-load-columns.png" alt-text="screenshot of SSMS data classification loading classified columns.":::
 
 5. You can also **manually classify** columns as an alternative, or in addition, to the recommendation-based classification:
 
@@ -82,7 +82,7 @@ The classification includes two metadata attributes:
 
     - If you want to add classification for all the unclassified columns for a specific table in a single attempt, then select **All Unclassified** in the **Column** drop down of **Add Classification** page.
 
-        :::image type="content" source="media/sql-data-discovery-and-classification/data-classification-all-unclassified-column-selection.png" alt-text="screenshot of S S M S data classification selecting all unclassified columns":::
+        :::image type="content" source="media/sql-data-discovery-and-classification/data-classification-all-unclassified-column-selection.png" alt-text="screenshot of SSMS data classification selecting all unclassified columns":::
 
 6. To complete your classification and persistently label (tag) the database columns with the new classification metadata, select the **Save** button on the top menu of the window.
 
@@ -111,29 +111,29 @@ Power BI datasets or reports that connect to sensitivity-labeled data in support
 1. In SQL Server Management Studio (SSMS), connect to the SQL Server.
 1. In the SSMS Object Explorer, select the database that you would like to classify and select **Tasks** > **Data Discovery and Classification** > **Set Microsoft Information Protection Policy**
 
-   :::image type="content" source="media/sql-data-discovery-and-classification/data-classification-set-microsoft-information-protection-policy.png" alt-text="Screenshot to sset Microsoft Information Protection Policy in S S M S":::
+   :::image type="content" source="media/sql-data-discovery-and-classification/data-classification-set-microsoft-information-protection-policy.png" alt-text="Screenshot to sset Microsoft Information Protection Policy in SSMS":::
 
 1. An authentication window for Microsoft 365 to set the Microsoft Information Protection Policy will show. Select **Sign In** and enter or select a valid user credential to authenticate to your Microsoft 365 tenant.
 
    :::image type="content" source="media/sql-data-discovery-and-classification/data-classification-authenticate-microsoft-information-protection-policy.png" alt-text="Screenshot of authenticating to set Microsoft Information Protection Policy":::
 
 1. If the authentication is successful, you'll see a pop-up window with status as **Success**.
 
-   :::image type="content" source="media/sql-data-discovery-and-classification/successfully-setting-microsoft-information-protection-policy.png" alt-text="Screenshot of successfully setting Microsoft Information Protection Policy in S S M S":::
+   :::image type="content" source="media/sql-data-discovery-and-classification/successfully-setting-microsoft-information-protection-policy.png" alt-text="Screenshot of successfully setting Microsoft Information Protection Policy in SSMS":::
 
 1. Optional - If you want to sign into any of the Microsoft sovereign cloud to authenticate to Microsoft 365, go to SSMS > **Tools** > **Options** > **Azure Services** > **Azure Cloud**, and change the **Name** to the relevant Microsoft sovereign cloud.
 
-   :::image type="content" source="media/sql-data-discovery-and-classification/select-sovereign-cloud.png" alt-text="Screenshot of selecting type of Azure cloud in S S M S":::
+   :::image type="content" source="media/sql-data-discovery-and-classification/select-sovereign-cloud.png" alt-text="Screenshot of selecting type of Azure cloud in SSMS":::
 
 1. In the SSMS **Object Explorer** window, right-click on the database that you would like to classify and choose **Tasks** > **Data Discovery and Classification** > **Classify Data**. You can now add new classification using MIP sensitivity labels defined in your Microsoft 365 tenant and use those labels to classify columns in SQL Server.
 
-   :::image type="content" source="media/sql-data-discovery-and-classification/choose-microsoft-information-protection-policy-sensitivity-labels.png" alt-text="Choosing Microsoft Information Protection Policy sensitivity labels in S S M S":::
+   :::image type="content" source="media/sql-data-discovery-and-classification/choose-microsoft-information-protection-policy-sensitivity-labels.png" alt-text="Choosing Microsoft Information Protection Policy sensitivity labels in SSMS":::
 
    Automatic data discovery and recommendation is disabled while in Microsoft Information Protection Policy mode. It's currently available only in SQL Information Protection Policy mode.
 
 To reset the Information Protection Policy to default or SQL Information Protection, go to the SSMS **Object Explorer**, right-click on the database and choose **Tasks** > **Data Discovery and Classification** > **Reset Information Protection Policy to Default**. This will apply the default or SQL Information Protection policy and you can classify the data using SQL sensitivity labels instead of MIP labels. 
 
-   :::image type="content" source="media/sql-data-discovery-and-classification/reset-information-protection-policy-to-default.png" alt-text="Screenshot of resetting Information Protection Policy in S S M S":::
+   :::image type="content" source="media/sql-data-discovery-and-classification/reset-information-protection-policy-to-default.png" alt-text="Screenshot of resetting Information Protection Policy in SSMS":::
 
 To enable Information Protection Policy from a custom JSON file, go to the SSMS **Object Explorer**, right-click on the database and choose **Tasks** > **Data Discovery and Classification** > **Set Information Protection Policy File**.