Merge pull request #111061 from DCtheGeek/dmc-bp-images

Full review, reflow, and platform adjustments

Author: v-albemi

articles/governance/blueprints/concepts/parameters.md

@@ -1,15 +1,15 @@
 ---
 title: Use parameters to creating dynamic blueprints
 description: Learn about static and dynamic parameters and how to use them to create secure and dynamic blueprints.
-ms.date: 03/12/2019
+ms.date: 04/15/2020
 ms.topic: conceptual
 ---
 # Creating dynamic blueprints through parameters
 
 A fully defined blueprint with various artifacts (such as resource groups, Resource Manager
 templates, policies, or role assignments) offers the rapid creation and consistent creation of
-objects within Azure. To enable flexible use of these reusable design patterns and containers,
-Azure Blueprints supports parameters. The parameter creates flexibility, both during definition and
+objects within Azure. To enable flexible use of these reusable design patterns and containers, Azure
+Blueprints supports parameters. The parameter creates flexibility, both during definition and
 assignment, to change properties on the artifacts deployed by the blueprint.
 
 A simple example is the resource group artifact. When a resource group is created, it has two
@@ -32,22 +32,21 @@ without having conflict.
 ## Blueprint parameters
 
 Through the REST API, parameters can be created on the blueprint itself. These parameters are
