Merge pull request #96774 from DCtheGeek/dmc-gov-mvccomp4

Updates for Blueprints MVC compliance

Author: TedA-M

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

@@ -1,7 +1,7 @@
 ---
 title: "Quickstart: Create a blueprint in the portal"
 description: In this quickstart, you use Azure Blueprints to create, define, and deploy artifacts through the Azure portal.
-ms.date: 03/11/2019
+ms.date: 11/21/2019
 ms.topic: quickstart
 ---
 # Quickstart: Define and assign a blueprint in the portal
@@ -11,13 +11,7 @@ reusable and rapidly deployable configurations based on Azure Resource Manager t
 security, and more. In this tutorial, you learn to use Azure Blueprints to do some of the common
 tasks related to creating, publishing, and assigning a blueprint within your organization. These tasks include:
 
-> [!div class="checklist"]
-> - Create a new blueprint and add various supported artifacts
-> - Make changes to an existing blueprint still in **Draft**
-> - Mark a blueprint as ready to assign with **Published**
-> - Assign a blueprint to an existing subscription
-> - Check the status and progress of an assigned blueprint
-> - Remove a blueprint that has been assigned to a subscription
+## Prerequisites
 
 If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free)
 before you begin.
@@ -364,9 +358,8 @@ blueprint assignment, follow these steps:
 
 ## Next steps
 
-- Learn about the [blueprint lifecycle](./concepts/lifecycle.md).
-- Understand how to use [static and dynamic parameters](./concepts/parameters.md).
-- Learn to customize the [blueprint sequencing order](./concepts/sequencing-order.md).
-- Find out how to make use of [blueprint resource locking](./concepts/resource-locking.md).
-- Learn how to [update existing assignments](./how-to/update-existing-assignments.md).
-- Resolve issues during the assignment of a blueprint with [general troubleshooting](./troubleshoot/general.md).
+In this quickstart, you've created, assigned, and removed a blueprint with Azure portal. To learn
+more about Azure Blueprints, continue to the blueprint lifecycle article.
+
+> [!div class="nextstepaction"]
+> [Learn about the blueprint lifecycle](./concepts/lifecycle.md)

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

@@ -1,7 +1,7 @@
 ---
 title: "Quickstart: Create a blueprint with PowerShell"
 description: In this quickstart, you use Azure Blueprints to create, define, and deploy artifacts using the PowerShell.
-ms.date: 08/21/2019
+ms.date: 11/21/2019
 ms.topic: quickstart
 ---
 # Quickstart: Define and Assign an Azure Blueprint with PowerShell
@@ -11,20 +11,16 @@ reusable and rapidly deployable configurations based on Resource Manager templat
 security, and more. In this tutorial, you learn to use Azure Blueprints to do some of the common
 tasks related to creating, publishing, and assigning a blueprint within your organization, such as:
 
-> [!div class="checklist"]
-> - Create a new blueprint and add various supported artifacts
-> - Make changes to an existing blueprint still in **Draft**
-> - Mark a blueprint as ready to assign with **Published**
-> - Assign a blueprint to an existing subscription
-> - Check the status and progress of an assigned blueprint
-> - Remove a blueprint that has been assigned to a subscription
+## Prerequisites
 
-If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free) before you begin.
+If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free)
+before you begin.
 
