Merge pull request #247696 from tfitzmac/0808alttext3

update alt text

Author: prmerger-automator[bot]

articles/azure-resource-manager/templates/deploy-what-if.md

@@ -49,7 +49,7 @@ To use what-if in Azure CLI, you must have Azure CLI 2.14.0 or later. If needed,
 
 When you use what-if in PowerShell or Azure CLI, the output includes color-coded results that help you see the different types of changes.
 
-![Resource Manager template deployment what-if operation fullresourcepayload and change types](./media/template-deploy-what-if/resource-manager-deployment-whatif-change-types.png)
+:::image type="content" source="./media/template-deploy-what-if/resource-manager-deployment-whatif-change-types.png" alt-text="Screenshot of Resource Manager template deployment what-if operation with full resource payload and change types.":::
 
 The text output is:
 
@@ -264,7 +264,7 @@ az deployment group what-if \
 
 The what-if output appears similar to:
 
-![Resource Manager template deployment what-if operation output](./media/template-deploy-what-if/resource-manager-deployment-whatif-change-types.png)
+:::image type="content" source="./media/template-deploy-what-if/resource-manager-deployment-whatif-change-types.png" alt-text="Screenshot of Resource Manager template deployment what-if operation output showing changes.":::
 
 The text output is:
 
@@ -360,7 +360,7 @@ az deployment group create \
 
 Because no resources are defined in the template and the deployment mode is set to complete, the virtual network will be deleted.
 
-![Resource Manager template deployment what-if operation output deployment mode complete](./media/template-deploy-what-if/resource-manager-deployment-whatif-output-mode-complete.png)
+:::image type="content" source="./media/template-deploy-what-if/resource-manager-deployment-whatif-output-mode-complete.png" alt-text="Screenshot of Resource Manager template deployment what-if operation output in deployment mode complete.":::
 
 The text output is:
 

articles/azure-resource-manager/templates/export-template-portal.md

@@ -27,14 +27,14 @@ To export one or more resources from a resource group:
 
 1. Select one or more resources by selecting the checkboxes.  To select all, select the checkbox on the left of **Name**. The **Export template** menu item only becomes enabled after you've selected at least one resource.
 
-   ![Export all resources](./media/export-template-portal/select-all-resources.png)
+   :::image type="content" source="./media/export-template-portal/select-all-resources.png" alt-text="Screenshot of selecting all resources for export in Azure portal.":::
 
     On the screenshot, only the storage account is selected.
 1. Select **Export template**.
 
 1. The exported template is displayed, and is available to download and deploy.
 
-   ![Show template](./media/export-template-portal/show-template.png)
+   :::image type="content" source="./media/export-template-portal/show-template.png" alt-text="Screenshot of the displayed exported template in Azure portal.":::
 
    **Include parameters** is selected by default.  When selected, all template parameters will be included when the template is generated. If you’d like to author your own parameters, toggle this checkbox to not include them.
 
@@ -48,7 +48,7 @@ To export one resource:
 
 1. For that resource, select **Export template** in the left pane.
 
-   ![Export resource](./media/export-template-portal/export-single-resource.png)
+   :::image type="content" source="./media/export-template-portal/export-single-resource.png" alt-text="Screenshot of exporting a single resource in Azure portal.":::
 
 1. The exported template is displayed, and is available to download and deploy. The template only contains the single resource. **Include parameters** is selected by default.  When selected, all template parameters will be included when the template is generated. If you’d like to author your own parameters, toggle this checkbox to not include them.
 
@@ -62,7 +62,7 @@ The portal has the option of downloading a template before deploying it. This op
 
 1. After passing validation, but before starting the deployment, select **Download a template for automation**.
 
-   ![Download template](./media/export-template-portal/download-before-deployment.png)
+   :::image type="content" source="./media/export-template-portal/download-before-deployment.png" alt-text="Screenshot of the option to download a template before deployment in Azure portal.":::
 
 1. The template is displayed and is available for download and deploy.
 
