You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-resource-manager/managed-applications/deploy-service-catalog-quickstart.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Describes how to deploy a service catalog's managed application for
4
4
author: davidsmatlak
5
5
ms.author: davidsmatlak
6
6
ms.topic: quickstart
7
-
ms.date: 03/16/2023
7
+
ms.date: 03/21/2023
8
8
---
9
9
10
10
# Quickstart: Deploy a service catalog managed application
@@ -121,13 +121,13 @@ You also need to create a name for the managed application resource group. The r
121
121
Run the following commands to create the managed resource group's name.
122
122
123
123
```azurepowershell
124
-
$mrgprefix = 'rg-sampleManagedApplication-'
124
+
$mrgprefix = 'mrg-sampleManagedApplication-'
125
125
$mrgtimestamp = Get-Date -UFormat "%Y%m%d%H%M%S"
126
126
$mrgname = $mrgprefix + $mrgtimestamp
127
127
$mrgname
128
128
```
129
129
130
-
The `$mrgprefix` and `$mrgtimestamp` variables are concatenated to create a managed resource group name like _rg-sampleManagedApplication-20230310100148_ that's stored in the `$mrgname` variable. The name's format `rg-{definitionName}-{dateTime}` is the same format as the portal's default value. You use the `$mrgname` variable's value when you deploy the managed application.
130
+
The `$mrgprefix` and `$mrgtimestamp` variables are concatenated to create a managed resource group name like _mrg-sampleManagedApplication-20230310100148_ that's stored in the `$mrgname` variable. The name's format `mrg-{definitionName}-{dateTime}` is the same format as the portal's default value. You use the `$mrgname` variable's value when you deploy the managed application.
131
131
132
132
You need to provide several parameters to the deployment command for the managed application. You can use a JSON formatted string or create a JSON file. In this example, we use a JSON formatted string. The PowerShell escape character for the quote marks is the backtick (`` ` ``) character. The backtick is also used for line continuation so that commands can use multiple lines.
133
133
@@ -166,14 +166,14 @@ You also need to create a name and path for the managed application resource gro
166
166
Run the following commands to create the managed resource group's path.
167
167
168
168
```azurecli
169
-
mrgprefix='rg-sampleManagedApplication-'
169
+
mrgprefix='mrg-sampleManagedApplication-'
170
170
mrgtimestamp=$(date +%Y%m%d%H%M%S)
171
171
mrgname="${mrgprefix}${mrgtimestamp}"
172
172
subid=$(az account list --query [].id --output tsv)
The `mrgprefix` and `mrgtimestamp` variables are concatenated to create a managed resource group name like _rg-sampleManagedApplication-20230310100148_ that's stored in the `mrgname` variable. The name's format:`rg-{definitionName}-{dateTime}` is the same format as the portal's default value. The `mrgname` and `subid` variable's are concatenated to create the `mrgpath` variable value that creates the managed resource group during the deployment.
176
+
The `mrgprefix` and `mrgtimestamp` variables are concatenated to create a managed resource group name like _mrg-sampleManagedApplication-20230310100148_ that's stored in the `mrgname` variable. The name's format:`mrg-{definitionName}-{dateTime}` is the same format as the portal's default value. The `mrgname` and `subid` variable's are concatenated to create the `mrgpath` variable value that creates the managed resource group during the deployment.
177
177
178
178
You need to provide several parameters to the deployment command for the managed application. You can use a JSON formatted string or create a JSON file. In this example, we use a JSON formatted string. The PowerShell escape character for the quote marks is the backslash (`\`) character. The backslash is also used for line continuation so that commands can use multiple lines.
179
179
@@ -209,7 +209,7 @@ The parameters to create the managed resources:
209
209
-**Resource group**: Select the resource group. For this example, create a resource group named _applicationGroup_.
210
210
-**Region**: Select the location where you want to deploy the resource.
211
211
-**Application Name**: Enter a name for your managed application. For this example, use _demoManagedApplication_.
212
-
-**Application resources Resource group name**: The name of the managed resource group that contains the resources that are deployed for the managed application. The default name is in the format `rg-{definitionName}-{dateTime}` but you can change the name.
212
+
-**Managed Resource Group**: The name of the managed resource group that contains the resources that are deployed for the managed application. The default name is in the format `mrg-{definitionName}-{dateTime}` but you can change the name.
213
213
214
214
1. Provide values for the **Web App settings** tab and select **Next: Storage settings**.
215
215
@@ -395,15 +395,15 @@ To review the managed resource group's deny assignments, use the Azure portal or
395
395
396
396
# [Portal](#tab/azure-portal)
397
397
398
-
Go to the managed resource group with the name prefix **rg-sampleManagedApplication** and select **Overview** to display the resources that were deployed. The resource group contains an App Service, App Service plan, and storage account.
398
+
Go to the managed resource group with the name prefix **mrg-sampleManagedApplication** and select **Overview** to display the resources that were deployed. The resource group contains an App Service, App Service plan, and storage account.
399
399
400
400
:::image type="content" source="./media/deploy-service-catalog-quickstart/view-managed-resource-group.png" alt-text="Screenshot that shows the managed resource group that contains the resources deployed by the managed application definition.":::
401
401
402
402
The managed resource group and each resource created by the managed application has a role assignment. When you used a quickstart article to create the definition, you created an Azure Active Directory group. That group was used in the managed application definition. When you deployed the managed application, a role assignment for that group was added to the managed resources.
403
403
404
404
To see the role assignment from the Azure portal:
405
405
406
-
1. Go to your **rg-sampleManagedApplication** resource group.
406
+
1. Go to your **mrg-sampleManagedApplication** resource group.
407
407
1. Select **Access Control (IAM)** > **Role assignments**.
408
408
409
409
You can also view the resource's **Deny assignments**.
@@ -414,7 +414,7 @@ The role assignment gives the application's publisher access to manage the stora
414
414
415
415
## Clean up resources
416
416
417
-
When you're finished with the managed application, you can delete the resource groups and that removes all the resources you created. For example, in this quickstart you created the resource groups _applicationGroup_ and a managed resource group with the prefix _rg-sampleManagedApplication_.
417
+
When you're finished with the managed application, you can delete the resource groups and that removes all the resources you created. For example, in this quickstart you created the resource groups _applicationGroup_ and a managed resource group with the prefix _mrg-sampleManagedApplication_.
0 commit comments