Merge pull request #247611 from tfitzmac/0808alttext1

update alt text

Author: prmerger-automator[bot]

articles/azure-resource-manager/management/deployment-models.md

@@ -71,7 +71,7 @@ Only resources created through Resource Manager support tags. You can't apply ta
 
 The following diagram displays compute, network, and storage resources deployed through Resource Manager.
 
-![Resource Manager architecture](./media/deployment-models/arm_arch3.png)
+:::image type="content" source="./media/deployment-models/arm_arch3.png" alt-text="Diagram that shows Resource Manager architecture with SRP, CRP, and NRP.":::
 
 SRP: Storage Resource Provider, CRP: Compute Resource Provider, NRP: Network Resource Provider
 
@@ -86,7 +86,7 @@ Note the following relationships between the resources:
 
 Here are the components and their relationships for classic deployment:
 
-![classic architecture](./media/deployment-models/arm_arch1.png)
+:::image type="content" source="./media/deployment-models/arm_arch1.png" alt-text="Diagram that shows classic architecture for hosting a virtual machine.":::
 
 The classic solution for hosting a virtual machine includes:
 

articles/azure-resource-manager/templates/deploy-cloud-shell.md

@@ -20,7 +20,7 @@ To deploy an external template, provide the URI of the template exactly as you w
 
 1. Open the Cloud Shell prompt.
 
-   :::image type="content" source="./media/deploy-cloud-shell/open-cloud-shell.png" alt-text="Open Cloud Shell":::
+   :::image type="content" source="./media/deploy-cloud-shell/open-cloud-shell.png" alt-text="Screenshot of the button to open Cloud Shell.":::
 
 1. To deploy the template, use the following commands:
 
@@ -56,11 +56,11 @@ To deploy a local template, you must first upload your template to the storage a
 
 1. Select either **PowerShell** or **Bash**.
 
-   :::image type="content" source="./media/deploy-cloud-shell/cloud-shell-bash-powershell.png" alt-text="Select Bash or PowerShell":::
+   :::image type="content" source="./media/deploy-cloud-shell/cloud-shell-bash-powershell.png" alt-text="Screenshot of the option to select Bash or PowerShell in Cloud Shell.":::
 
 1. Select **Upload/Download files**, and then select **Upload**.
 
-   :::image type="content" source="./media/deploy-cloud-shell/cloud-shell-upload.png" alt-text="Upload file":::
+   :::image type="content" source="./media/deploy-cloud-shell/cloud-shell-upload.png" alt-text="Screenshot of the Cloud Shell interface with the Upload file option highlighted.":::
 
 1. Select the ARM template you want to upload, and then select **Open**.
 

articles/azure-resource-manager/templates/deploy-to-azure-button.md

@@ -33,7 +33,7 @@ To add the button to your web page or repository, use the following image:
 
 The image appears as:
 
