Merge pull request #129996 from jdmartinez36/validationworkingbranch2

Court72 · web-flow · commit 387f9301ca05 · 2020-09-22T09:02:08.000-07:00
Duplicate alt text validation edits US1760863
diff --git a/articles/automation/learn/automation-tutorial-runbook-textual.md b/articles/automation/learn/automation-tutorial-runbook-textual.md
@@ -104,17 +104,17 @@ The runbook that you've created is still in Draft mode. You must publish it befo
 
 6. Note that the job status is shown in **Job Summary**. This status matches the statuses that you saw when testing the runbook.
 
-   ![Job Summary](../media/automation-tutorial-runbook-textual/job-pane-status-blade-jobsummary.png)
+   :::image type="content" source="../media/automation-tutorial-runbook-textual/job-pane-status-blade-jobsummary.png" alt-text="Screenshot of the runbook Job pane showing the Job Summary section highlighted.":::
 
 7. Once the runbook status shows Completed, click **Output**. The Output page is opened, where you can see your `Hello World` message.
 
-   ![Job Summary](../media/automation-tutorial-runbook-textual/job-pane-status-blade-outputtile.png)
+   :::image type="content" source="../media/automation-tutorial-runbook-textual/job-pane-status-blade-outputtile.png" alt-text="Screenshot of the runbook Job pane showing the Output button highlighted.":::
 
 8. Close the Output page.
 
 9. Click **All Logs** to open the Streams pane for the runbook job. You should only see `Hello World` in the output stream. Note that the Streams pane can show other streams for a runbook job, such as verbose and error streams, if the runbook writes to them.
 
-   ![Job Summary](../media/automation-tutorial-runbook-textual/job-pane-status-blade-alllogstile.png)
+   :::image type="content" source="../media/automation-tutorial-runbook-textual/job-pane-status-blade-alllogstile.png" alt-text="Screenshot of the runbook Job pane showing the All Logs button highlighted.":::
 
 10. Close the Streams pane and the Job pane to return to the MyFirstRunbook page.
 
diff --git a/articles/automation/manage-runbooks.md b/articles/automation/manage-runbooks.md
@@ -287,15 +287,15 @@ The summary displays a count and graphical representation of the job status for
 
 Clicking the tile presents the Jobs page, which includes a summarized list of all jobs executed. This page shows the status, runbook name, start time, and completion time for each job.
 
-![Automation account Jobs page](./media/manage-runbooks/automation-account-jobs-status-blade.png)
+:::image type="content" source="./media/manage-runbooks/automation-account-jobs-status-blade.png" alt-text="Screenshot of the Jobs page.":::
 
 You can filter the list of jobs by selecting **Filter jobs**. Filter on a specific runbook, job status, or a choice from the dropdown list, and provide the time range for the search.
 
 ![Filter job status](./media/manage-runbooks/automation-account-jobs-filter.png)
 
 Alternatively, you can view job summary details for a specific runbook by selecting that runbook from the Runbooks page in your Automation account and then selecting **Jobs**. This action presents the Jobs page. From here, you can click a job record to view its details and output.
 
-![Automation account Jobs page](./media/manage-runbooks/automation-runbook-job-summary-blade.png)
+:::image type="content" source="./media/manage-runbooks/automation-runbook-job-summary-blade.png" alt-text="Screenshot of the Jobs page with the Errors button highlighted.":::
 
 ### Retrieve job statuses using PowerShell
 
