Fix image links

articles/guidance/guidance-compute-multi-vm.md

@@ -150,8 +150,7 @@ For incoming Internet traffic, the load balancer rules define which traffic can
 
 A deployment for this reference architecture is available on [GitHub][github-folder]. It includes a VNet, NSG, load balancer, and two VMs. It can be deployed with either Windows or Linux VMs. To deploy the architecture, follow these steps: 
 
-1. Right-click the button below and select either "Open link in new tab" or "Open link in new window":  
-   [![Deploy to Azure](./media/blueprints/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fmspnp%2Freference-architectures%2Fmaster%2Fguidance-compute-multi-vm%2Fazuredeploy.json)
+1. Open [this link](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fmspnp%2Freference-architectures%2Fmaster%2Fguidance-compute-multi-vm%2Fazuredeploy.json) in a new tab or browser window. The link takes you to the Azure Portal.  
 2. Once the link has opened in the Azure portal, you must enter values for some of the settings: 
 
    * The **Resource group** name is already defined in the parameter file, so select **Create new** and enter `ra-multi-vm-rg` in the text box.

articles/guidance/guidance-compute-multiple-datacenters.md

@@ -52,7 +52,7 @@ The following diagram builds on the architecture shown in [Running Windows VMs f
 > 
 > 
 
-[![0]][0] 
+![[0]][0] 
 
 * **Primary and secondary regions**. Use two regions to achieve higher availability. One is the primary region. The other region is for failover. 
 * **Azure Traffic Manager**. [Traffic Manager][traffic-manager] routes incoming requests to one of the regions. During normal operations, it routes requests to the primary region. If that region becomes unavailable, Traffic Manager fails over to the secondary region. For more information, see the section [Traffic Manager configuration](#traffic manager-configuration).

articles/guidance/guidance-compute-n-tier-vm-linux.md

@@ -140,8 +140,7 @@ Simplify management of the entire system by using centralized administration too
 
 A deployment for this reference architecture is available on [GitHub][github-folder]. The reference architecture is deployed in three stages. To deploy the architecture, follow these steps: 
 
-1. Right click the button below and select "open in new tab" or "open in new window."  
-   [!["Deploy To Azure"][1]][2]
+1. Open [this link][2] in a new tab or browser window. The link takes you to the Azure Portal.
 2. Once the link has opened in the Azure portal, enter the follow values: 
 
    * The **Resource group** name is already defined in the parameter file, so select **Create New** and enter `ra-ntier-sql-network-rg` in the text box.

articles/guidance/guidance-compute-n-tier-vm.md

@@ -155,8 +155,7 @@ Simplify management of the entire system by using centralized administration too
 
 A deployment for this reference architecture is available on [GitHub][github-folder]. The reference architecture is deployed in three stages. To deploy the architecture, follow these steps: 
 
-1. Right click the button below and select "open in new tab" or "open in new window" to begin the first stage of the deployment.  
-   [!["Deploy To Azure"][1]][2]
+1. Open [this link][2] in a new tab or browser window to begin the first stage of the deployment. The link takes you to the Azure Portal. 
 2. Once the link has opened in the Azure portal, enter the follow values: 
 
    * The **Resource group** name is already defined in the parameter file, so select **Create New** and enter `ra-ntier-sql-network-rg` in the text box.
@@ -165,8 +164,7 @@ A deployment for this reference architecture is available on [GitHub][github-fol
    * Review the terms and conditions, then click the **I agree to the terms and conditions stated above** checkbox.
    * Click on the **Purchase** button.
 3. Check Azure portal notification for a message that the first stage of the deployment is complete.
-4. Right click the button below and select "open in new tab" or "open in new window" to begin the second stage of the deployment.  
-   [!["Deploy To Azure"][1]][3]
+4. Open [this link][3] in a new tab or browser window to begin the second stage of the deployment.
 5. Once the link has opened in the Azure portal, enter the follow values: 
 
    * The **Resource group** name is already defined in the parameter file, so select **Create New** and enter `ra-ntier-sql-workload-rg` in the text box.
@@ -175,8 +173,7 @@ A deployment for this reference architecture is available on [GitHub][github-fol
    * Review the terms and conditions, then click the **I agree to the terms and conditions stated above** checkbox.
    * Click on the **Purchase** button.
 6. Check Azure portal notification for a message that the second stage of deployment is complete.
-7. Right click the button below and select "open in new tab" or "open in new window" to begin the third stage of the deployment.  
-   [!["Deploy To Azure"][1]][4]
+7. Open [this link][4] in a new tab or browser window to begin the third stage of the deployment.
 8. Once the link has opened in the Azure portal, enter the follow values: 
 
    * The **Resource group** name is already defined in the parameter file, so select **Use Existing** and enter `ra-ntier-sql-network-rg` in the text box.

articles/guidance/guidance-hybrid-network-expressroute-vpn-failover.md

@@ -132,8 +132,7 @@ For general Azure security considerations, see [Microsoft cloud services and net
 
 If you have an existing on-premises infrastructure already configured with a suitable network appliance, you can deploy the reference architecture by following these steps:
 
-1. Right-click the button below and select either "Open link in new tab" or "Open link in new window":  
-   [![Deploy to Azure](./media/blueprints/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fmspnp%2Freference-architectures%2Fmaster%2Fguidance-hybrid-network-vpn-er%2Fazuredeploy.json)
+1. Open [this link](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fmspnp%2Freference-architectures%2Fmaster%2Fguidance-hybrid-network-vpn-er%2Fazuredeploy.json) in a new tab or browser window. The link takes you to the Azure Portal.
 2. Wait for the link to open in the Azure portal, then follow these steps:
 
    * The **Resource group** name is already defined in the parameter file, so select **Create New** and enter `ra-hybrid-vpn-er-rg` in the text box.
@@ -142,8 +141,7 @@ If you have an existing on-premises infrastructure already configured with a sui
    * Review the terms and conditions, then click the **I agree to the terms and conditions stated above** checkbox.
    * Click the **Purchase** button.
 3. Wait for the deployment to complete.
-4. Right-click the button below and select either "Open link in new tab" or "Open link in new window":  
-   [![Deploy to Azure](./media/blueprints/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fmspnp%2Freference-architectures%2Fmaster%2Fguidance-hybrid-network-vpn-er%2Fazuredeploy-expressRouteCircuit.json)
+4. Open [this link](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fmspnp%2Freference-architectures%2Fmaster%2Fguidance-hybrid-network-vpn-er%2Fazuredeploy-expressRouteCircuit.json) in a new tab or browser window. 
 5. Wait for the link to open in the Azure portal, then enter then follow these steps:
 
    * Select **Use existing** in the **Resource group** section and enter `ra-hybrid-vpn-er-rg` in the text box.

articles/guidance/guidance-hybrid-network-expressroute.md

@@ -271,8 +271,7 @@ If you must expose management endpoints for VMs to an external network, use NSGs
 If you have an existing on-premises infrastructure already configured with a suitable network appliance, you can deploy the reference architecture by following these steps:
 
 
-1. Right-click the button below and select either "Open link in new tab" or "Open link in new window":  
-   [![Deploy to Azure](./media/blueprints/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fmspnp%2Freference-architectures%2Fmaster%2Fguidance-hybrid-network-er%2Fazuredeploy.json)
+1. Open [this link](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fmspnp%2Freference-architectures%2Fmaster%2Fguidance-hybrid-network-er%2Fazuredeploy.json) in a new tab or browser window. The link takes you to the Azure Portal.
 2. Wait for the link to open in the Azure portal, then follow these steps:
 
    * The **Resource group** name is already defined in the parameter file, so select **Create New** and enter `ra-hybrid-er-rg` in the text box.
@@ -281,8 +280,7 @@ If you have an existing on-premises infrastructure already configured with a sui
    * Review the terms and conditions, then click the **I agree to the terms and conditions stated above** checkbox.
    * Click the **Purchase** button.
 3. Wait for the deployment to complete.
-4. Right-click the button below and select either "Open link in new tab" or "Open link in new window":  
-   [![Deploy to Azure](./media/blueprints/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fmspnp%2Freference-architectures%2Fmaster%2Fguidance-hybrid-network-er%2Fazuredeploy-expressRouteCircuit.json)
+4. Open [this link](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fmspnp%2Freference-architectures%2Fmaster%2Fguidance-hybrid-network-er%2Fazuredeploy-expressRouteCircuit.json) in a new tab or browser window. 
 5. Wait for the link to open in the Azure portal, then follow these steps:
 
    * Select **Use existing** in the **Resource group** section and enter `ra-hybrid-er-rg` in the text box.

articles/guidance/guidance-hybrid-network-vpn.md

@@ -468,8 +468,7 @@ The following recommendations are useful for determining if there is an issue wi
 ## Solution deployment
 If you have an existing on-premises infrastructure already configured with a VPN appliance, you can deploy the reference architecture by following these steps:
 
-1. Right-click the button below and select either "Open link in new tab" or "Open link in new window":  
-   [![Deploy to Azure](./media/blueprints/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fmspnp%2Freference-architectures%2Fmaster%2Fguidance-hybrid-network-vpn%2Fazuredeploy.json)
+1. Open [this link](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fmspnp%2Freference-architectures%2Fmaster%2Fguidance-hybrid-network-vpn%2Fazuredeploy.json) in a new tab or browser window. The link takes you to the Azure Portal. 
 2. Wait for the link to open in the Azure portal, then follow these steps: 
 
    * The **Resource group** name is already defined in the parameter file, so select **Create New** and enter `ra-hybrid-vpn-rg` in the text box.

articles/guidance/guidance-iaas-ra-secure-vnet-dmz.md

@@ -44,7 +44,7 @@ The following diagram highlights the important components in this architecture:
 > 
 > 
 
-[![0]][0] 
+![[0]][0] 
 
 To enable Internet traffic to Azure, the architecture includes the following components:
 
@@ -98,8 +98,7 @@ You should log all incoming requests on all ports. Regularly audit the logs, pay
 
 A deployment for a reference architecture that implements these recommendations is available on [GitHub][github-folder]. The reference architecture can be deployed either with Windows or Linux VMs by following the directions below:
 
-1. Right-click the button below and select either "Open link in new tab" or "Open link in new window":  
-   [![Deploy to Azure](./media/blueprints/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fmspnp%2Freference-architectures%2Fmaster%2Fguidance-hybrid-network-secure-vnet-dmz%2FvirtualNetwork.azuredeploy.json)
+1. Open [this link](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fmspnp%2Freference-architectures%2Fmaster%2Fguidance-hybrid-network-secure-vnet-dmz%2FvirtualNetwork.azuredeploy.json) in a new tab or browser window. The link takes you to the Azure Portal.
 2. Once the link has opened in the Azure portal, you must enter values for some of the settings:
 
    * The **Resource group** name is already defined in the parameter file, so select **Create New** and enter `ra-public-dmz-network-rg` in the text box.
@@ -109,8 +108,7 @@ A deployment for a reference architecture that implements these recommendations
    * Review the terms and conditions, then click the **I agree to the terms and conditions stated above** checkbox.
    * Click the **Purchase** button.
 3. Wait for the deployment to complete.
-4. Right-click the button below and select either "Open link in new tab" or "Open link in new window":  
-   [![Deploy to Azure](./media/blueprints/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fmspnp%2Freference-architectures%2Fmaster%2Fguidance-hybrid-network-secure-vnet-dmz%2Fworkload.azuredeploy.json)
+4. Open [this link](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fmspnp%2Freference-architectures%2Fmaster%2Fguidance-hybrid-network-secure-vnet-dmz%2Fworkload.azuredeploy.json) in a new tab or browser window.
 5. Once the link has opened in the Azure portal, you must enter values for some of the settings:
 
    * The **Resource group** name is already defined in the parameter file, so select **Create New** and enter `ra-public-dmz-wl-rg` in the text box.
@@ -119,8 +117,7 @@ A deployment for a reference architecture that implements these recommendations
    * Review the terms and conditions, then click the **I agree to the terms and conditions stated above** checkbox.
    * Click the **Purchase** button.
 6. Wait for the deployment to complete.
-7. Right-click the button below and select either "Open link in new tab" or "Open link in new window":  
-   [![Deploy to Azure](./media/blueprints/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fmspnp%2Freference-architectures%2Fmaster%2Fguidance-hybrid-network-secure-vnet-dmz%2Fsecurity.azuredeploy.json)
+7. Open [this link](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fmspnp%2Freference-architectures%2Fmaster%2Fguidance-hybrid-network-secure-vnet-dmz%2Fsecurity.azuredeploy.json) in a new tab or browser window. 
 8. Once the link has opened in the Azure portal, you must enter values for some of the settings:
 
    * The **Resource group** name is already defined in the parameter file, so select **Use Existing** and enter `ra-public-dmz-network-rg` in the text box.

articles/guidance/guidance-iaas-ra-secure-vnet-hybrid.md

@@ -43,7 +43,7 @@ The following diagram highlights the important components in this architecture:
 > 
 > 
 
-[![0]][0] 
+![[0]][0] 
 
 * **On-premises network**. A  private local-area network implemented in an organization.
 * **Azure virtual network (VNet)**. The VNet hosts the application and other resources running in Azure.
@@ -184,8 +184,7 @@ Use [RBAC][rbac] to restrict the operations that DevOps can perform on each tier
 
 A deployment for a reference architecture that implements these recommendations is available on [GitHub][github-folder]. The reference architecture can be deployed by following the directions below:
 
-1. Right-click the button below and select either "Open link in new tab" or "Open link in new window":  
-   [![Deploy to Azure](./media/blueprints/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fmspnp%2Freference-architectures%2Fmaster%2Fguidance-hybrid-network-secure-vnet%2Fazuredeploy.json)
+1. Open [this link](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fmspnp%2Freference-architectures%2Fmaster%2Fguidance-hybrid-network-secure-vnet%2Fazuredeploy.json) in a new tab or browser window. The link takes you to the Azure Portal. 
 2. Once the link has opened in the Azure portal, you must enter values for some of the settings:   
    * The **Resource group** name is already defined in the parameter file, so select **Create New** and enter `ra-private-dmz-rg` in the text box.
    * Select the region from the **Location** drop down box.

articles/guidance/guidance-identity-aad.md

@@ -60,7 +60,7 @@ The following diagram highlights the important components in this architecture.
 >
 >
 
-[![0]][0]
+![[0]][0]
 
 > [!NOTE]
 > For simplicity, this diagram only shows the connections directly related to Azure AD, and does not show protocol-related traffic that may occur as part of authentication and identity federation. For example, a web application may redirect the web browser to authenticate the request through Azure AD. Once authenticated, the request can be passed back to the web application, with the appropriate identity information.
@@ -242,8 +242,7 @@ For more information, see [Azure Active Directory conditional access][aad-condit
 
 A deployment for a reference architecture that implements these recommendations and considerations is available on GitHub. This reference architecture deploys a simulated on-premise network in Azure that you can use to test and experiment. The reference architecture can be deployed with either with Windows or Linux VMs by following the directions below:
 
-1. Right-click the button below and select either "Open link in new tab" or "Open link in new window":  
-   [![Deploy to Azure](./media/blueprints/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fmspnp%2Freference-architectures%2Fmaster%2Fguidance-identity-aad%2Fazuredeploy.json)
+1. Open [this link](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fmspnp%2Freference-architectures%2Fmaster%2Fguidance-identity-aad%2Fazuredeploy.json) in a new tab or browser window. The link takes you to the Azure Portal. 
 2. Once the link has opened in the Azure portal, you must enter values for some of the settings:
 
    * The **Resource group** name is already defined in the parameter file, so select **Create New** and enter `ra-aad-onpremise-rg` in the text box.

articles/guidance/guidance-identity-adds-extend-domain.md

@@ -50,7 +50,7 @@ The following diagram highlights the important components in this architecture.
 > 
 > 
 
-[![0]][0] 
+![[0]][0] 
 
 * **On-premises network**. The on-premises network includes local Active Directory servers that can perform authentication and authorization for components located on-premises.
 * **Active Directory servers**. These are domain controllers implementing directory services (AD DS) running as VMs in the cloud. These servers can provide authentication of components running in your Azure virtual network.

articles/guidance/guidance-identity-adds-resource-forest.md

@@ -45,7 +45,7 @@ The following diagram highlights the important components in this architecture.
 > 
 > 
 
-[![0]][0] 
+![[0]][0] 
 
 * **On-premises network**. The on-premises network contains its own Active Directory forest and domains.
 * **Active Directory servers**. These are domain controllers implementing domain services running as VMs in the cloud. These servers host a forest containing one or more domains, separate from those located on-premises.

articles/guidance/guidance-identity-adfs.md

@@ -54,7 +54,7 @@ The diagram shows the following scenarios:
 > 
 > 
 
-[![0]][0]
+![[0]][0]
 
 * **AD DS subnet**. The AD DS servers are contained in their own subnet with network security group (NSG) rules acting as a firewall.