-## Prerequisites
+If it isn't already installed, follow the instructions in
+[Add the Az.Blueprint module](./how-to/manage-assignments-ps.md#add-the-azblueprint-module) to
+install and validate the **Az.Blueprint** module from the PowerShell Gallery.
 
-If it isn't already installed, follow the instructions in [Add the Az.Blueprint module](./how-to/manage-assignments-ps.md#add-the-azblueprint-module)
-to install and validate the **Az.Blueprint** module from the PowerShell Gallery.
+[!INCLUDE [cloud-shell-try-it.md](../../../includes/cloud-shell-try-it.md)]
 
 ## Create a blueprint
 
@@ -113,7 +109,8 @@ a role assignment on the resource group.
 
      > [!NOTE]
      > Use the filename _blueprint.json_ when creating your blueprint definitions programmatically.
-     > This file name is used when calling [Import-AzBlueprintWithArtifact](/powershell/module/az.blueprint/import-azblueprintwithartifact).
+     > This file name is used when calling
+     > [Import-AzBlueprintWithArtifact](/powershell/module/az.blueprint/import-azblueprintwithartifact).
 
      The blueprint object is created in the default subscription by default. To specify the
      management group, use parameter **ManagementGroupId**. To specify the subscription, use
@@ -445,9 +442,8 @@ Remove-AzBlueprintAssignment -Name 'assignMyBlueprint'
 
 ## Next steps
 
-- Learn about the [blueprint lifecycle](./concepts/lifecycle.md).
-- Understand how to use [static and dynamic parameters](./concepts/parameters.md).
-- Learn to customize the [blueprint sequencing order](./concepts/sequencing-order.md).
-- Find out how to make use of [blueprint resource locking](./concepts/resource-locking.md).
-- Learn how to [update existing assignments](./how-to/update-existing-assignments.md).
-- Resolve issues during the assignment of a blueprint with [general troubleshooting](./troubleshoot/general.md).
+In this quickstart, you've created, assigned, and removed a blueprint with PowerShell. To learn more
+about Azure Blueprints, continue to the blueprint lifecycle article.
+
+> [!div class="nextstepaction"]
+> [Learn about the blueprint lifecycle](./concepts/lifecycle.md)

articles/governance/blueprints/create-blueprint-rest-api.md

@@ -1,7 +1,7 @@
 ---
 title: "Quickstart: Create a blueprint with REST API"
 description: In this quickstart, you use Azure Blueprints to create, define, and deploy artifacts using the REST API.
-ms.date: 02/04/2019
+ms.date: 11/21/2019
 ms.topic: quickstart
 ---
 # Quickstart: Define and Assign an Azure Blueprint with REST API
@@ -11,15 +11,12 @@ reusable and rapidly deployable configurations based on Resource Manager templat
 security, and more. In this tutorial, you learn to use Azure Blueprints to do some of the common
 tasks related to creating, publishing, and assigning a blueprint within your organization, such as:
 
-> [!div class="checklist"]
-> - Create a new blueprint and add various supported artifacts
-> - Make changes to an existing blueprint still in **Draft**
-> - Mark a blueprint as ready to assign with **Published**
-> - Assign a blueprint to an existing subscription
-> - Check the status and progress of an assigned blueprint
-> - Remove a blueprint that has been assigned to a subscription
+## Prerequisites
 
-If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free) before you begin.
+If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free)
+before you begin.
+
+[!INCLUDE [cloud-shell-try-it.md](../../../includes/cloud-shell-try-it.md)]
 
 ## Getting started with REST API
 
@@ -34,9 +31,9 @@ For the Blueprints specs, see [Azure Blueprints REST API](/rest/api/blueprints/)
 ### REST API and PowerShell
 
 If you don't already have a tool for making REST API calls, consider using PowerShell for these
-instructions. Following is a sample header for authenticating with Azure. Generate an
-authentication header, sometimes called a **Bearer token**, and provide the REST API URI to connect
-to with any parameters or a **Request Body**:
+instructions. Following is a sample header for authenticating with Azure. Generate an authentication
+header, sometimes called a **Bearer token**, and provide the REST API URI to connect to with any
+parameters or a **Request Body**:
 
 ```azurepowershell-interactive
 # Log in first with Connect-AzAccount if not using Cloud Shell
@@ -70,9 +67,11 @@ assignments for the subscription. Then we'll add a resource group, a Resource Ma
 a role assignment on the resource group.
 
 > [!NOTE]
-> When using the REST API, the _blueprint_ object is created first. For each _artifact_ to be added that has parameters, the parameters need to be defined in advance on the initial _blueprint_.
+> When using the REST API, the _blueprint_ object is created first. For each _artifact_ to be added
+> that has parameters, the parameters need to be defined in advance on the initial _blueprint_.
 
-In each REST API URI, there are variables that are used that you need to replace with your own values:
+In each REST API URI, there are variables that are used that you need to replace with your own
+values:
 
 - `{YourMG}` - Replace with the ID of your management group
 - `{subscriptionId}` - Replace with your subscription ID
@@ -82,8 +81,8 @@ In each REST API URI, there are variables that are used that you need to replace
 > [create blueprint at subscription example](/rest/api/blueprints/blueprints/createorupdate#subscriptionblueprint).
 
 1. Create the initial _blueprint_ object. The **Request Body** includes properties about the
-blueprint, any resource groups to create, and all of the blueprint level parameters. The parameters
-are set during assignment and used by the artifacts added in later steps.
+   blueprint, any resource groups to create, and all of the blueprint level parameters. The
+   parameters are set during assignment and used by the artifacts added in later steps.
 
    - REST API URI
 
@@ -143,10 +142,10 @@ are set during assignment and used by the artifacts added in later steps.
      ```
 
 1. Add role assignment at subscription. The **Request Body** defines the _kind_ of artifact, the
