Merge pull request #110345 from DCtheGeek/dmc-policy-ghpr51361

Addressing branding issues pointed out in #51361

Author: Jak-MS

articles/governance/blueprints/concepts/deployment-stages.md

@@ -11,24 +11,24 @@ deploy the resources defined in the blueprint. This article provides details abo
 involves.
 
 Blueprint deployment is triggered by assigning a blueprint to a subscription or [updating an
-existing assignment](../how-to/update-existing-assignments.md). During the deployment, Blueprints
-takes the following high-level steps:
+existing assignment](../how-to/update-existing-assignments.md). During the deployment, Azure
+Blueprints takes the following high-level steps:
 
 > [!div class="checklist"]
-> - Blueprints granted owner rights
+> - Azure Blueprints granted owner rights
 > - The blueprint assignment object is created
-> - Optional - Blueprints creates **system-assigned** managed identity
+> - Optional - Azure Blueprints creates **system-assigned** managed identity
 > - The managed identity deploys blueprint artifacts
-> - Blueprint service and **system-assigned** managed identity rights are revoked
+> - Azure Blueprints service and **system-assigned** managed identity rights are revoked
 
-## Blueprints granted owner rights
+## Azure Blueprints granted owner rights
 
 The Azure Blueprints service principal is granted owner rights to the assigned subscription or
 subscriptions when a [system-assigned managed
 identity](../../../active-directory/managed-identities-azure-resources/overview.md) managed identity
-is used. The granted role allows Blueprints to create, and later revoke, the **system-assigned**
-managed identity. If using a **user-assigned** managed identity, the Azure Blueprints service
-principal doesn't get and doesn't need owner rights on the subscription.
+is used. The granted role allows Azure Blueprints to create, and later revoke, the
+**system-assigned** managed identity. If using a **user-assigned** managed identity, the Azure
+Blueprints service principal doesn't get and doesn't need owner rights on the subscription.
 
 The rights are granted automatically if the assignment is done through the portal. However, if the
 assignment is done through the REST API, granting the rights needs to be done with a separate API
@@ -43,7 +43,7 @@ principal. Then, grant the Azure Blueprints the _Owner_ role through the
 [REST API](../../../role-based-access-control/role-assignments-rest.md), or a
 [Resource Manager template](../../../role-based-access-control/role-assignments-template.md).
 
-The Blueprints service doesn't directly deploy the resources.
+The Azure Blueprints service doesn't directly deploy the resources.
 
 ## The blueprint assignment object is created
 
@@ -61,14 +61,14 @@ before the blueprint assignment is created. Both the
 built-in roles have the necessary `blueprintAssignment/write` permission to create an assignment
 that uses a **user-assigned** managed identity.
 
-## Optional - Blueprints creates system-assigned managed identity
+## Optional - Azure Blueprints creates system-assigned managed identity
 
 When [system-assigned managed
 identity](../../../active-directory/managed-identities-azure-resources/overview.md) is selected
