Merge pull request #187702 from mumian/0207-idempotent

Don't use newguid() for the role assignment name

Author: PRMerger3

articles/azure-resource-manager/bicep/scope-extension-resources.md

@@ -1,10 +1,8 @@
 ---
 title: Scope on extension resource types (Bicep)
 description: Describes how to use the scope property when deploying extension resource types with Bicep.
-author: mumian
-ms.author: jgao
 ms.topic: conceptual
-ms.date: 11/16/2021
+ms.date: 02/07/2022
 ---
 
 # Set scope for extension resources in Bicep
@@ -54,8 +52,8 @@ param principalId string
 @description('Built-in role to assign')
 param builtInRoleType string
 
-@description('A new GUID used to identify the role assignment')
-param roleNameGuid string = newGuid()
+@description('The role assignment name')
+param roleNameGuid string
 
 var role = {
   Owner: '/subscriptions/${subscription().subscriptionId}/providers/Microsoft.Authorization/roleDefinitions/8e3af657-a8ff-443c-a75c-2fe8c4bcb635'

articles/azure-resource-manager/templates/deploy-github-actions.md

@@ -2,7 +2,7 @@
 title: Deploy Resource Manager templates by using GitHub Actions
 description: Describes how to deploy Azure Resource Manager templates (ARM templates) by using GitHub Actions.
 ms.topic: conceptual
-ms.date: 10/13/2020
+ms.date: 02/07/2022
 ms.custom: github-actions-azure
 ---
 
@@ -16,8 +16,8 @@ Use the [Deploy Azure Resource Manager Template Action](https://github.com/marke
 
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 - A GitHub account. If you don't have one, sign up for [free](https://github.com/join).
-    - A GitHub repository to store your Resource Manager templates and your workflow files. To create one, see [Creating a new repository](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/creating-a-new-repository).
 
+  - A GitHub repository to store your Resource Manager templates and your workflow files. To create one, see [Creating a new repository](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/creating-a-new-repository).
 
 ## Workflow file overview
 
@@ -32,7 +32,6 @@ The file has two sections:
 
 ## Generate deployment credentials
 
-
 You can create a [service principal](../../active-directory/develop/app-objects-and-service-principals.md#service-principal-object) with the [az ad sp create-for-rbac](/cli/azure/ad/sp#az_ad_sp_create_for_rbac) command in the [Azure CLI](/cli/azure/). Run this command with [Azure Cloud Shell](https://shell.azure.com/) in the Azure portal or by selecting the **Try it** button.
 
 Create a resource group if you do not already have one.
@@ -62,8 +61,6 @@ In the example above, replace the placeholders with your subscription ID and res
 > [!IMPORTANT]
 > It is always a good practice to grant minimum access. The scope in the previous example is limited to the resource group.
 
-
-
 ## Configure the GitHub secrets
 
 You need to create secrets for your Azure credentials, resource group, and subscriptions.
@@ -126,6 +123,7 @@ The workflow file must be stored in the **.github/workflows** folder at the root
           # output containerName variable from template
         - run: echo ${{ steps.deploy.outputs.containerName }}
     ```
+
     > [!NOTE]
     > You can specify a JSON format parameters file instead in the ARM Deploy action (example: `.azuredeploy.parameters.json`).
 
@@ -147,6 +145,7 @@ Because the workflow is configured to be triggered by either the workflow file o
 1. Select **Run ARM deploy** from the menu to verify the deployment.
 
 ## Clean up resources
+
 When your resource group and repository are no longer needed, clean up the resources you deployed by deleting the resource group and your GitHub repository.
 
 ## Next steps