@@ -74,15 +74,15 @@ You can export the template that was used to deploy existing resources. The temp
 
 1. Select the link under **Deployments**.
 
-   ![Select deployment history](./media/export-template-portal/select-deployment-history.png)
+   :::image type="content" source="./media/export-template-portal/select-deployment-history.png" alt-text="Screenshot of selecting deployment history in Azure portal.":::
 
 1. Select one of the deployments from the deployment history.
 
-   ![Select deployment](./media/export-template-portal/select-details.png)
+   :::image type="content" source="./media/export-template-portal/select-details.png" alt-text="Screenshot of selecting a specific deployment from deployment history in Azure portal.":::
 
 1. Select **Template**. The template used for this deployment is displayed, and is available for download.
 
-   ![Select template](./media/export-template-portal/show-template-from-history.png)
+   :::image type="content" source="./media/export-template-portal/show-template-from-history.png" alt-text="Screenshot of selecting the template used for a specific deployment in Azure portal.":::
 
 ## Next steps
 

articles/azure-resource-manager/templates/key-vault-parameter.md

@@ -160,7 +160,7 @@ When using a key vault with the template for a [Managed Application](../managed-
 
 With this approach, you reference the key vault in the parameter file, not the template. The following image shows how the parameter file references the secret and passes that value to the template.
 
-![Resource Manager key vault integration Static ID diagram](./media/key-vault-parameter/statickeyvault.png)
+:::image type="content" source="./media/key-vault-parameter/statickeyvault.png" alt-text="Diagram showing Resource Manager key vault integration with Static ID.":::
 
 [Tutorial: Integrate Azure Key Vault in Resource Manager Template deployment](./template-tutorial-use-key-vault.md) uses this method.
 
@@ -267,7 +267,7 @@ You can't dynamically generate the resource ID in the parameters file because te
 
 In your parent template, you add the nested template and pass in a parameter that contains the dynamically generated resource ID. The following image shows how a parameter in the linked template references the secret.
 
-![Dynamic ID](./media/key-vault-parameter/dynamickeyvault.png)
+:::image type="content" source="./media/key-vault-parameter/dynamickeyvault.png" alt-text="Diagram illustrating dynamic ID generation for key vault secret.":::
 
 The following template dynamically creates the key vault ID and passes it as a parameter.
 

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

@@ -31,7 +31,7 @@ If you're trying to decide between using ARM templates and one of the other infr
 
 * **Orchestration**: You don't have to worry about the complexities of ordering operations. Resource Manager orchestrates the deployment of interdependent resources so they're created in the correct order. When possible, Resource Manager deploys resources in parallel so your deployments finish faster than serial deployments. You deploy the template through one command, rather than through multiple imperative commands.
 
-   ![Template deployment comparison](./media/overview/template-processing.png)
+   :::image type="content" source="./media/overview/template-processing.png" alt-text="Diagram that shows the difference between imperative and declarative deployment.":::
 
 * **Modular files**: You can break your templates into smaller, reusable components and link them together at deployment time. You can also nest one template inside another template.
 
@@ -47,7 +47,7 @@ If you're trying to decide between using ARM templates and one of the other infr
 
 * **Tracked deployments**: In the Azure portal, you can review the deployment history and get information about the template deployment. You can see the template that was deployed, the parameter values passed in, and any output values. Other infrastructure as code services aren't tracked through the portal.
 
-   ![Deployment history](./media/overview/deployment-history.png)
+   :::image type="content" source="./media/overview/deployment-history.png" alt-text="Screenshot of the Azure portal showing deployment history.":::
 
 * **Policy as code**: [Azure Policy](../../governance/policy/overview.md) is a policy as code framework to automate governance. If you're using Azure policies, policy remediation is done on non-compliant resources when deployed through templates.
 
@@ -125,15 +125,15 @@ To deploy a template, use any of the following options:
 
 How you define templates and resource groups is entirely up to you and how you want to manage your solution. For example, you can deploy your three tier application through a single template to a single resource group.
 
-![three tier template](./media/overview/3-tier-template.png)
+:::image type="content" source="./media/overview/3-tier-template.png" alt-text="Diagram that shows a three-tier application deployment using a single template.":::
 
 But, you don't have to define your entire infrastructure in a single template. Often, it makes sense to divide your deployment requirements into a set of targeted, purpose-specific templates. You can easily reuse these templates for different solutions. To deploy a particular solution, you create a main template that links all the required templates. The following image shows how to deploy a three tier solution through a parent template that includes three nested templates.
 
-![nested tier template](./media/overview/nested-tiers-template.png)
+:::image type="content" source="./media/overview/nested-tiers-template.png" alt-text="Diagram that shows a three-tier application deployment using nested templates.":::
 
 If you envision your tiers having separate lifecycles, you can deploy your three tiers to separate resource groups. Notice the resources can still be linked to resources in other resource groups.
 
-![tier template](./media/overview/tier-templates.png)
+:::image type="content" source="./media/overview/tier-templates.png" alt-text="Diagram that shows a three-tier application deployment with separate resource groups.":::
 
 For information about nested templates, see [Using linked templates with Azure Resource Manager](linked-templates.md).
 

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

@@ -318,7 +318,7 @@ For inline comments, you can use either `//` or `/* ... */`. In Visual Studio Co
 
 In Visual Studio Code, the [Azure Resource Manager Tools extension](quickstart-create-templates-use-visual-studio-code.md) can automatically detect an ARM template and change the language mode. If you see **Azure Resource Manager Template** at the bottom-right corner of Visual Studio Code, you can use the inline comments. The inline comments are no longer marked as invalid.
 
-![Visual Studio Code Azure Resource Manager template mode](./media/template-syntax/resource-manager-template-editor-mode.png)
+:::image type="content" source="./media/template-syntax/resource-manager-template-editor-mode.png" alt-text="Screenshot of Visual Studio Code in Azure Resource Manager template mode.":::
 
 In Bicep, see [comments](../bicep/file.md#comments).
 
@@ -350,7 +350,7 @@ For `parameters`, add a `metadata` object with a `description` property.
 
 When deploying the template through the portal, the text you provide in the description is automatically used as a tip for that parameter.
 
-![Show parameter tip](./media/template-syntax/show-parameter-tip.png)
+:::image type="content" source="./media/template-syntax/show-parameter-tip.png" alt-text="Screenshot showing parameter tip in Azure portal.":::
 
 For `resources`, add a `comments` element or a `metadata` object. The following example shows both a `comments` element and a `metadata` object.
 
@@ -430,4 +430,4 @@ In Bicep, see [multi-line strings](../bicep/file.md#multi-line-strings).
 * For details about the functions you can use from within a template, see [ARM template functions](template-functions.md).
 * To combine several templates during deployment, see [Using linked and nested templates when deploying Azure resources](linked-templates.md).
 * For recommendations about creating templates, see [ARM template best practices](./best-practices.md).
-* For answers to common questions, see [Frequently asked questions about ARM templates](frequently-asked-questions.yml).
+* For answers to common questions, see [Frequently asked questions about ARM templates](frequently-asked-questions.yml).

articles/azure-resource-manager/templates/template-cloud-consistency.md

@@ -22,7 +22,7 @@ Microsoft offers intelligent, enterprise-ready cloud services in many locations,
 
 At the core of all these clouds, Azure Resource Manager provides an API that allows a wide variety of user interfaces to communicate with the Azure platform. This API gives you powerful infrastructure-as-code capabilities. Any type of resource that is available on the Azure cloud platform can be deployed and configured with Azure Resource Manager. With a single template, you can deploy and configure your complete application to an operational end state.
 
-![Azure environments](./media/templates-cloud-consistency/environments.png)
+:::image type="content" source="./media/templates-cloud-consistency/environments.png" alt-text="Diagram of various Azure environments including global Azure, sovereign clouds, and Azure Stack.":::
 
 The consistency of global Azure, the sovereign clouds, hosted clouds, and a cloud in your datacenter helps you benefit from Azure Resource Manager. You can reuse your development investments across these clouds when you set up template-based resource deployment and configuration.
 
@@ -210,7 +210,7 @@ Knowing that Azure regions and clouds may differ in their available services, yo
 
 A template deploys and configures resources. A resource type is provided by a resource provider. For example, the compute resource provider (Microsoft.Compute), provides multiple resource types such as virtualMachines and availabilitySets. Each resource provider provides an API to Azure Resource Manager defined by a common contract, enabling a consistent, unified authoring experience across all resource providers. However, a resource provider that is available in global Azure may not be available in a sovereign cloud or an Azure Stack region.
 
-![Resource providers](./media/templates-cloud-consistency/resource-providers.png)
+:::image type="content" source="./media/templates-cloud-consistency/resource-providers.png" alt-text="Diagram illustrating the relationship between resource providers, resource types, and API versions.":::
 
 To verify the resource providers that are available in a given cloud, run the following script in the [Azure CLI](/cli/azure/):
 
@@ -650,7 +650,7 @@ It's a challenge to keep track of all related settings, capabilities, and limita
 
 The following image shows a typical example of a development process for a team using an integrated development environment (IDE). At different stages in the timeline, different test types are executed. Here, two developers are working on the same solution, but this scenario applies equally to a single developer or a large team. Each developer typically creates a local copy of a central repository, enabling each one to work on the local copy without impacting the others who may be working on the same files.
 
-![Diagram shows two sets of unit tests and integration tests in parallel on local I D E, which merge in the C I / C D development flow into unit tests, then integration tests, then test deployment, then deployment.](./media/templates-cloud-consistency/workflow.png)
+:::image type="content" source="./media/templates-cloud-consistency/workflow.png" alt-text="Diagram showing parallel unit tests and integration tests in local IDEs, merging into CI/CD development flow with unit tests, integration tests, test deployment, and final deployment.":::
 
 Consider the following tips for testing and automation:
 

articles/azure-resource-manager/templates/template-tutorial-add-tags.md

@@ -76,7 +76,7 @@ You can verify the deployment by exploring the resource group from the Azure por
 1. Select the resource group you deployed to.
 1. Select one of the resources, such as the storage account resource. You see that it now has tags.
 
-   ![Show tags](./media/template-tutorial-add-tags/show-tags.png)
+   :::image type="content" source="./media/template-tutorial-add-tags/show-tags.png" alt-text="Screenshot of Azure portal showing tags on a storage account resource.":::
 
 ## Clean up resources
 

articles/azure-resource-manager/templates/template-tutorial-create-multiple-instances.md

@@ -12,7 +12,7 @@ ms.author: jgao
 
 Learn how to iterate in your Azure Resource Manager template (ARM template) to create multiple instances of an Azure resource. In this tutorial, you modify a template to create three storage account instances.
 
-![Azure Resource Manager creates multiple instances diagram](./media/template-tutorial-create-multiple-instances/resource-manager-template-create-multiple-instances-diagram.png)
+:::image type="content" source="./media/template-tutorial-create-multiple-instances/resource-manager-template-create-multiple-instances-diagram.png" alt-text="Diagram showing Azure Resource Manager creating multiple instances.":::
 
 This tutorial covers the following tasks:
 
@@ -52,7 +52,7 @@ The existing template creates one storage account. You customize the template to
 
 From Visual Studio Code, make the following four changes:
 
-![Azure Resource Manager creates multiple instances](./media/template-tutorial-create-multiple-instances/resource-manager-template-create-multiple-instances.png)
+:::image type="content" source="./media/template-tutorial-create-multiple-instances/resource-manager-template-create-multiple-instances.png" alt-text="Screenshot of Visual Studio Code with Azure Resource Manager creating multiple instances.":::
 
 1. Add a `copy` element to the storage account resource definition. In the `copy` element, you specify the number of iterations and a variable for this loop. The count value must be a positive integer and can't exceed 800.