-during assignment, Blueprints creates the identity and grants the managed identity the
+during assignment, Azure Blueprints creates the identity and grants the managed identity the
 [owner](../../../role-based-access-control/built-in-roles.md#owner) role. If an
-[existing assignment is upgraded](../how-to/update-existing-assignments.md), Blueprints uses the
-previously created managed identity.
+[existing assignment is upgraded](../how-to/update-existing-assignments.md), Azure Blueprints uses
+the previously created managed identity.
 
 The managed identity related to the blueprint assignment is used to deploy or redeploy the resources
 defined in the blueprint. This design avoids assignments inadvertently interfering with each other.
@@ -82,15 +82,16 @@ blueprint in the defined [sequencing order](./sequencing-order.md). The order ca
 ensure artifacts dependent on other artifacts are deployed in the correct order.
 
 An access failure by a deployment is often the result of the level of access granted to the managed
-identity. The Blueprints service manages the security lifecycle of the **system-assigned** managed
-identity. However, the user is responsible for managing the rights and lifecycle of a
+identity. The Azure Blueprints service manages the security lifecycle of the **system-assigned**
+managed identity. However, the user is responsible for managing the rights and lifecycle of a
 **user-assigned** managed identity.
 
 ## Blueprint service and system-assigned managed identity rights are revoked
 
-Once the deployments are completed, Blueprints revokes the rights of the **system-assigned** managed
-identity from the subscription. Then, the Blueprints service revokes its rights from the
-subscription. Rights removal prevents Blueprints from becoming a permanent owner on a subscription.
+Once the deployments are completed, Azure Blueprints revokes the rights of the **system-assigned**
+managed identity from the subscription. Then, the Azure Blueprints service revokes its rights from
+the subscription. Rights removal prevents Azure Blueprints from becoming a permanent owner on a
+subscription.
 
 ## Next steps
 

articles/governance/blueprints/concepts/lifecycle.md

@@ -7,7 +7,7 @@ ms.topic: conceptual
 # Understand the lifecycle of an Azure Blueprint
 
 Like many resources within Azure, a blueprint in Azure Blueprints has a typical and natural
-lifecycle. They're created, deployed, and finally deleted when no longer needed or relevant.
+lifecycle. They're created, deployed, and finally deleted when no longer needed or relevant. Azure
 Blueprints supports standard lifecycle operations. It then builds upon them to provide additional
 levels of status that support common continuous integration and continuous deployment pipelines for
 organizations that manage their Infrastructure as Code – a key element in DevOps.

articles/governance/blueprints/concepts/parameters.md

@@ -24,7 +24,7 @@ resource group. Resources inside that resource group would become duplicated and
 > related artifacts in that resource group. This could cause a conflict as two resources with the
 > same name and resource type cannot exist within a subscription.
 
-The solution to this problem is parameters. Blueprints allows you to define the value for each
+The solution to this problem is parameters. Azure Blueprints allows you to define the value for each
 property of the artifact during assignment to a subscription. The parameter makes it possible to
 reuse a blueprint that creates a resource group and other resources within a single subscription
 without having conflict.

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

@@ -21,15 +21,15 @@ see an example of resource locking and application of _deny assignments_, see th
 Locking Mode applies to the blueprint assignment and it has three options: **Don't Lock**, **Read
 Only**, or **Do Not Delete**. The locking mode is configured during artifact deployment during a
 blueprint assignment. A different locking mode can be set by updating the blueprint assignment.
-Locking modes, however, can't be changed outside of Blueprints.
+Locking modes, however, can't be changed outside of Azure Blueprints.
 
 Resources created by artifacts in a blueprint assignment have four states: **Not Locked**, **Read
 Only**, **Cannot Edit / Delete**, or **Cannot Delete**. Each artifact type can be in the **Not
 Locked** state. The following table can be used to determine the state of a resource:
 
 |Mode|Artifact Resource Type|State|Description|
 |-|-|-|-|
-|Don't Lock|*|Not Locked|Resources aren't protected by Blueprints. This state is also used for resources added to a **Read Only** or **Do Not Delete** resource group artifact from outside a blueprint assignment.|
+|Don't Lock|*|Not Locked|Resources aren't protected by Azure Blueprints. This state is also used for resources added to a **Read Only** or **Do Not Delete** resource group artifact from outside a blueprint assignment.|
 |Read Only|Resource group|Cannot Edit / Delete|The resource group is read only and tags on the resource group can't be modified. **Not Locked** resources can be added, moved, changed, or deleted from this resource group.|
 |Read Only|Non-resource group|Read Only|The resource can't be altered in any way -- no changes and it can't be deleted.|
 |Do Not Delete|*|Cannot Delete|The resources can be altered, but can't be deleted. **Not Locked** resources can be added, moved, changed, or deleted from this resource group.|
@@ -38,7 +38,7 @@ Locked** state. The following table can be used to determine the state of a reso
 
 It's typically possible for someone with appropriate [role-based access
 control](../../../role-based-access-control/overview.md) (RBAC) on the subscription, such as the
-'Owner' role, to be allowed to alter or delete any resource. This access isn't the case when
+'Owner' role, to be allowed to alter or delete any resource. This access isn't the case when Azure
 Blueprints applies locking as part of a deployed assignment. If the assignment was set with the
 **Read Only** or **Do Not Delete** option, not even the subscription owner can perform the blocked
 action on the protected resource.
@@ -116,8 +116,8 @@ ways to do so.
 - Updating the blueprint assignment to a locking mode of **Don't Lock**
 - Delete the blueprint assignment
 
-When the assignment is removed, the locks created by Blueprints are removed. However, the resource
-is left behind and would need to be deleted through normal means.
+When the assignment is removed, the locks created by Azure Blueprints are removed. However, the
+resource is left behind and would need to be deleted through normal means.
 
 ## How blueprint locks work
 
@@ -126,7 +126,7 @@ applied to artifact resources during assignment of a blueprint if the assignment
 Only** or **Do Not Delete** option. The deny action is added by the managed identity of the
 blueprint assignment and can only be removed from the artifact resources by the same managed
 identity. This security measure enforces the locking mechanism and prevents removing the blueprint
-lock outside Blueprints.
+lock outside Azure Blueprints.
 
 ![Blueprint deny assignment on resource group](../media/resource-locking/blueprint-deny-assignment.png)
 

articles/governance/blueprints/concepts/sequencing-order.md

@@ -42,8 +42,8 @@ created within that resource group:
 
 When composing large blueprint definitions, it may be necessary for resources to be created in a
 specific order. The most common use pattern of this scenario is when a blueprint definition includes
-several Azure Resource Manager templates. Blueprints handles this pattern by allowing the sequencing
-order to be defined.
+several Azure Resource Manager templates. Azure Blueprints handles this pattern by allowing the
+sequencing order to be defined.
 
 The ordering is accomplished by defining a `dependsOn` property in the JSON. The blueprint
 definition, for resource groups, and artifact objects support this property. `dependsOn` is a string

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

@@ -425,8 +425,8 @@ lock, and blueprint parameters, use the matching PowerShell parameters on the
      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.