-properties align to the role definition identifier, and the principal identities are passed as an
-array of values. In the example below, the principal identities granted the specified role are
-configured to a parameter that is set during blueprint assignment. This example uses the
-_Contributor_ built-in role with a GUID of `b24988ac-6180-42a0-ab88-20f7382dd24c`.
+   properties align to the role definition identifier, and the principal identities are passed as an
+   array of values. In the example below, the principal identities granted the specified role are
+   configured to a parameter that is set during blueprint assignment. This example uses the
+   _Contributor_ built-in role with a GUID of `b24988ac-6180-42a0-ab88-20f7382dd24c`.
 
    - REST API URI
 
@@ -167,10 +166,10 @@ _Contributor_ built-in role with a GUID of `b24988ac-6180-42a0-ab88-20f7382dd24c
      ```
 
 1. Add policy assignment at subscription. The **Request Body** defines the _kind_ of artifact, the
-properties that align to a policy or initiative definition, and configures the policy assignment to
-use the defined blueprint parameters to configure during blueprint assignment. This example uses
-the _Apply tag and its default value to resource groups_ built-in policy with a GUID of
-`49c88fc8-6fd1-46fd-a676-f12d1d3a4c71`.
+   properties that align to a policy or initiative definition, and configures the policy assignment
+   to use the defined blueprint parameters to configure during blueprint assignment. This example
+   uses the _Apply tag and its default value to resource groups_ built-in policy with a GUID of
+   `49c88fc8-6fd1-46fd-a676-f12d1d3a4c71`.
 
    - REST API URI
 
@@ -199,11 +198,11 @@ the _Apply tag and its default value to resource groups_ built-in policy with a
      ```
 
 1. Add another policy assignment for Storage tag (reusing _storageAccountType_ parameter) at
-subscription. This additional policy assignment artifact demonstrates that a parameter defined on
-the blueprint is usable by more than one artifact. In the example, the **storageAccountType** is
-used to set a tag on the resource group. This value provides information about the storage account
-that is created in the next step. This example uses the _Apply tag and its default value to
-resource groups_ built-in policy with a GUID of `49c88fc8-6fd1-46fd-a676-f12d1d3a4c71`.
+   subscription. This additional policy assignment artifact demonstrates that a parameter defined on
+   the blueprint is usable by more than one artifact. In the example, the **storageAccountType** is
+   used to set a tag on the resource group. This value provides information about the storage
+   account that is created in the next step. This example uses the _Apply tag and its default value
+   to resource groups_ built-in policy with a GUID of `49c88fc8-6fd1-46fd-a676-f12d1d3a4c71`.
 
    - REST API URI
 
@@ -232,13 +231,13 @@ resource groups_ built-in policy with a GUID of `49c88fc8-6fd1-46fd-a676-f12d1d3
      ```
 
 1. Add template under resource group. The **Request Body** for a Resource Manager template includes
-the normal JSON component of the template and defines the target resource group with
-**properties.resourceGroup**. The template also reuses the **storageAccountType**, **tagName**, and
-**tagValue** blueprint parameters by passing each to the template. The blueprint parameters are
-available to the template by defining **properties.parameters** and inside the template JSON that
-key-value pair is used to inject the value. The blueprint and template parameter names could be the
-same, but were made different to illustrate how each passes from the blueprint to the template
-artifact.
+   the normal JSON component of the template and defines the target resource group with
+   **properties.resourceGroup**. The template also reuses the **storageAccountType**, **tagName**,
+   and **tagValue** blueprint parameters by passing each to the template. The blueprint parameters
+   are available to the template by defining **properties.parameters** and inside the template JSON
+   that key-value pair is used to inject the value. The blueprint and template parameter names could
+   be the same, but were made different to illustrate how each passes from the blueprint to the
+   template artifact.
 
    - REST API URI
 
@@ -325,9 +324,9 @@ artifact.
      ```
 
 1. Add role assignment under resource group. Similar to the previous role assignment entry, the
-example below uses the definition identifier for the **Owner** role and provides it a different
-parameter from the blueprint. This example uses the _Owner_ built-in role with a GUID of
-`8e3af657-a8ff-443c-a75c-2fe8c4bcb635`.
+   example below uses the definition identifier for the **Owner** role and provides it a different
+   parameter from the blueprint. This example uses the _Owner_ built-in role with a GUID of
+   `8e3af657-a8ff-443c-a75c-2fe8c4bcb635`.
 
    - REST API URI
 