diff --git a/articles/automation/migrate-oms-update-deployments.md b/articles/automation/migrate-oms-update-deployments.md
@@ -27,7 +27,7 @@ The Operations Management Suite (OMS) portal is being [deprecated](../azure-moni
 
 3. In your Automation account, click **Update Management**.
 
-    ![Update Management](media/migrate-oms-update-deployments/azure-automation.png)
+    :::image type="content" source="media/migrate-oms-update-deployments/azure-automation.png" alt-text="Screenshot of the Update management page.":::
 
 4. In the Azure portal, select **Automation Accounts** under **All services**. 
 
@@ -37,7 +37,7 @@ The Operations Management Suite (OMS) portal is being [deprecated](../azure-moni
 
 All update deployments created in the OMS portal have a [saved search](../azure-monitor/platform/computer-groups.md) also known as a computer group, with the same name as the update deployment that exists. The saved search contains the list of machines that were scheduled in the update deployment.
 
-![Update Management](media/migrate-oms-update-deployments/oms-deployment.png)
+:::image type="content" source="media/migrate-oms-update-deployments/oms-deployment.png" alt-text="Screenshot of the Update Deployments page with the Name and Servers fields highlighted.":::
 
 To use this existing saved search, follow these steps:
 
diff --git a/articles/automation/python-packages.md b/articles/automation/python-packages.md
@@ -15,15 +15,15 @@ Azure Automation allows you to run Python 2 runbooks on Azure and on Linux Hybri
 
 In your Automation account, select **Python 2 packages** under **Shared Resources**. Click **+ Add a Python 2 package**.
 
-![Add Python package](media/python-packages/add-python-package.png)
+:::image type="content" source="media/python-packages/add-python-package.png" alt-text="Screenshot of the Python 2 packages page shows Python 2 packages in the left menu and Add a Python 2 package highlighted.":::
 
 On the Add Python 2 Package page, select a local package to upload. The package can be a **.whl** or **.tar.gz** file. When the package is selected, click **OK** to upload it.
 
-![Add Python package](media/python-packages/upload-package.png)
+:::image type="content" source="media/python-packages/upload-package.png" alt-text="Screenshot shows the Add Python 2 Package page with an uploaded tar.gz file selected.":::
 
 Once a package has been imported, it's listed on the Python 2 packages page in your Automation account. If you need to remove a package, select the package and click **Delete**.
 
-![Package list](media/python-packages/package-list.png)
+:::image type="content" source="media/python-packages/package-list.png" alt-text="Screenshot shows the Python 2 packages page after a package has been imported.":::
 
 ## Import packages with dependencies
 
@@ -48,7 +48,7 @@ Once the packages are downloaded, you can import them into your automation accou
 * -a \<automationAccount\>
 * -m \<modulePackage\>
 
-![Package list](media/python-packages/import-python-runbook.png)
+:::image type="content" source="media/python-packages/import-python-runbook.png" alt-text="Screenshot shows the Overview page for  import_py2package_from_pypi with the Start Runbook pane on the right side.":::
 
 The runbook allows you to specify what package to download. For example, use of the `Azure` parameter downloads all Azure modules and all dependencies (about 105).
 
diff --git a/articles/automation/update-management/update-mgmt-configure-alerts.md b/articles/automation/update-management/update-mgmt-configure-alerts.md
@@ -51,7 +51,7 @@ Follow the steps below to set up alerts to let you know the status of an update
 
 9. Set the **Severity** field to **Informational(Sev 2)** for a successful run or **Informational(Sev 1)** for a failed run.
 
-    ![Configure signal logic](./media/update-mgmt-manage-updates-for-vm/define-alert-details.png)
+    ![Screenshot shows the Define alert details section with Alert rule name, Description, and Severity fields highlighted.](./media/update-mgmt-manage-updates-for-vm/define-alert-details.png)
 
 10. Select **Yes** to enable the alert rule.
 
diff --git a/articles/automation/update-management/update-mgmt-groups.md b/articles/automation/update-management/update-mgmt-groups.md
@@ -40,7 +40,7 @@ To preview the results of your dynamic group query, click **Preview**. The previ
 
 A dynamic group for non-Azure machines uses saved searches, also called computer groups. To learn how to create a saved search, see [Creating a computer group](../../azure-monitor/platform/computer-groups.md#creating-a-computer-group). Once your saved search is created, you can select it from the list of saved searches in **Update management** in the Azure portal. Click **Preview** to preview the computers in the saved search.
 
-![Select groups](./media/update-mgmt-groups/select-groups-2.png)
+![Screenshot shows the Select groups page for Non-Azure (Preview) and the Preview pane on the right side.](./media/update-mgmt-groups/select-groups-2.png)
 
 ## Next steps
 
diff --git a/articles/azure-functions/functions-create-scheduled-function.md b/articles/azure-functions/functions-create-scheduled-function.md
@@ -39,7 +39,7 @@ Your new function app is ready to use. Next, you'll create a function in the new
 
 1. Configure the new trigger with the settings as specified in the table below the image, and then select **Create Function**.
 
-    :::image type="content" source="./media/functions-create-scheduled-function/function-configure-timer-trigger.png" alt-text="Select the timer trigger in the Azure portal." border="true":::
+    :::image type="content" source="./media/functions-create-scheduled-function/function-configure-timer-trigger.png" alt-text="Screenshot shows the New Function page with the Timer Trigger template selected." border="true":::
     
     | Setting | Suggested value | Description |
     |---|---|---|
diff --git a/articles/azure-functions/functions-create-storage-queue-triggered-function.md b/articles/azure-functions/functions-create-storage-queue-triggered-function.md
@@ -84,7 +84,7 @@ Now that you have a storage queue, you can test the function by adding a message
 
 1. Select **Add message**, and type "Hello World!" in **Message text**. Select **OK**.
 
-    :::image type="content" source="./media/functions-create-storage-queue-triggered-function/functions-storage-queue-test.png" alt-text="Go to your myqueue-items queue in the Azure portal." border="true":::
+    :::image type="content" source="./media/functions-create-storage-queue-triggered-function/functions-storage-queue-test.png" alt-text="Screenshot shows the Add message button selected and the Message text field highlighted." border="true":::
 
 1. Wait for a few seconds, then go back to your function logs and verify that the new message has been read from the queue.
 
diff --git a/articles/azure-functions/functions-integrate-storage-queue-output-binding.md b/articles/azure-functions/functions-integrate-storage-queue-output-binding.md
@@ -107,7 +107,7 @@ A new queue named **outqueue** is created in your Storage account by the Functio
 
 1. Under **Application settings**, select **AzureWebJobsStorage**.
 
-    :::image type="content" source="./media/functions-integrate-storage-queue-output-binding/function-find-storage-account.png" alt-text="Locate the storage account connected to AzureWebJobsStorage." border="true":::
+    :::image type="content" source="./media/functions-integrate-storage-queue-output-binding/function-find-storage-account.png" alt-text="Screenshot shows the Configuration page with AzureWebJobsStorage selected." border="true":::
 
 1. Locate and make note of the account name.
 
diff --git a/articles/azure-functions/functions-integrate-store-unstructured-data-cosmosdb.md b/articles/azure-functions/functions-integrate-store-unstructured-data-cosmosdb.md
@@ -138,7 +138,7 @@ This code sample reads the HTTP Request query strings and assigns them to fields
 
 1. Select **Run** and verify that a 200 status is returned.
 
-    :::image type="content" source="./media/functions-integrate-store-unstructured-data-cosmosdb/functions-test-function-output.png" alt-text="Test the function." border="true":::
+    :::image type="content" source="./media/functions-integrate-store-unstructured-data-cosmosdb/functions-test-function-output.png" alt-text="Screenshot shows the HTTP response code 200 status highlighted after selecting Run." border="true":::
 
 
 1. In the Azure portal, search for and select **Azure Cosmos DB**.
diff --git a/articles/azure-government/documentation-government-get-started-connect-with-portal.md b/articles/azure-government/documentation-government-get-started-connect-with-portal.md
@@ -44,7 +44,7 @@ You can take a look at Azure Government regions and their health status by click
 
 Currently, you can choose from 6 available government-only datacenter regions.
 
-![Azure Government Portal](./media/connect-with-portal/connect-with-portal.png)
+![Screenshot shows the Service Health page for Azure Government with the Region drop-down menu open.](./media/connect-with-portal/connect-with-portal.png)
 
 ## Next steps
 
diff --git a/articles/azure-government/documentation-government-manage-marketplace.md b/articles/azure-government/documentation-government-manage-marketplace.md
@@ -44,22 +44,22 @@ If your subscription is under an Enterprise Agreement (EA), the Azure Government
 
 1. Click on **+New**.
 
-   ![alt text](./media/government-manage-marketplace-launch.png)  
+   ![Screenshot shows Azure Government portal New page with Compute selected.](./media/government-manage-marketplace-launch.png)  
 
 1. Browse through different products to find the right one. The marketplace publisher provides a list of certifications as part of the product description to help you make the right choice. 
 
-   ![alt text](./media/government-manage-marketplace-service.png)
+   ![Screenshot shows marketplace Compute page and recommended apps.](./media/government-manage-marketplace-service.png)
 
 1. Choose an product\image and click **Create**.
 
-   ![alt text](./media/government-manage-marketplace-image.png)
+   ![Screenshot shows selected example Red Hat Enterprise Linux 7.2 description and the Create button.](./media/government-manage-marketplace-image.png)
 
 1. Enter the required parameters for deployment.
 
    > [!NOTE]
    > In the Location dropdown, only Azure Government locations are visible
   
-   ![alt text](./media/government-manage-marketplace-deployment.png)
+   ![Screenshot shows the Basics window with example parameters entered.](./media/government-manage-marketplace-deployment.png)
 
 1. To start the provisioning process, click **Ok**.
 
diff --git a/articles/azure-government/documentation-government-manage-oms.md b/articles/azure-government/documentation-government-manage-oms.md
@@ -50,8 +50,9 @@ Azure Monitor logs can also connect to your storage account and/or existing Syst
 
 Azure Monitor logs also supports collecting logging information from other monitoring services like Chef or Puppet. Furthermore, for Azure deployments, we have VMs with Azure Monitor logs-enabled Azure Resource Manager templates so you can deploy compute and onboard to your Log Analytics workspace at the same time.
 
-![Figure 3: Azure Resource Manager templates for Azure VMs with Azure Monitor VM extension](./media/documentation-government-oms-figure3a.png)
-![Figure 3: Azure Resource Manager templates for Azure VMs with Azure Monitor VM extension](./media/documentation-government-oms-figure3b.png)
+![Screenshot shows Deploy a Ubuntu VM with the OMS extension template.](./media/documentation-government-oms-figure3a.png)
+
+![Azure Resource Manager templates for Azure VMs with Azure Monitor VM extension](./media/documentation-government-oms-figure3b.png)
 <p align="center">Figure 3: Azure Resource Manager templates for Azure VMs with Azure Monitor VM extension</p>
 
 Information about setting up Azure Monitor logs with your existing Operations Manager implementation on-premises can be found in [Connect Operations Manager to Azure Monitor logs](https://docs.microsoft.com/azure/log-analytics/log-analytics-om-agents).
diff --git a/articles/azure-government/documentation-government-plan-identity.md b/articles/azure-government/documentation-government-plan-identity.md
@@ -64,7 +64,7 @@ Supporting IaaS cloud-based applications dependent on NTLM/Kerberos authenticati
 <div></div>
 <div align="center">
 
-![alt text](./media/documentation-government-plan-identity-extending-ad-to-azure-iaas.png "Extending On-Premises Active Directory Footprint to Azure IaaS")
+![Diagram shows a site-to-site VPN connectivity example for Azure IaaS.](./media/documentation-government-plan-identity-extending-ad-to-azure-iaas.png "Extending On-Premises Active Directory Footprint to Azure IaaS")
 
 </div>
 <div></div>
@@ -111,7 +111,7 @@ The following diagram is the simplest of the scenarios to implement.
 <div></div>
 <div align="center">
 
-![alt text](./media/documentation-government-plan-identity-cloud-identities-for-subscription-administration.png "Using Cloud Identities for Multi-Cloud Subscription Administration")
+![Diagram shows a multi-cloud subscription administration option using cloud identities for Office 365 and Microsoft Azure Government.](./media/documentation-government-plan-identity-cloud-identities-for-subscription-administration.png "Using Cloud Identities for Multi-Cloud Subscription Administration")
 
 </div>
 <div></div>
@@ -129,7 +129,7 @@ In this scenario, we include administrator identities through directory synchron
 <div></div>
 <div align="center">
 
-![alt text](./media/documentation-government-plan-identity-hybrid-and-cloud-identities-for-subscription-administration.png "Using Hybrid and Cloud Identities for Multi-Cloud Subscription Administration")
+![Diagram shows a scenario for hybrid and cloud identities for multi-cloud subscription administration using smartcards for access.](./media/documentation-government-plan-identity-hybrid-and-cloud-identities-for-subscription-administration.png "Using Hybrid and Cloud Identities for Multi-Cloud Subscription Administration")
 
 </div>
 <div></div>
@@ -145,7 +145,7 @@ In this scenario, hybrid identities are used to administrator subscriptions in b
 <div></div>
 <div align="center">
 
-![alt text](./media/documentation-government-plan-identity-hybrid-identities-for-subscription-administration.png "Using Hybrid Identities for Multi-Cloud Subscription Administration")
+![Diagram shows a scenario with hybrid identities for multi-cloud subscription administration, requiring different credentials for each cloud service.](./media/documentation-government-plan-identity-hybrid-identities-for-subscription-administration.png "Using Hybrid Identities for Multi-Cloud Subscription Administration")
 
 </div>
 <div></div>
diff --git a/articles/azure-monitor/app/app-insights-overview.md b/articles/azure-monitor/app/app-insights-overview.md
@@ -54,7 +54,7 @@ There are plenty of ways to explore your data. Check out these articles:
 | [**Dashboards**](./overview-dashboard.md)<br/>Mash up data from multiple resources and share with others. Great for multi-component applications, and for continuous display in the team room. |![Dashboards sample](./media/app-insights-overview/dashboard-tn.png) |
 | [**Live Metrics Stream**](./live-stream.md)<br/>When you deploy a new build, watch these near-real-time performance indicators to make sure everything works as expected. |![Live metrics sample](./media/app-insights-overview/live-metrics-tn.png) |
 | [**Analytics**](../log-query/log-query-overview.md)<br/>Answer tough questions about your app's performance and usage by using this powerful query language. |![Analytics sample](./media/app-insights-overview/analytics-tn.png) |
-| [**Visual Studio**](./visual-studio.md)<br/>See performance data in the code. Go to code from stack traces.|![Visual studio](./media/app-insights-overview/visual-studio-tn.png) |
+| [**Visual Studio**](./visual-studio.md)<br/>See performance data in the code. Go to code from stack traces.|![Screenshot shows Exception Details in Visual Studio and an example of going to code from stack traces.](./media/app-insights-overview/visual-studio-tn.png) |
 | [**Snapshot debugger**](./snapshot-debugger.md)<br/>Debug snapshots sampled from live operations, with parameter values.|![Visual studio](./media/app-insights-overview/snapshot.png) |
 | [**Power BI**](./export-power-bi.md)<br/>Integrate usage metrics with other business intelligence.| ![Power BI](./media/app-insights-overview/power-bi.png)|
 | [**REST API**](https://dev.applicationinsights.io/)<br/>Write code to run queries over your metrics and raw data.| ![REST API](./media/app-insights-overview/rest-tn.png) |
diff --git a/articles/azure-monitor/app/app-map.md b/articles/azure-monitor/app/app-map.md
@@ -30,7 +30,7 @@ On clicking "Update map components", the map is refreshed with all components di
 
 If all of the components are roles within a single Application Insights resource, then this discovery step is not required. The initial load for such an application will have all its components.
 
-![Application Map Screenshot](media/app-map/app-map-001.png)
+![Screenshot shows an example of an application map.](media/app-map/app-map-001.png)
 
 One of the key objectives with this experience is to be able to visualize complex topologies with hundreds of components.
 
diff --git a/articles/azure-monitor/app/asp-net-trace-logs.md b/articles/azure-monitor/app/asp-net-trace-logs.md
diff --git a/articles/azure-monitor/app/asp-net.md b/articles/azure-monitor/app/asp-net.md
diff --git a/articles/azure-monitor/app/automate-with-logic-apps.md b/articles/azure-monitor/app/automate-with-logic-apps.md