+     > Azure Blueprints doesn't manage the user-assigned managed identity. Users are responsible for
+     > assigning sufficient roles and permissions or the blueprint assignment will fail.
 
 ## Clean up resources
 

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

@@ -28,7 +28,7 @@ uses these concepts to provide directions for working with Azure Blueprints and
 knowledge of them. Tools such as [ARMClient](https://github.com/projectkudu/ARMClient) and others
 may handle authorization automatically and are recommended for beginners.
 
-For the Blueprints specs, see [Azure Blueprints REST API](/rest/api/blueprints/).
+For the Azure Blueprints specs, see [Azure Blueprints REST API](/rest/api/blueprints/).
 
 ### REST API and PowerShell
 
@@ -470,7 +470,7 @@ values:
      assigning the blueprint has permissions to.
 
      > [!IMPORTANT]
-     > Blueprints doesn't manage the user-assigned managed identity. Users are responsible for
+     > Azure Blueprints doesn't manage the user-assigned managed identity. Users are responsible for
      > assigning sufficient roles and permissions or the blueprint assignment will fail.
 
 ## Clean up resources

articles/governance/blueprints/how-to/import-export-ps.md

@@ -7,8 +7,8 @@ ms.topic: how-to
 # Import and export blueprint definitions with PowerShell
 
 Azure Blueprints can be fully managed through Azure portal. As organizations advance in their use of
-Blueprints, they should start thinking of blueprint definitions as managed code. This concept is
-often referred to as Infrastructure as Code (IaC). Treating your blueprint definitions as code
+Azure Blueprints, they should start thinking of blueprint definitions as managed code. This concept
+is often referred to as Infrastructure as Code (IaC). Treating your blueprint definitions as code
 offers additional advantages beyond what Azure portal offers. These benefits include:
 
 - Sharing blueprint definitions

articles/governance/blueprints/how-to/manage-assignments-ps.md

@@ -25,12 +25,12 @@ The Azure Blueprints module requires the following software:
 
 ### Install the module
 
-The Blueprints module for PowerShell is **Az.Blueprint**.
+The Azure Blueprints module for PowerShell is **Az.Blueprint**.
 
 1. From an **administrative** PowerShell prompt, run the following command:
 
    ```azurepowershell-interactive
-   # Install the Blueprints module from PowerShell Gallery
+   # Install the Azure Blueprints module from PowerShell Gallery
    Install-Module -Name Az.Blueprint
    ```
 

articles/governance/blueprints/overview.md

@@ -24,7 +24,7 @@ other artifacts such as:
 The Azure Blueprints service is backed by the globally distributed [Azure Cosmos DB](../../cosmos-db/introduction.md).
 Blueprint objects are replicated to multiple Azure regions. This replication provides low latency,
 high availability, and consistent access to your blueprint objects, regardless of which region
-Blueprints deploys your resources to.
+Azure Blueprints deploys your resources to.
 
 ## How it's different from Resource Manager templates
 
@@ -34,20 +34,21 @@ is a package to bring each of these _artifact_ types together and allow you to c
 that package -- including through a CI/CD pipeline. Ultimately, each is assigned to a subscription
 in a single operation that can be audited and tracked.
 
-Nearly everything that you want to include for deployment in Blueprints can be accomplished with a
-Resource Manager template. However, a Resource Manager template is a document that doesn't exist
-natively in Azure – each is stored either locally or in source control. The template gets used for
-deployments of one or more Azure resources, but once those resources deploy there's no active
+Nearly everything that you want to include for deployment in Azure Blueprints can be accomplished
+with a Resource Manager template. However, a Resource Manager template is a document that doesn't
+exist natively in Azure – each is stored either locally or in source control. The template gets used
+for deployments of one or more Azure resources, but once those resources deploy there's no active
 connection or relationship to the template.
 
-With Blueprints, the relationship between the blueprint definition (what _should be_ deployed) and
-the blueprint assignment (what _was_ deployed) is preserved. This connection supports improved
-tracking and auditing of deployments. Blueprints can also upgrade several subscriptions at once that
-are governed by the same blueprint.
+With Azure Blueprints, the relationship between the blueprint definition (what _should be_ deployed)
+and the blueprint assignment (what _was_ deployed) is preserved. This connection supports improved
+tracking and auditing of deployments. Azure Blueprints can also upgrade several subscriptions at
+once that are governed by the same blueprint.
 
 There's no need to choose between a Resource Manager template and a blueprint. Each blueprint can
 consist of zero or more Resource Manager template _artifacts_. This support means that previous
-efforts to develop and maintain a library of Resource Manager templates are reusable in Blueprints.
+efforts to develop and maintain a library of Resource Manager templates are reusable in Azure
+Blueprints.
 
 ## How it's different from Azure Policy
 
@@ -68,7 +69,7 @@ support using parameters with policies and initiatives.
 
 ## Blueprint definition
 
-A blueprint is made up of _artifacts_. Blueprints currently support the following resources
+A blueprint is made up of _artifacts_. Azure Blueprints currently supports the following resources
 as artifacts:
 
 |Resource  | Hierarchy options| Description  |