@@ -372,21 +371,31 @@ Body** specifies the blueprint to assign, provides name and location to any reso
 blueprint definition, and provides all parameters defined on the blueprint and used by one or more
 attached artifacts.
 
-In each REST API URI, there are variables that are used that you need to replace with your own values:
+In each REST API URI, there are variables that are used that you need to replace with your own
+values:
 
 - `{tenantId}` - Replace with your tenant ID
 - `{YourMG}` - Replace with the ID of your management group
 - `{subscriptionId}` - Replace with your subscription ID
 
-1. Provide the Azure Blueprint service principal the **Owner** role on the target subscription. The AppId is static (`f71766dc-90d9-4b7d-bd9d-4499c4331c3f`), but the service principal ID varies by tenant. Details can be requested for your tenant using the following REST API. It uses [Azure Active Directory Graph API](../../active-directory/develop/active-directory-graph-api.md) which has different authorization.
+1. Provide the Azure Blueprint service principal the **Owner** role on the target subscription. The
+   AppId is static (`f71766dc-90d9-4b7d-bd9d-4499c4331c3f`), but the service principal ID varies by
+   tenant. Details can be requested for your tenant using the following REST API. It uses
+   [Azure Active Directory Graph API](../../active-directory/develop/active-directory-graph-api.md)
+   which has different authorization.
 
    - REST API URI
 
      ```http
      GET https://graph.windows.net/{tenantId}/servicePrincipals?api-version=1.6&$filter=appId eq 'f71766dc-90d9-4b7d-bd9d-4499c4331c3f'
      ```
 
-1. Run the blueprint deployment by assigning it to a subscription. As the **contributors** and **owners** parameters require an array of objectIds of the principals to be granted the role assignment, use [Azure Active Directory Graph API](../../active-directory/develop/active-directory-graph-api.md) for gathering the objectIds for use in the **Request Body** for your own users, groups, or service principals.
+1. Run the blueprint deployment by assigning it to a subscription. As the **contributors** and
+   **owners** parameters require an array of objectIds of the principals to be granted the role
+   assignment, use
+   [Azure Active Directory Graph API](../../active-directory/develop/active-directory-graph-api.md)
+   for gathering the objectIds for use in the **Request Body** for your own users, groups, or
+   service principals.
 
    - REST API URI
 
@@ -439,7 +448,11 @@ In each REST API URI, there are variables that are used that you need to replace
 
    - User-assigned managed identity
 
-     A blueprint assignment can also use a [user-assigned managed identity](../../active-directory/managed-identities-azure-resources/overview.md). In this case, the **identity** portion of the request body changes as follows.  Replace `{yourRG}` and `{userIdentity}` with your resource group name and the name of your user-assigned managed identity, respectively.
+     A blueprint assignment can also use a
+     [user-assigned managed identity](../../active-directory/managed-identities-azure-resources/overview.md).
+     In this case, the **identity** portion of the request body changes as follows. Replace
+     `{yourRG}` and `{userIdentity}` with your resource group name and the name of your
+     user-assigned managed identity, respectively.
 
      ```json
      "identity": {
@@ -455,8 +468,8 @@ In each REST API URI, there are variables that are used that you need to replace
      assigning the blueprint has permissions to.
 
      > [!IMPORTANT]
-     > Blueprints doesn't manage the user-assigned managed identity. Users are responsible for assigning
-     > sufficient roles and permissions or the blueprint assignment will fail.
+     > Blueprints doesn't manage the user-assigned managed identity. Users are responsible for
+     > assigning sufficient roles and permissions or the blueprint assignment will fail.
 
 ## Unassign a blueprint
 
@@ -482,9 +495,8 @@ To remove the blueprint itself, use the following REST API operation:
 
 ## Next steps
 
-- Learn about the [blueprint lifecycle](./concepts/lifecycle.md).
-- Understand how to use [static and dynamic parameters](./concepts/parameters.md).
-- Learn to customize the [blueprint sequencing order](./concepts/sequencing-order.md).
-- Find out how to make use of [blueprint resource locking](./concepts/resource-locking.md).
-- Learn how to [update existing assignments](./how-to/update-existing-assignments.md).
-- Resolve issues during the assignment of a blueprint with [general troubleshooting](./troubleshoot/general.md).
+In this quickstart, you've created, assigned, and removed a blueprint with REST API. To learn more
+about Azure Blueprints, continue to the blueprint lifecycle article.
+
+> [!div class="nextstepaction"]
+> [Learn about the blueprint lifecycle](./concepts/lifecycle.md)