-![Deploy to Azure button](https://aka.ms/deploytoazurebutton)
+:::image type="content" source="https://aka.ms/deploytoazurebutton" alt-text="Screenshot of Deploy to Azure button.":::
 
 ## Create URL for deploying template
 
@@ -43,7 +43,7 @@ This section shows how to get the URLs for the templates stored in GitHub and Az
 
 To create the URL for your template, start with the raw URL to the template in your GitHub repo. To see the raw URL, select **Raw**.
 
-:::image type="content" source="./media/deploy-to-azure-button/select-raw.png" alt-text="select Raw":::
+:::image type="content" source="./media/deploy-to-azure-button/select-raw.png" alt-text="Screenshot showing how to select Raw in GitHub.":::
 
 The format of the URL is:
 
@@ -136,11 +136,11 @@ For Git with Azure repo, the button is in the format:
 
 To test the full solution, select the following button:
 
-[![Deploy to Azure](https://aka.ms/deploytoazurebutton)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fquickstarts%2Fmicrosoft.storage%2Fstorage-account-create%2Fazuredeploy.json)
+:::image type="content" source="https://aka.ms/deploytoazurebutton" alt-text="Screenshot of Deploy to Azure button with link." link="https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fquickstarts%2Fmicrosoft.storage%2Fstorage-account-create%2Fazuredeploy.json":::
 
 The portal displays a pane that allows you to easily provide parameter values. The parameters are pre-filled with the default values from the template. The camel-cased parameter name, *storageAccountType*, defined in the template is turned into a space-separated string when displayed on the portal.
 
-![Use portal to deploy](./media/deploy-to-azure-button/portal.png)
+:::image type="content" source="./media/deploy-to-azure-button/portal.png" alt-text="Screenshot of Azure portal displaying pane for providing parameter values.":::
 
 ## Next steps
 

articles/azure-resource-manager/templates/linked-templates.md

@@ -442,7 +442,7 @@ You may reference templates using parameters that include HTTP or HTTPS. For exa
 
 If you're linking to a template in GitHub, use the raw URL. The link has the format: `https://raw.githubusercontent.com/Azure/azure-docs-json-samples/master/get-started-with-templates/quickstart-template/azuredeploy.json`. To get the raw link, select **Raw**.
 
-:::image type="content" source="./media/linked-templates/select-raw.png" alt-text="Select raw URL":::
+:::image type="content" source="./media/linked-templates/select-raw.png" alt-text="Screenshot of selecting raw URL in GitHub.":::
 
 [!INCLUDE [Deploy templates in private GitHub repo](../../../includes/resource-manager-private-github-repo-templates.md)]
 
@@ -506,7 +506,7 @@ The `relativePath` property of `Microsoft.Resources/deployments` makes it easier
 
 Assume a folder structure like this:
 
-![resource manager linked template relative path](./media/linked-templates/resource-manager-linked-templates-relative-path.png)
+:::image type="content" source="./media/linked-templates/resource-manager-linked-templates-relative-path.png" alt-text="Diagram showing folder structure for Resource Manager linked template relative path.":::
 
 The following template shows how *mainTemplate.json* deploys *nestedChild.json* illustrated in the preceding image.
 
@@ -707,7 +707,7 @@ To use the public IP address from the preceding template when deploying a load b
 
 Resource Manager processes each template as a separate deployment in the deployment history. A main template with three linked or nested templates appears in the deployment history as:
 
-![Deployment history](./media/linked-templates/deployment-history.png)
+:::image type="content" source="./media/linked-templates/deployment-history.png" alt-text="Screenshot of deployment history in Azure portal.":::
 
 You can use these separate entries in the history to retrieve output values after the deployment. The following template creates a public IP address and outputs the IP address:
 

articles/azure-resource-manager/templates/quickstart-create-template-specs.md

@@ -78,20 +78,20 @@ The template spec is a resource type named `Microsoft.Resources/templateSpecs`.
 1. Sign in to the [Azure portal](https://portal.azure.com).
 1. Search for **template specs**. Select **Template specs** from the available options.
 
-    :::image type="content" source="./media/quickstart-create-template-specs/search-template-spec.png" alt-text="search template specs":::
+    :::image type="content" source="./media/quickstart-create-template-specs/search-template-spec.png" alt-text="Screenshot of search bar with 'template specs' query.":::
 
 1. Select **Import template**.
 
-    :::image type="content" source="./media/quickstart-create-template-specs/import-template.png" alt-text="import template":::
+    :::image type="content" source="./media/quickstart-create-template-specs/import-template.png" alt-text="Screenshot of 'Import template' button in Template specs page.":::
 
 1. Select the folder icon.
 
-    :::image type="content" source="./media/quickstart-create-template-specs/open-folder.png" alt-text="open folder":::
+    :::image type="content" source="./media/quickstart-create-template-specs/open-folder.png" alt-text="Screenshot of folder icon to open file explorer.":::
 
 1. Navigate to the local template you saved and select it. Select **Open**.
 1. Select **Import**.
 
-    :::image type="content" source="./media/quickstart-create-template-specs/select-import.png" alt-text="select import option":::
+    :::image type="content" source="./media/quickstart-create-template-specs/select-import.png" alt-text="Screenshot of 'Import' button after selecting a template file.":::
 
 1. Provide the following values:
 
@@ -304,11 +304,11 @@ To deploy a template spec, use the same deployment commands as you would use to
 
 1. Select the template spec you created.
 
-    :::image type="content" source="./media/quickstart-create-template-specs/select-template-spec.png" alt-text="select template specs":::
+    :::image type="content" source="./media/quickstart-create-template-specs/select-template-spec.png" alt-text="Screenshot of Template specs list with one item selected.":::
 
 1. Select **Deploy**.
 
-    :::image type="content" source="./media/quickstart-create-template-specs/deploy-template-spec.png" alt-text="deploy template specs":::
+    :::image type="content" source="./media/quickstart-create-template-specs/deploy-template-spec.png" alt-text="Screenshot of 'Deploy' button in the selected Template spec.":::
 
 1. Provide the following values:
 
@@ -453,22 +453,22 @@ Rather than creating a new template spec for the revised template, add a new ver
 
 1. In your template spec, select **Create new version**.
 
-   :::image type="content" source="./media/quickstart-create-template-specs/select-versions.png" alt-text="create new version":::
+   :::image type="content" source="./media/quickstart-create-template-specs/select-versions.png" alt-text="Screenshot of 'Create new version' button in Template spec details.":::
 
 1. Name the new version `2.0` and optionally add notes. Select **Edit template**.
 
-   :::image type="content" source="./media/quickstart-create-template-specs/add-version-name.png" alt-text="name new version":::
+   :::image type="content" source="./media/quickstart-create-template-specs/add-version-name.png" alt-text="Screenshot of naming the new version and selecting 'Edit template' button.":::
 
 1. Replace the contents of the template with your updated template. Select **Review + Save**.
 1. Select **Save changes**.
 
 1. To deploy the new version, select **Versions**
 
-   :::image type="content" source="./media/quickstart-create-template-specs/see-versions.png" alt-text="list versions":::
+   :::image type="content" source="./media/quickstart-create-template-specs/see-versions.png" alt-text="Screenshot of 'Versions' tab in Template spec details.":::
 
 1. For the version you want to deploy, select the three dots and **Deploy**.
 
-   :::image type="content" source="./media/quickstart-create-template-specs/deploy-version.png" alt-text="select version to deploy":::
+   :::image type="content" source="./media/quickstart-create-template-specs/deploy-version.png" alt-text="Screenshot of 'Deploy' option in the context menu of a specific version.":::
 
 1. Fill in the fields as you did when deploying the earlier version.
 1. Select **Review + create**.

articles/azure-resource-manager/templates/quickstart-create-templates-use-the-portal.md

@@ -26,29 +26,29 @@ Rather than manually building an entire ARM template, let's start by retrieving
 1. In a web browser, go to the [Azure portal](https://portal.azure.com) and sign in.
 1. From the Azure portal search bar, search for **deploy a custom template** and then select it from the available options.
 
-    :::image type="content" source="./media/quickstart-create-templates-use-the-portal/search-custom-template.png" alt-text="Screenshot of Search for Custom Template.":::
+    :::image type="content" source="./media/quickstart-create-templates-use-the-portal/search-custom-template.png" alt-text="Screenshot of searching for custom template in Azure portal.":::
 
 1. For **Template** source, notice that **Quickstart template** is selected by default. You can keep this selection. In the drop-down, search for *quickstarts/microsoft.storage/storage-account-create* and select it. After finding the quickstart template, select **Select template.**
 
-    :::image type="content" source="./media/quickstart-create-templates-use-the-portal/select-custom-template.png" alt-text="Screenshot of Select Quickstart Template.":::
+    :::image type="content" source="./media/quickstart-create-templates-use-the-portal/select-custom-template.png" alt-text="Screenshot of selecting a Quickstart Template in Azure portal.":::
 
 1. In the next blade, you provide custom values to use for the deployment.
 
     For **Resource group**, select **Create new** and provide *myResourceGroup* for the name. You can use the default values for the other fields. When you've finished providing values, select **Review + create**.
 
-    :::image type="content" source="./media/quickstart-create-templates-use-the-portal/input-fields-template.png" alt-text="Screenshot for Input Fields for Template.":::
+    :::image type="content" source="./media/quickstart-create-templates-use-the-portal/input-fields-template.png" alt-text="Screenshot of input fields for custom template in Azure portal.":::
 
 1. The portal validates your template and the values you provided. After validation succeeds, select **Create** to start the deployment.
 
-    :::image type="content" source="./media/quickstart-create-templates-use-the-portal/template-validation.png" alt-text="Screenshot for Validation and create.":::
+    :::image type="content" source="./media/quickstart-create-templates-use-the-portal/template-validation.png" alt-text="Screenshot of template validation and create button in Azure portal.":::
 
 1. Once your validation has passed, you'll see the status of the deployment. When it completes successfully, select **Go to resource** to see the storage account.
 
-     :::image type="content" source="./media/quickstart-create-templates-use-the-portal/deploy-success.png" alt-text="Screenshot for Deployment Succeeded Notification.":::
+     :::image type="content" source="./media/quickstart-create-templates-use-the-portal/deploy-success.png" alt-text="Screenshot of deployment succeeded notification in Azure portal.":::
 
 1. From this screen, you can view the new storage account and its properties.
 
-     :::image type="content" source="./media/quickstart-create-templates-use-the-portal/view-storage-account.png" alt-text="Screenshot for View Deployment Page.":::
+     :::image type="content" source="./media/quickstart-create-templates-use-the-portal/view-storage-account.png" alt-text="Screenshot of view deployment page with storage account in Azure portal.":::
 
 ## Edit and deploy the template
 
@@ -60,11 +60,11 @@ In this section, let's suppose you have an ARM template that you want to deploy
 
 1. This time, select **Build your own template in the editor**.
 
-   :::image type="content" source="./media/quickstart-create-templates-use-the-portal/build-own-template.png" alt-text="Screenshot for Build your own template.":::  
+   :::image type="content" source="./media/quickstart-create-templates-use-the-portal/build-own-template.png" alt-text="Screenshot of build your own template option in Azure portal.":::  
 
 1. You see a blank template.
 
-   :::image type="content" source="./media/quickstart-create-templates-use-the-portal/blank-template.png" alt-text="Screenshot for Blank Template.":::
+   :::image type="content" source="./media/quickstart-create-templates-use-the-portal/blank-template.png" alt-text="Screenshot of blank ARM template in Azure portal.":::
 
 1. Replace the blank template with the following template. It deploys a virtual network with a subnet.
 
@@ -143,25 +143,25 @@ In this section, let's suppose you have an ARM template that you want to deploy
 
 1. When the deployment completes, you see the status of the deployment. This time select the name of the resource group.
 
-   :::image type="content" source="./media/quickstart-create-templates-use-the-portal/view-second-deployment.png" alt-text="Screenshot for View second deployment.":::
+   :::image type="content" source="./media/quickstart-create-templates-use-the-portal/view-second-deployment.png" alt-text="Screenshot of view second deployment page in Azure portal.":::
 
 1. Notice that your resource group now contains a storage account and a virtual network.
 
-   :::image type="content" source="./media/quickstart-create-templates-use-the-portal/view-resource-group.png" alt-text="Screenshot for View Storage Account and Virtual Network.":::
+   :::image type="content" source="./media/quickstart-create-templates-use-the-portal/view-resource-group.png" alt-text="Screenshot of resource group with storage account and virtual network in Azure portal.":::
 
 ## Export a custom template 
 
 Sometimes the easiest way to work with an ARM template is to have the portal generate it for you. The portal can create an ARM template based on the current state of your resource group.
 
 1. In your resource group, select **Export template**. 
 
-   :::image type="content" source="./media/quickstart-create-templates-use-the-portal/export-template.png" alt-text="Screenshot for Export Template.":::
+   :::image type="content" source="./media/quickstart-create-templates-use-the-portal/export-template.png" alt-text="Screenshot of export template option in Azure portal.":::
 
 1. The portal generates a template for you based on the current state of the resource group. Notice that this template isn't the same as either template you deployed earlier. It contains definitions for both the storage account and virtual network, along with other resources like a blob service that was automatically created for your storage account.
 
 1. To save this template for later use, select **Download**.
 
-   :::image type="content" source="./media/quickstart-create-templates-use-the-portal/download-template.png" alt-text="Screenshot for Download exported template."::: 
+   :::image type="content" source="./media/quickstart-create-templates-use-the-portal/download-template.png" alt-text="Screenshot of download button for exported ARM template in Azure portal."::: 
 
 You now have an ARM template that represents the current state of the resource group. This template is auto-generated. Before using the template for production deployments, you may want to revise it, such as adding parameters for template reuse.