-different than the parameters on each of the supported artifacts. When a parameter is created on
-the blueprint, it can be used by the artifacts in that blueprint. An example might be the prefix
-for naming of the resource group. The artifact can use the blueprint parameter to create a "mostly
-dynamic" parameter. As the parameter can also be defined during assignment, this pattern allows
-for a consistency that may adhere to naming rules. For steps, see [setting static parameters -
-blueprint level parameter](#blueprint-level-parameter).
+different than the parameters on each of the supported artifacts. When a parameter is created on the
+blueprint, it can be used by the artifacts in that blueprint. An example might be the prefix for
+naming of the resource group. The artifact can use the blueprint parameter to create a "mostly
+dynamic" parameter. As the parameter can also be defined during assignment, this pattern allows for
+a consistency that may adhere to naming rules. For steps, see [setting static parameters - blueprint
+level parameter](#blueprint-level-parameter).
 
 ### Using secureString and secureObject parameters
 
 While a Resource Manager template _artifact_ supports parameters of the **secureString** and
-**secureObject** types, Azure Blueprints requires each to be connected with an Azure Key Vault.
-This security measure prevents the unsafe practice of storing secrets along with the Blueprint and
-encourages employment of secure patterns. Azure Blueprints supports this security measure,
-detecting the inclusion of either secure parameter in a Resource Manager template _artifact_. The
-service then prompts during assignment for the following Key Vault properties per detected secure
-parameter:
+**secureObject** types, Azure Blueprints requires each to be connected with an Azure Key Vault. This
+security measure prevents the unsafe practice of storing secrets along with the Blueprint and
+encourages employment of secure patterns. Azure Blueprints supports this security measure, detecting
+the inclusion of either secure parameter in a Resource Manager template _artifact_. The service then
+prompts during assignment for the following Key Vault properties per detected secure parameter:
 
 - Key Vault resource ID
 - Key Vault secret name
@@ -73,30 +72,36 @@ Overview](../../../key-vault/key-vault-overview.md).
 
 ### Static parameters
 
-A parameter value defined in the definition of a blueprint is called a **static parameter**,
-because every use of the blueprint will deploy the artifact using that static value. In the
-resource group example, while it doesn't make sense for the name of the resource group, it might
-make sense for the location. Then, every assignment of the blueprint would create the resource
-group, whatever it's called during assignment, in the same location. This flexibility allows you to
-be selective in what you define as required vs what can be changed during assignment.
+A parameter value defined in the definition of a blueprint is called a **static parameter**, because
+every use of the blueprint will deploy the artifact using that static value. In the resource group
+example, while it doesn't make sense for the name of the resource group, it might make sense for the
+location. Then, every assignment of the blueprint would create the resource group, whatever it's
+called during assignment, in the same location. This flexibility allows you to be selective in what
+you define as required vs what can be changed during assignment.
 
 #### Setting static parameters in the portal
 
 1. Select **All services** in the left pane. Search for and select **Blueprints**.
 
 1. Select **Blueprint definitions** from the page on the left.
 
-1. Click on an existing blueprint and then click **Edit blueprint** OR click **+ Create blueprint** and fill out the information on the **Basics** tab.
+1. Click on an existing blueprint and then click **Edit blueprint** OR click **+ Create blueprint**
+   and fill out the information on the **Basics** tab.
 
 1. Click **Next: Artifacts** OR click on the **Artifacts** tab.
 
-1. Artifacts added to the blueprint that have parameter options display **X of Y parameters populated** in the **Parameters** column. Click on the artifact row to edit the artifact parameters.
+1. Artifacts added to the blueprint that have parameter options display **X of Y parameters
+   populated** in the **Parameters** column. Click on the artifact row to edit the artifact
+   parameters.
 
-   ![Blueprint parameters on a blueprint definition](../media/parameters/parameter-column.png)
+   :::image type="content" source="../media/parameters/parameter-column.png" alt-text="Blueprint parameters on a blueprint definition" border="false":::
 
-1. The **Edit Artifact** page displays value options appropriate to the artifact clicked on. Each parameter on the artifact has a title, a value box, and a checkbox. Set the box to unchecked to make it a **static parameter**. In the example below, only _Location_ is a **static parameter** as it's unchecked and _Resource Group Name_ is checked.
+1. The **Edit Artifact** page displays value options appropriate to the artifact clicked on. Each
+   parameter on the artifact has a title, a value box, and a checkbox. Set the box to unchecked to
+   make it a **static parameter**. In the example below, only _Location_ is a **static parameter**
+   as it's unchecked and _Resource Group Name_ is checked.
 
-   ![Blueprint static parameters on a blueprint artifact](../media/parameters/static-parameter.png)
+   :::image type="content" source="../media/parameters/static-parameter.png" alt-text="Blueprint static parameters on a blueprint artifact" border="false":::
 
 #### Setting static parameters from REST API
 
@@ -205,20 +210,24 @@ and **tagValue**. The value on each is directly provided and doesn't use a funct
 The opposite of a static parameter is a **dynamic parameter**. This parameter isn't defined on the
 blueprint, but instead is defined during each assignment of the blueprint. In the resource group
 example, use of a **dynamic parameter** makes sense for the resource group name. It provides a
-different name for every assignment of the blueprint. For a list of blueprint functions, see the [blueprint functions](../reference/blueprint-functions.md)
-reference.
+different name for every assignment of the blueprint. For a list of blueprint functions, see the
+[blueprint functions](../reference/blueprint-functions.md) reference.
 
 #### Setting dynamic parameters in the portal
 
 1. Select **All services** in the left pane. Search for and select **Blueprints**.
 
 1. Select **Blueprint definitions** from the page on the left.
 
-1. Right-click on the blueprint that you want to assign. Select **Assign blueprint** OR click on the blueprint you want to assign, then click the **Assign blueprint** button.
+1. Right-click on the blueprint that you want to assign. Select **Assign blueprint** OR click on the
+   blueprint you want to assign, then click the **Assign blueprint** button.
 
-1. On the **Assign blueprint** page, find the **Artifact parameters** section. Each artifact with at least one **dynamic parameter** displays the artifact and the configuration options. Provide required values to the parameters before assigning the blueprint. In the example below, _Name_ is a **dynamic parameter** that must be defined to complete blueprint assignment.
+1. On the **Assign blueprint** page, find the **Artifact parameters** section. Each artifact with at
+   least one **dynamic parameter** displays the artifact and the configuration options. Provide
+   required values to the parameters before assigning the blueprint. In the example below, _Name_ is
+   a **dynamic parameter** that must be defined to complete blueprint assignment.
 
-   ![Blueprint dynamic parameter during blueprint assignment](../media/parameters/dynamic-parameter.png)
+   :::image type="content" source="../media/parameters/dynamic-parameter.png" alt-text="Blueprint dynamic parameter during blueprint assignment" border="false":::
 
 #### Setting dynamic parameters from REST API
 

articles/governance/blueprints/concepts/resource-locking.md

@@ -128,7 +128,7 @@ blueprint assignment and can only be removed from the artifact resources by the
 identity. This security measure enforces the locking mechanism and prevents removing the blueprint
 lock outside Azure Blueprints.
 
-![Blueprint deny assignment on resource group](../media/resource-locking/blueprint-deny-assignment.png)
+:::image type="content" source="../media/resource-locking/blueprint-deny-assignment.png" alt-text="Blueprint deny assignment on resource group" border="false":::
 
 The
 [deny assignment properties](../../../role-based-access-control/deny-assignments.md#deny-assignment-properties)

articles/governance/blueprints/create-blueprint-portal.md

@@ -31,7 +31,7 @@ Manager template and role assignment on the new resource group.
 
    Or, select **Create** from the **Getting started** page to go straight to creating a blueprint.
 
-   ![Create a blueprint from the Blueprint definitions page](./media/create-blueprint-portal/create-blueprint-button.png)
+   :::image type="content" source="./media/create-blueprint-portal/create-blueprint-button.png" alt-text="Create a blueprint from the Blueprint definitions page" border="false":::
 
 1. Select **Start with blank blueprint** from the card at the top of the built-in blueprints list.
 
@@ -59,12 +59,13 @@ Manager template and role assignment on the new resource group.
 
    1. Select **Add** to add this artifact to the blueprint.
 
-   ![Role assignment for a blueprint artifact](./media/create-blueprint-portal/add-role-assignment.png)
+   :::image type="content" source="./media/create-blueprint-portal/add-role-assignment.png" alt-text="Role assignment for a blueprint artifact" border="false":::
 
    > [!NOTE]
    > Most artifacts support parameters. A parameter that's assigned a value during blueprint
-   > creation is a *static parameter*. If the parameter is assigned during blueprint assignment,
-   > it's a *dynamic parameter*. For more information, see [Blueprint parameters](./concepts/parameters.md).
+   > creation is a _static parameter_. If the parameter is assigned during blueprint assignment,
+   > it's a _dynamic parameter_. For more information, see
+   > [Blueprint parameters](./concepts/parameters.md).
 
 1. Add a policy assignment at the subscription level:
 
@@ -171,13 +172,13 @@ Manager template and role assignment on the new resource group.
 
    1. Select **Add** to add this artifact to the blueprint.
 
-   ![Resource Manager template for the blueprint artifact](./media/create-blueprint-portal/add-resource-manager-template.png)
+   :::image type="content" source="./media/create-blueprint-portal/add-resource-manager-template.png" alt-text="Resource Manager template for the blueprint artifact" border="false":::
 
 1. Your completed blueprint should look similar to the following. Notice that each artifact has
    **_x_ out of _y_ parameters populated** in the **Parameters** column. The dynamic parameters are
    set during each assignment of the blueprint.
 
-   ![Completed blueprint definition](./media/create-blueprint-portal/completed-blueprint.png)
+   :::image type="content" source="./media/create-blueprint-portal/completed-blueprint.png" alt-text="Completed blueprint definition" border="false":::
 
 1. Now that all planned artifacts have been added, select **Save Draft** at the bottom of the page.
 
@@ -211,14 +212,14 @@ assignment to the new resource group. You can fix both by following these steps:
    1. Search for and select a user, app, or group to add. This artifact uses a static parameter set
       the same in every assignment of this blueprint.
 
-   e. Select **Add** to add this artifact to the blueprint.
+   1. Select **Add** to add this artifact to the blueprint.
 
-   ![Second role assignment for the blueprint artifact](./media/create-blueprint-portal/add-role-assignment-2.png)
+   :::image type="content" source="./media/create-blueprint-portal/add-role-assignment-2.png" alt-text="Second role assignment for the blueprint artifact" border="false":::
 
 1. Your completed blueprint should look similar to the following. Notice that the newly added role
    assignment shows **1 out of 1 parameters populated**. That means it's a static parameter.
 
-   ![Second definition for the completed blueprint](./media/create-blueprint-portal/completed-blueprint-2.png)
+   :::image type="content" source="./media/create-blueprint-portal/completed-blueprint-2.png" alt-text="Second definition for the completed blueprint" border="false":::
 
 1. Select **Save Draft** now that it has been updated.
 
@@ -252,8 +253,9 @@ is saved to a subscription, it can only be assigned to that subscription.
 1. On the **Assign blueprint** page, in the **Subscription** drop-down list, select the
    subscriptions that you want to deploy this blueprint to.
 
-   If there are supported Enterprise offerings available from [Azure Billing](../../billing/index.md),
-   a **Create new** link is activated under the **Subscription** box. Follow these steps:
+   If there are supported Enterprise offerings available from
+   [Azure Billing](../../billing/index.md), a **Create new** link is activated under the
+   **Subscription** box. Follow these steps:
 
    1. Select the **Create new** link to create a new subscription instead of selecting existing
       ones.
@@ -267,10 +269,10 @@ is saved to a subscription, it can only be assigned to that subscription.
 
    1. Select **Create** at the bottom of the page.
 
-   ![Create a subscription for a blueprint assignment subscription](./media/create-blueprint-portal/assignment-create-subscription.png)
+      :::image type="content" source="./media/create-blueprint-portal/assignment-create-subscription.png" alt-text="Create a subscription for a blueprint assignment subscription" border="false":::
 
-   > [!IMPORTANT]
-   > The new subscription is created immediately after you select **Create**.
+      > [!IMPORTANT]
+      > The new subscription is created immediately after you select **Create**.
 
    > [!NOTE]
    > An assignment is created for each subscription that you select. You can make changes to a
@@ -287,9 +289,10 @@ is saved to a subscription, it can only be assigned to that subscription.
 1. Leave the **Blueprint definition version** drop-down selection of **Published** versions on the
    **v1** entry. (The default is the most recently published version.)
 
-1. For **Lock Assignment**, leave the default of **Don't Lock**. For more information, see [Blueprints resource locking](./concepts/resource-locking.md).
+1. For **Lock Assignment**, leave the default of **Don't Lock**. For more information, see
+   [Blueprints resource locking](./concepts/resource-locking.md).
 
-   ![Locking and managed identities for the assignment](./media/create-blueprint-portal/assignment-locking-mi.png)
+   :::image type="content" source="./media/create-blueprint-portal/assignment-locking-mi.png" alt-text="Locking and managed identities for the assignment" border="false":::
 
 1. Under **Managed Identity**, leave the default of **System assigned**.
 
@@ -327,7 +330,7 @@ Now that the blueprint has been assigned to a subscription, verify the progress
 1. In the list of blueprints, right-click the one that you previously assigned and select **View
    assignment details**.
 
-   ![View assignment details from the Assigned blueprints page](./media/create-blueprint-portal/view-assignment-details.png)
+   :::image type="content" source="./media/create-blueprint-portal/view-assignment-details.png" alt-text="View assignment details from the Assigned blueprints page" border="false":::
 
 1. On the **Blueprint assignment** page, validate that all artifacts were successfully deployed and
    that there were no errors during the deployment. If errors occurred, see [Troubleshooting blueprints](./troubleshoot/general.md)

articles/governance/blueprints/how-to/update-existing-assignments.md

@@ -1,7 +1,7 @@
 ---
 title: Update an existing assignment from the portal
 description: Learn about the mechanism for updating an existing blueprint assignment from the portal in Azure Blueprints.
-ms.date: 11/21/2019
+ms.date: 04/15/2020
 ms.topic: how-to
 ---
 # How to update an existing blueprint assignment
@@ -22,7 +22,7 @@ an existing assignment, including:
 1. In the list of blueprints, left-click the blueprint assignment. Then click the **Update
    assignment** button OR right-click the blueprint assignment and select **Update assignment**.
 
-   ![Update an existing blueprint assignment](../media/update-existing-assignments/update-assignment.png)
+   :::image type="content" source="../media/update-existing-assignments/update-assignment.png" alt-text="Update an existing blueprint assignment" border="false":::
 
 1. The **Assign blueprint** page will load pre-filled with all values from the original assignment.
    You can change the **blueprint definition version**, the **Lock Assignment** state, and any of
@@ -32,12 +32,12 @@ an existing assignment, including:
 1. On the updated assignment details page, see the new status. In this example, we added **Locking**
    to the assignment.
 
-   ![Updated an existing blueprint assignment - lock mode changed](../media/update-existing-assignments/updated-assignment.png)
+   :::image type="content" source="../media/update-existing-assignments/updated-assignment.png" alt-text="Updated an existing blueprint assignment - lock mode changed" border="false":::
 
 1. Explore details about other **Assignment operations** using the drop-down. The table of **Managed
    resources** updates by selected assignment operation.
 
-   ![Assignment operations of a blueprint assignment](../media/update-existing-assignments/assignment-operations.png)
+   :::image type="content" source="../media/update-existing-assignments/assignment-operations.png" alt-text="Assignment operations of a blueprint assignment" border="false":::
 
 ## Rules for updating assignments
 

articles/governance/blueprints/samples/caf-foundation/index.md

@@ -1,7 +1,7 @@
 ---
 title: CAF Foundation blueprint sample overview
 description: Overview and architecture of the Cloud Adoption Framework (CAF) for Azure Foundation blueprint sample.
-ms.date: 08/20/2019
+ms.date: 04/15/2020
 ms.topic: sample
 ---
 # Overview of the Microsoft Cloud Adoption Framework for Azure Foundation blueprint sample
@@ -17,7 +17,7 @@ be used by organizations to put in place the foundation controls necessary to ma
 estate. This sample will deploy and enforce resources, policies, and templates that will allow an
 organization to confidently get started with Azure.
 
-![CAF Foundation, image describes what gets installed as part of CAF guidance for creating a foundation to get started with Azure](../../media/caf-blueprints/caf-foundation-architecture.png)
+:::image type="content" source="../../media/caf-blueprints/caf-foundation-architecture.png" alt-text="CAF Foundation, image describes what gets installed as part of CAF guidance for creating a foundation to get started with Azure" border="false":::
 
 This implementation incorporates several Azure services used to provide a secure, fully monitored,
 enterprise-ready foundation. This environment is composed of: