upldate alt text

Author: tfitzmac

articles/azure-resource-manager/templates/deploy-portal.md

@@ -22,19 +22,19 @@ This article shows both methods.
 
 1. To create a new resource group, select **Resource groups** from the [Azure portal](https://portal.azure.com).
 
-   ![Select resource groups](./media/deploy-portal/select-resource-groups.png)
+   :::image type="content" source="./media/deploy-portal/select-resource-groups.png" alt-text="Screenshot of selecting resource groups in Azure portal":::
 
 1. Under Resource groups, select **Add**.
 
-   ![Add resource group](./media/deploy-portal/add-resource-group.png)
+   :::image type="content" source="./media/deploy-portal/add-resource-group.png" alt-text="Screenshot of adding a resource group in Azure portal":::
 
 1. Select or enter the following property values:
 
     - **Subscription**: Select an Azure subscription.
     - **Resource group**: Give the resource group a name.
     - **Region**: Specify an Azure location. This location is where the resource group stores metadata about the resources. For compliance reasons, you may want to specify where that metadata is stored. In general, we recommend that you specify a location where most of your resources will be. Using the same location can simplify your template.
 
-   ![Set group values](./media/deploy-portal/set-group-properties.png)
+   :::image type="content" source="./media/deploy-portal/set-group-properties.png" alt-text="Screenshot of setting resource group property values in Azure portal":::
 
 1. Select **Review + create**.
 1. Review the values, and then select **Create**.
@@ -46,25 +46,25 @@ After you create a resource group, you can deploy resources to the group from th
 
 1. To start a deployment, select **Create a resource** from the [Azure portal](https://portal.azure.com).
 
-   ![New resource](./media/deploy-portal/new-resources.png)
+   :::image type="content" source="./media/deploy-portal/new-resources.png" alt-text="Screenshot of creating a new resource in Azure portal":::
 
 1. Find the type of resource you would like to deploy. The resources are organized in categories. If you don't see the particular solution you would like to deploy, you can search the Marketplace for it. The following screenshot shows that Ubuntu Server is selected.
 
-   ![Select resource type](./media/deploy-portal/select-resource-type.png)
+   :::image type="content" source="./media/deploy-portal/select-resource-type.png" alt-text="Screenshot of selecting a resource type in Azure portal":::
 
 1. Depending on the type of selected resource, you have a collection of relevant properties to set before deployment. For all types, you must select a destination resource group. The following image shows how to create a Linux virtual machine and deploy it to the resource group you created.
 
-   ![Create resource group](./media/deploy-portal/select-existing-group.png)
+   :::image type="content" source="./media/deploy-portal/select-existing-group.png" alt-text="Screenshot of creating a Linux virtual machine and deploying it to a resource group in Azure portal":::
 
    You can decide to create a resource group when deploying your resources. Select **Create new** and give the resource group a name.
 
 1. Your deployment begins. The deployment could take several minutes. Some resources take longer time than other resources. When the deployment has finished, you see a notification. Select **Go to resource** to open
 
-   ![View notification](./media/deploy-portal/view-notification.png)
+   :::image type="content" source="./media/deploy-portal/view-notification.png" alt-text="Screenshot of viewing deployment notification in Azure portal":::
 
 1. After deploying your resources, you can add more resources to the resource group by selecting **Add**.
 
-   ![Add resource](./media/deploy-portal/add-resource.png)
+   :::image type="content" source="./media/deploy-portal/add-resource.png" alt-text="Screenshot of adding a resource to a resource group in Azure portal":::
 
 Although you didn't see it, the portal used an ARM template to deploy the resources you selected. You can find the template from the deployment history. For more information, see [Export template after deployment](export-template-portal.md#export-template-after-deployment).
 
@@ -77,7 +77,7 @@ If you want to execute a deployment but not use any of the templates in the Mark
 
 1. To deploy a customized template through the portal, select **Create a resource**, search for **template**. and then select **Template deployment**.
 
-   ![Search template deployment](./media/deploy-portal/search-template.png)
+   :::image type="content" source="./media/deploy-portal/search-template.png" alt-text="Screenshot of searching for template deployment in Azure portal":::
 
 1. Select **Create**.
 1. You see several options for creating a template:
@@ -86,7 +86,7 @@ If you want to execute a deployment but not use any of the templates in the Mark
     - **Common templates**: Select from common solutions.
     - **Load a GitHub quickstart template**: Select from [quickstart templates](https://azure.microsoft.com/resources/templates/).
 
-   ![View options](./media/deploy-portal/see-options.png)
+   :::image type="content" source="./media/deploy-portal/see-options.png" alt-text="Screenshot of template creation options in Azure portal":::
 
     This tutorial provides the instruction for loading a quickstart template.
 
@@ -99,7 +99,7 @@ If you want to execute a deployment but not use any of the templates in the Mark
 
 1. Select **Edit template** to explore the portal template editor. The template is loaded in the editor. Notice there are two parameters: `storageAccountType` and `location`.
 
-   ![Create template](./media/deploy-portal/show-json.png)
+   :::image type="content" source="./media/deploy-portal/show-json.png" alt-text="Screenshot of editing a JSON template in Azure portal":::
 
 1. Make a minor change to the template. For example, update the `storageAccountName` variable to:
 

articles/azure-resource-manager/templates/deployment-script-template-configure-dev.md

@@ -212,7 +212,7 @@ You also can upload the file by using the Azure portal or the Azure CLI.
 2. Open the container group. The default container group name is the project name appended with *cg*. The container instance is in the **Running** state.
 3. In the resource menu, select **Containers**. The container instance name is the project name appended with *container*.
 
-    ![Screenshot of the deployment script connect container instance in the Azure portal.](./media/deployment-script-template-configure-dev/deployment-script-container-instance-connect.png)
+    :::image type="content" source="./media/deployment-script-template-configure-dev/deployment-script-container-instance-connect.png" alt-text="Screenshot of the deployment script connect container instance option in the Azure portal.":::
 
 4. Select **Connect**, and then select **Connect**. If you can't connect to the container instance, restart the container group and try again.
 5. In the console pane, run the following commands:
@@ -225,7 +225,7 @@ You also can upload the file by using the Azure portal or the Azure CLI.
 
     The output is **Hello John Dole**.
 
-    ![Screenshot of the deployment script connect container instance test output in the console.](./media/deployment-script-template-configure-dev/deployment-script-container-instance-test.png)
+    :::image type="content" source="./media/deployment-script-template-configure-dev/deployment-script-container-instance-test.png" alt-text="Screenshot of the deployment script connect container instance test output displayed in the console.":::
 
 ## Use an Azure CLI container instance
 
@@ -402,7 +402,7 @@ You also can upload the file by using the Azure portal or the Azure CLI.
 1. Open the container group. The default container group name is the project name appended with *cg*. The container instance is shown in the **Running** state.
 1. In the resource menu, select **Containers**. The container instance name is the project name appended with *container*.
 
-    ![deployment script connect container instance](./media/deployment-script-template-configure-dev/deployment-script-container-instance-connect.png)
+    :::image type="content" source="./media/deployment-script-template-configure-dev/deployment-script-container-instance-connect.png" alt-text="Screenshot of the deployment script connect container instance option in the Azure portal.":::
 
 1. Select **Connect**, and then select **Connect**. If you can't connect to the container instance, restart the container group and try again.
 1. In the console pane, run the following commands:
@@ -415,7 +415,7 @@ You also can upload the file by using the Azure portal or the Azure CLI.
 
     The output is **Hello John Dole**.
 
-    ![deployment script container instance test](./media/deployment-script-template-configure-dev/deployment-script-container-instance-test-cli.png)
+    :::image type="content" source="./media/deployment-script-template-configure-dev/deployment-script-container-instance-test-cli.png" alt-text="Screenshot of the deployment script container instance test output displayed in the console.":::
 
 ## Use Docker
 
@@ -460,7 +460,7 @@ You also need to configure file sharing to mount the directory, which contains t
 
 1. The following screenshot shows how to run a PowerShell script, given that you have a *helloworld.ps1* file in the shared drive.
 
-    ![Resource Manager template deployment script docker cmd](./media/deployment-script-template/resource-manager-deployment-script-docker-cmd.png)
+    :::image type="content" source="./media/deployment-script-template/resource-manager-deployment-script-docker-cmd.png" alt-text="Screenshot of the Resource Manager template deployment script using Docker command.":::
 
 After the script is tested successfully, you can use it as a deployment script in your templates.
 

articles/azure-resource-manager/templates/deployment-script-template.md

@@ -225,7 +225,7 @@ Write-Host "Press [ENTER] to continue ..."
 
 The output looks like:
 
-![Resource Manager template deployment script hello world output](./media/deployment-script-template/resource-manager-template-deployment-script-helloworld-output.png)
+:::image type="content" source="./media/deployment-script-template/resource-manager-template-deployment-script-helloworld-output.png" alt-text="Screenshot of Resource Manager template deployment script hello world output.":::
 
 ## Use external scripts
 
@@ -366,7 +366,7 @@ The max allowed size for environment variables is 64 KB.
 
 The script service creates a [storage account](../../storage/common/storage-account-overview.md) (unless you specify an existing storage account) and a [container instance](../../container-instances/container-instances-overview.md) for script execution. If these resources are automatically created by the script service, both resources have the `azscripts` suffix in the resource names.
 
-![Resource Manager template deployment script resource names](./media/deployment-script-template/resource-manager-template-deployment-script-resources.png)
+:::image type="content" source="./media/deployment-script-template/resource-manager-template-deployment-script-resources.png" alt-text="Screenshot of Resource Manager template deployment script resource names.":::
 
 The user script, the execution results, and the stdout file are stored in the files shares of the storage account. There's a folder called `azscripts`. In the folder, there are two more folders for the input and the output files: `azscriptinput` and `azscriptoutput`.
 
@@ -376,7 +376,7 @@ The output folder contains a _executionresult.json_ and the script output file.
 
 After you deploy a deployment script resource, the resource is listed under the resource group in the Azure portal. The following screenshot shows the **Overview** page of a deployment script resource:
 
-![Resource Manager template deployment script portal overview](./media/deployment-script-template/resource-manager-deployment-script-portal.png)
+:::image type="content" source="./media/deployment-script-template/resource-manager-deployment-script-portal.png" alt-text="Screenshot of Resource Manager template deployment script portal overview.":::
 
 The overview page displays some important information of the resource, such as **Provisioning state**, **Storage account**, **Container instance**, and **Logs**.
 
@@ -568,7 +568,7 @@ It only works before the deployment script resources are deleted.
 
 To see the deploymentScripts resource in the portal, select **Show hidden types**:
 
-![Resource Manager template deployment script, show hidden types, portal](./media/deployment-script-template/resource-manager-deployment-script-portal-show-hidden-types.png)
+:::image type="content" source="./media/deployment-script-template/resource-manager-deployment-script-portal-show-hidden-types.png" alt-text="Screenshot of Resource Manager template deployment script with show hidden types option in portal.":::
 
 ## Clean up deployment script resources
 

articles/azure-resource-manager/templates/deployment-tutorial-pipeline.md

@@ -48,7 +48,7 @@ If you don't have a GitHub account, see [Prerequisites](#prerequisites).
 1. Sign in to [GitHub](https://github.com).
 1. Select your account image on the upper right corner, and then select **Your repositories**.
 
-    ![Azure Resource Manager Azure DevOps Azure Pipelines create GitHub repository](./media/deployment-tutorial-pipeline/azure-resource-manager-devops-pipelines-github-repository.png)
+    :::image type="content" source="./media/deployment-tutorial-pipeline/azure-resource-manager-devops-pipelines-github-repository.png" alt-text="Screenshot of creating a GitHub repository for Azure Resource Manager Azure DevOps Azure Pipelines.":::
 
 1. Select **New**, a green button.
 1. In **Repository name**, enter a repository name.  For example, **ARMPipeline-repo**. Remember to replace any of **ARMPipeline** with your project name. You can select either **Public** or **private** for going through this tutorial. And then select **Create repository**.
@@ -115,7 +115,7 @@ A DevOps organization is needed before you can proceed to the next procedure. If
 1. Select a DevOps organization from the left, and then select **New project**. If you don't have any projects, the create project page is opened automatically.
 1. Enter the following values:
 
-    ![Azure Resource Manager Azure DevOps Azure Pipelines create Azure DevOps project](./media/deployment-tutorial-pipeline/azure-resource-manager-devops-pipelines-create-devops-project.png)
+    :::image type="content" source="./media/deployment-tutorial-pipeline/azure-resource-manager-devops-pipelines-create-devops-project.png" alt-text="Screenshot of creating an Azure DevOps project for Azure Resource Manager Azure DevOps Azure Pipelines.":::
 
     * **Project name**: Enter a project name. You can use the project name you picked at the very beginning of the tutorial.
     * **Visibility**: Select **Private**.
@@ -151,7 +151,7 @@ To create a pipeline with a step to deploy a template:
 1. Select **Create pipeline**.
 1. From the **Connect** tab, select **GitHub**. If asked, enter your GitHub credentials, and then follow the instructions. If you see the following screen, select **Only select repositories**, and verify your repository is in the list before you select **Approve & Install**.
 
-    ![Azure Resource Manager Azure DevOps Azure Pipelines only select repositories](./media/deployment-tutorial-pipeline/azure-resource-manager-devops-pipelines-only-select-repositories.png)
+    :::image type="content" source="./media/deployment-tutorial-pipeline/azure-resource-manager-devops-pipelines-only-select-repositories.png" alt-text="Screenshot of selecting repositories for Azure Resource Manager Azure DevOps Azure Pipelines.":::
 
 1. From the **Select** tab, select your repository. The default name is `[YourAccountName]/[YourGitHubRepositoryName]`.
 1. From the **Configure** tab, select **Starter pipeline**. It shows the _azure-pipelines.yml_ pipeline file with two script steps.
@@ -174,21 +174,21 @@ To create a pipeline with a step to deploy a template:
     * **Deployment mode**: Select **Incremental**.
     * **Deployment name**: Enter **DeployPipelineTemplate**. Select **Advanced** before you can see **Deployment name**.
 
-    ![Screenshot shows the ARM template deployment page with required values entered.](./media/deployment-tutorial-pipeline/resource-manager-template-pipeline-configure.png)
+    :::image type="content" source="./media/deployment-tutorial-pipeline/resource-manager-template-pipeline-configure.png" alt-text="Screenshot of the ARM template deployment page with required values entered for Azure DevOps Azure Pipelines.":::
 
 1. Select **Add**.
 
     For more information about the task, see [Azure Resource Group Deployment task](/azure/devops/pipelines/tasks/deploy/azure-resource-group-deployment), and [Azure Resource Manager template deployment task](https://github.com/microsoft/azure-pipelines-tasks/blob/master/Tasks/AzureResourceManagerTemplateDeploymentV3/README.md)
 
     The _.yml_ file shall be similar to:
 
-    ![Screenshot shows the Review page with the new pipeline titled Review your pipeline YAML.](./media/deployment-tutorial-pipeline/azure-resource-manager-devops-pipelines-yml.png)
+    :::image type="content" source="./media/deployment-tutorial-pipeline/azure-resource-manager-devops-pipelines-yml.png" alt-text="Screenshot of the Review page with the new pipeline titled Review your pipeline YAML for Azure DevOps Azure Pipelines.":::
 
 1. Select **Save and run**.
 1. From the **Save and run** pane, select **Save and run** again. A copy of the YAML file is saved into the connected repository. You can see the YAML file by browse to your repository.
 1. Verify that the pipeline is executed successfully.
 
-    ![Azure Resource Manager Azure DevOps Azure Pipelines yaml](./media/deployment-tutorial-pipeline/azure-resource-manager-devops-pipelines-status.png)
+    :::image type="content" source="./media/deployment-tutorial-pipeline/azure-resource-manager-devops-pipelines-status.png" alt-text="Screenshot of Azure Resource Manager Azure DevOps Azure Pipelines YAML file.":::
 
 ## Verify the deployment
 
@@ -204,7 +204,7 @@ When you update the template and push the changes to the remote repository, the
 1. Open _linkedStorageAccount.json_ from your local repository in Visual Studio Code or any text editor.
 1. Update the **defaultValue** of **storageAccountType** to **Standard_GRS**. See the following screenshot:
 
-    ![Azure Resource Manager Azure DevOps Azure Pipelines update yaml](./media/deployment-tutorial-pipeline/azure-resource-manager-devops-pipelines-update-yml.png)
+    :::image type="content" source="./media/deployment-tutorial-pipeline/azure-resource-manager-devops-pipelines-update-yml.png" alt-text="Screenshot of updating the YAML file for Azure Resource Manager Azure DevOps Azure Pipelines.":::
 
 1. Save the changes.
 1. Push the changes to the remote repository by running the following commands from Git Bash/Shell.