Merge pull request #231629 from davidsmatlak/ds-fixes-0321

Fixes placeholders in code samples

Author: prmerger-automator[bot]

articles/azure-resource-manager/managed-applications/publish-service-catalog-app.md

@@ -5,7 +5,7 @@ author: davidsmatlak
 ms.author: davidsmatlak
 ms.topic: quickstart
 ms.custom: subject-armqs, devx-track-azurecli, devx-track-azurepowershell, subject-rbac-steps, mode-api, mode-arm
-ms.date: 03/17/2023
+ms.date: 03/21/2023
 ---
 
 # Quickstart: Create and publish an Azure Managed Application definition
@@ -261,7 +261,7 @@ To learn more, see [Get started with CreateUiDefinition](create-uidefinition-ove
 
 Add the two files to a package file named _app.zip_. The two files must be at the root level of the _.zip_ file. If the files are in a folder, when you create the managed application definition, you receive an error that states the required files aren't present.
 
-Upload _app.zip_ to an Azure storage account so you can use it when you deploy the managed application's definition. The storage account name must be globally unique across Azure and the length must be 3-24 characters with only lowercase letters and numbers. In the `Name` parameter, replace the placeholder `demostorageaccount` with your unique storage account name.
+Upload _app.zip_ to an Azure storage account so you can use it when you deploy the managed application's definition. The storage account name must be globally unique across Azure and the length must be 3-24 characters with only lowercase letters and numbers. In the command, replace the placeholder `<demostorageaccount>` including the angle brackets (`<>`), with your unique storage account name.
 
 # [PowerShell](#tab/azure-powershell)
 
@@ -278,7 +278,7 @@ New-AzResourceGroup -Name packageStorageGroup -Location westus3
 
 $storageAccount = New-AzStorageAccount `
   -ResourceGroupName packageStorageGroup `
-  -Name "demostorageaccount" `
+  -Name "<demostorageaccount>" `
   -Location westus3 `
   -SkuName Standard_LRS `
   -Kind StorageV2
@@ -308,7 +308,7 @@ The command opens your default browser and prompts you to sign in to Azure. For
 az group create --name packageStorageGroup --location westus3
 
 az storage account create \
-    --name demostorageaccount \
+    --name <demostorageaccount> \
     --resource-group packageStorageGroup \
     --location westus3 \
     --sku Standard_LRS \
@@ -321,13 +321,13 @@ After you add the role to the storage account, it takes a few minutes to become
 
 ```azurecli
 az storage container create \
-    --account-name demostorageaccount \
+    --account-name <demostorageaccount> \
     --name appcontainer \
     --auth-mode login \
     --public-access blob
 
 az storage blob upload \
-    --account-name demostorageaccount \
+    --account-name <demostorageaccount> \
     --container-name appcontainer \
     --auth-mode login \
     --name "app.zip" \
@@ -404,12 +404,12 @@ The next step is to select a user, security group, or application for managing t
 
 # [PowerShell](#tab/azure-powershell)
 
-This example uses a security group, and your Azure Active Directory account should be a member of the group. To get the group's object ID, replace the placeholder `managedAppDemo` with your group's name. You use this variable's value when you deploy the managed application definition.
+This example uses a security group, and your Azure Active Directory account should be a member of the group. To get the group's object ID, replace the placeholder `<managedAppDemo>` including the angle brackets (`<>`), with your group's name. You use this variable's value when you deploy the managed application definition.
 
 To create a new Azure Active Directory group, go to [Manage Azure Active Directory groups and group membership](../../active-directory/fundamentals/how-to-manage-groups.md).
 
 ```azurepowershell
-$principalid=(Get-AzADGroup -DisplayName managedAppDemo).Id
+$principalid=(Get-AzADGroup -DisplayName <managedAppDemo>).Id
 ```
 
 Next, get the role definition ID of the Azure built-in role you want to grant access to the user, group, or application. You use this variable's value when you deploy the managed application definition.
@@ -420,12 +420,12 @@ $roleid=(Get-AzRoleDefinition -Name Owner).Id
 
 # [Azure CLI](#tab/azure-cli)
 
-This example uses a security group, and your Azure Active Directory account should be a member of the group. To get the group's object ID, replace the placeholder `managedAppDemo` with your group's name. You use this variable's value when you deploy the managed application definition.
+This example uses a security group, and your Azure Active Directory account should be a member of the group. To get the group's object ID, replace the placeholder `<managedAppDemo>` including the angle brackets (`<>`), with your group's name. You use this variable's value when you deploy the managed application definition.
 
 To create a new Azure Active Directory group, go to [Manage Azure Active Directory groups and group membership](../../active-directory/fundamentals/how-to-manage-groups.md).
 
 ```azurecli
-principalid=$(az ad group show --group managedAppDemo --query id --output tsv)
+principalid=$(az ad group show --group <managedAppDemo> --query id --output tsv)
 ```
 
 Next, get the role definition ID of the Azure built-in role you want to grant access to the user, group, or application. You use this variable's value when you deploy the managed application definition.
@@ -485,11 +485,11 @@ Create a resource group for your managed application definition.
 az group create --name appDefinitionGroup --location westus3
 ```
 
-In the `blob` command's `account-name` parameter, replace the placeholder `demostorageaccount` with your unique storage account name. The `blob` command creates a variable to store the URL for the package _.zip_ file. That variable is used in the command that creates the managed application definition.
+In the `blob` command's `account-name` parameter, replace the placeholder `<demostorageaccount>` including the angle brackets (`<>`), with your unique storage account name. The `blob` command creates a variable to store the URL for the package _.zip_ file. That variable is used in the command that creates the managed application definition.
 
 ```azurecli
 blob=$(az storage blob url \
-  --account-name demostorageaccount \
+  --account-name <demostorageaccount> \
   --container-name appcontainer \
   --auth-mode login \
   --name app.zip --output tsv)

articles/azure-resource-manager/managed-applications/publish-service-catalog-bring-your-own-storage.md

@@ -5,7 +5,7 @@ author: davidsmatlak
 ms.author: davidsmatlak
 ms.topic: quickstart
 ms.custom: subject-armqs, devx-track-azurecli, devx-track-azurepowershell, subject-rbac-steps, mode-api, mode-arm
-ms.date: 03/01/2023
+ms.date: 03/21/2023
 ---
 
 # Quickstart: Bring your own storage to create and publish an Azure Managed Application definition
@@ -262,7 +262,7 @@ To learn more, go to [Get started with CreateUiDefinition](create-uidefinition-o
 
 Add the two files to a package file named _app.zip_. The two files must be at the root level of the _.zip_ file. If the files are in a folder, when you create the managed application definition, you receive an error that states the required files aren't present.
 
-Upload _app.zip_ to an Azure storage account so you can use it when you deploy the managed application's definition. The storage account name must be globally unique across Azure and the length must be 3-24 characters with only lowercase letters and numbers. In the `Name` parameter, replace the placeholder `demostorageaccount` with your unique storage account name.
+Upload _app.zip_ to an Azure storage account so you can use it when you deploy the managed application's definition. The storage account name must be globally unique across Azure and the length must be 3-24 characters with only lowercase letters and numbers. In the command, replace the placeholder `<demostorageaccount>` including the angle brackets (`<>`), with your unique storage account name.
 
 # [PowerShell](#tab/azure-powershell)
 
@@ -271,7 +271,7 @@ New-AzResourceGroup -Name packageStorageGroup -Location westus3
 
 $storageAccount = New-AzStorageAccount `
   -ResourceGroupName packageStorageGroup `
-  -Name "demostorageaccount" `
+  -Name "<demostorageaccount>" `
   -Location westus3 `
   -SkuName Standard_LRS `
   -Kind StorageV2
@@ -299,7 +299,7 @@ $packageuri=(Get-AzStorageBlob -Container appcontainer -Blob app.zip -Context $c
 az group create --name packageStorageGroup --location westus3
 
 az storage account create \
-    --name demostorageaccount \
+    --name <demostorageaccount> \
     --resource-group packageStorageGroup \
     --location westus3 \
     --sku Standard_LRS \
@@ -312,13 +312,13 @@ After you add the role to the storage account, it takes a few minutes to become
 
 ```azurecli
 az storage container create \
-    --account-name demostorageaccount \
+    --account-name <demostorageaccount> \
     --name appcontainer \
     --auth-mode login \
     --public-access blob
 
 az storage blob upload \
-    --account-name demostorageaccount \
+    --account-name <demostorageaccount> \
     --container-name appcontainer \
     --auth-mode login \
     --name "app.zip" \
@@ -331,7 +331,7 @@ Use the following command to store the package file's URI in a variable named `p
 
 ```azurecli
 packageuri=$(az storage blob url \
-  --account-name demostorageaccount \
+  --account-name <demostorageaccount> \
   --container-name appcontainer \
   --auth-mode login \
   --name app.zip --output tsv)
@@ -350,7 +350,7 @@ You store your managed application definition in your own storage account so tha
 
 Create the storage account for your managed application definition. The storage account name must be globally unique across Azure and the length must be 3-24 characters with only lowercase letters and numbers.
 
-This example creates a new resource group named `byosDefinitionStorageGroup`. In the `Name` parameter, replace the placeholder `definitionstorage` with your unique storage account name.
+This example creates a new resource group named `byosDefinitionStorageGroup`. In the command, replace the placeholder `<definitionstorage>` including the angle brackets (`<>`), with your unique storage account name.
 
 # [PowerShell](#tab/azure-powershell)
 
@@ -359,7 +359,7 @@ New-AzResourceGroup -Name byosDefinitionStorageGroup -Location westus3
 
 New-AzStorageAccount `
   -ResourceGroupName byosDefinitionStorageGroup `
-  -Name "definitionstorage" `
+  -Name "<definitionstorage>" `
   -Location westus3 `
   -SkuName Standard_LRS `
   -Kind StorageV2
@@ -368,7 +368,7 @@ New-AzStorageAccount `
 Use the following command to store the storage account's resource ID in a variable named `storageid`. You use the variable's value when you deploy the managed application definition.
 
 ```azurepowershell
-$storageid = (Get-AzStorageAccount -ResourceGroupName byosDefinitionStorageGroup -Name definitionstorage).Id
+$storageid = (Get-AzStorageAccount -ResourceGroupName byosDefinitionStorageGroup -Name <definitionstorage>).Id
 ```
 
 # [Azure CLI](#tab/azure-cli)
@@ -377,7 +377,7 @@ $storageid = (Get-AzStorageAccount -ResourceGroupName byosDefinitionStorageGroup
 az group create --name byosDefinitionStorageGroup --location westus3
 
 az storage account create \
-    --name definitionstorage \
+    --name <definitionstorage> \
     --resource-group byosDefinitionStorageGroup \
     --location westus3 \
     --sku Standard_LRS \
@@ -387,7 +387,7 @@ az storage account create \
 Use the following command to store the storage account's resource ID in a variable named `storageid`. You use the variable's value to set up the storage account's role assignment and when you deploy the managed application definition.
 
 ```azurecli
-storageid=$(az storage account show --resource-group byosDefinitionStorageGroup --name definitionstorage --query id --output tsv)
+storageid=$(az storage account show --resource-group byosDefinitionStorageGroup --name <definitionstorage> --query id --output tsv)
 ```
 
 ---
@@ -430,20 +430,20 @@ The _Appliance Resource Provider_ is a service principal in your Azure Active Di
 
 The next step is to select a user, security group, or application for managing the resources for the customer. This identity has permissions on the managed resource group according to the assigned role. The role can be any Azure built-in role like Owner or Contributor.
 
-This example uses a security group, and your Azure Active Directory account should be a member of the group. To get the group's object ID, replace the placeholder `managedAppDemo` with your group's name. You use the variable's value when you deploy the managed application definition.
+This example uses a security group, and your Azure Active Directory account should be a member of the group. To get the group's object ID, replace the placeholder `<managedAppDemo>` including the angle brackets (`<>`), with your group's name. You use the variable's value when you deploy the managed application definition.
 
 To create a new Azure Active Directory group, go to [Manage Azure Active Directory groups and group membership](../../active-directory/fundamentals/how-to-manage-groups.md).
 
 # [PowerShell](#tab/azure-powershell)
 
 ```azurepowershell
-$principalid=(Get-AzADGroup -DisplayName managedAppDemo).Id
+$principalid=(Get-AzADGroup -DisplayName <managedAppDemo>).Id
 ```
 
 # [Azure CLI](#tab/azure-cli)
 
 ```azurecli
-principalid=$(az ad group show --group managedAppDemo --query id --output tsv)
+principalid=$(az ad group show --group <managedAppDemo> --query id --output tsv)
 ```
 
 ---
@@ -523,27 +523,27 @@ The managed application definition's deployment template needs input for several
 
 In Visual Studio Code, create a new file named _deployDefinition.parameters.json_ and save it.
 
-Add the following to your parameter file and save it. Then, replace the `{placeholder values}` including the curly braces, with your values.
+Add the following to your parameter file and save it. Then, replace the `<placeholder values>` including the angle brackets (`<>`), with your values.
 
 ```json
 {
   "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentParameters.json#",
   "contentVersion": "1.0.0.0",
   "parameters": {
     "managedApplicationDefinitionName": {
-      "value": "{placeholder for managed application name}"
+      "value": "<placeholder for managed application name>"
     },
     "definitionStorageResourceID": {
-      "value": "{placeholder for you storage account ID}"
+      "value": "<placeholder for you storage account ID>"
     },
     "packageFileUri": {
-      "value": "{placeholder for the packageFileUri}"
+      "value": "<placeholder for the packageFileUri>"
     },
     "principalId": {
-      "value": "{placeholder for principalid value}"
+      "value": "<placeholder for principalid value>"
     },
     "roleId": {
-      "value": "{placeholder for roleid value}"
+      "value": "<placeholder for roleid value>"
     }
   }
 }
@@ -559,9 +559,9 @@ The following table describes the parameter values for the managed application d
 | `principalId` | The publishers Principal ID that needs permissions to manage resources in the managed resource group. Use your `principalid` variable's value. |
 | `roleId` | Role ID for permissions to the managed resource group. For example Owner, Contributor, Reader. Use your `roleid` variable's value. |
 
-To get your variable values from the command prompt:
-- Azure PowerShell: type `$variableName` to display the value.
-- Azure CLI: type `echo $variableName` to display the value.
+To get your variable values:
+- Azure PowerShell: In PowerShell, type `$variableName` to display a variable's value.
+- Azure CLI: In Bash, type `echo $variableName` to display a variable's value.
 
 ## Deploy the definition
 
@@ -597,12 +597,12 @@ az deployment group create \
 
 During deployment, the template's `storageAccountId` property uses your storage account's resource ID and creates a new container with the case-sensitive name `applicationdefinitions`. The files from the _.zip_ package you specified during the deployment are stored in the new container.
 
-You can use the following commands to verify that the managed application definition files are saved in your storage account's container. In the `Name` parameter, replace the placeholder `definitionstorage` with your unique storage account name.
+You can use the following commands to verify that the managed application definition files are saved in your storage account's container. In the command, replace the placeholder `<definitionstorage>` including the angle brackets (`<>`), with your unique storage account name.
 
 # [PowerShell](#tab/azure-powershell)
 
 ```azurepowershell
-Get-AzStorageAccount -ResourceGroupName byosDefinitionStorageGroup -Name definitionstorage |
+Get-AzStorageAccount -ResourceGroupName byosDefinitionStorageGroup -Name <definitionstorage> |
 Get-AzStorageContainer -Name applicationdefinitions |
 Get-AzStorageBlob | Select-Object -Property Name | Format-List
 ```
@@ -612,7 +612,7 @@ Get-AzStorageBlob | Select-Object -Property Name | Format-List
 ```azurecli
 az storage blob list \
   --container-name applicationdefinitions \
-  --account-name definitionstorage \
+  --account-name <definitionstorage> \
   --query "[].{Name:name}"
 ```