edits content and updates screenshots

Author: davidsmatlak

articles/azure-resource-manager/managed-applications/deploy-service-catalog-quickstart.md

@@ -1,19 +1,19 @@
 ---
 title: Deploy a service catalog managed application
-description: Shows consumers of Azure Managed Applications how to deploy a service catalog managed application.
+description: Describes how to deploy a service catalog's managed application for an Azure Managed Application.
 author: davidsmatlak
 ms.author: davidsmatlak
 ms.topic: quickstart
 ms.date: 03/01/2023
 ---
 
-# Quickstart: Deploy service catalog managed application
+# Quickstart: Deploy a service catalog managed application
 
 In this quickstart, you use the definition you created in the quickstarts to [publish an application definition](publish-service-catalog-app.md) or [publish a definition with bring your own storage](publish-service-catalog-bring-your-own-storage.md) to deploy a service catalog managed application. The deployment creates two resource groups. One resource group contains the managed application and the other is a managed resource group for the deployed resource. The managed application definition deploys an App Service plan, App Service, and storage account.
 
 ## Prerequisites
 
-To complete this quickstart, you need an Azure account with an active subscription. If you completed the quickstart to publish a definition, you should already have an account. Otherwise, [create a free account](https://azure.microsoft.com/free/) before you begin.
+To complete this quickstart, you need an Azure account with an active subscription. If you completed a quickstart to publish a definition, you should already have an account. Otherwise, [create a free account](https://azure.microsoft.com/free/) before you begin.
 
 ## Create service catalog managed application
 
@@ -70,21 +70,21 @@ After the service catalog managed application is deployed, you have two new reso
 
 ### Managed application
 
-Go to the resource group named **applicationGroup**. The resource group contains your managed application named _demoManagedApplication_.
+Go to the resource group named **applicationGroup** and select **Overview**. The resource group contains your managed application named _demoManagedApplication_.
 
    :::image type="content" source="./media/deploy-service-catalog-quickstart/view-application-group.png" alt-text="Screenshot that shows the resource group that contains the managed application.":::
 
-Select the managed application's name to get more information like a link to the managed resource group.
+Select the managed application's name to get more information like the link to the managed resource group.
 
    :::image type="content" source="./media/deploy-service-catalog-quickstart/view-managed-application.png" alt-text="Screenshot that shows the managed application's details and highlights the link to the managed resource group.":::
 
 ### Managed resource
 
-Go to the managed resource group with the name prefix **rg-sampleManagedApplication** to display the resources that were deployed. The resource group contains an App Service plan, App Service, and storage account.
+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.
 
    :::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.":::
 
-The managed resource group and each resource that's created by the managed application has a role assignment. In the [publish the definition](publish-service-catalog-app.md#get-group-id-and-role-definition-id) article, 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.
+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.
 
 To see the role assignment from the Azure portal:
 
@@ -113,5 +113,5 @@ If you want to delete the managed application definition, delete the resource gr
 
 ## Next steps
 
-- To learn how to create the definition files for a managed application, go to [Quickstart: Create and publish an Azure Managed Application definition](publish-service-catalog-app.md).
-- To create the definition files for a managed application using your own storage, go to [Quickstart: Bring your own storage to publish an Azure Managed Application definition](publish-service-catalog-bring-your-own-storage.md).
+- To learn how to create and publish the definition files for a managed application, go to [Quickstart: Create and publish an Azure Managed Application definition](publish-service-catalog-app.md).
+- To use your own storage to create and publish the definition files for a managed application, go to [Quickstart: Bring your own storage to create and publish an Azure Managed Application definition](publish-service-catalog-bring-your-own-storage.md).

articles/azure-resource-manager/managed-applications/media/deploy-service-catalog-quickstart/summary-validation.png

@@ -1,6 +1,6 @@
 ---
-title: Publish Azure Managed Application in service catalog
-description: Describes how to publish an Azure Managed Application in your service catalog that's intended for members of your organization.
+title: Create and publish Azure Managed Application in service catalog
+description: Describes how to create and publish an Azure Managed Application in your service catalog that's intended for members of your organization.
 author: davidsmatlak
 ms.author: davidsmatlak
 ms.topic: quickstart
@@ -10,13 +10,13 @@ ms.date: 03/01/2023
 
 # Quickstart: Create and publish an Azure Managed Application definition
 
-This quickstart provides an introduction to working with [Azure Managed Applications](overview.md). You create and publish a managed application that's stored in your service catalog and is intended for members of your organization.
+This quickstart provides an introduction to working with [Azure Managed Applications](overview.md). You create and publish a managed application definition that's stored in your service catalog and is intended for members of your organization.
 
 To publish a managed application to your service catalog, do the following tasks:
 
 - Create an Azure Resource Manager template (ARM template) that defines the resources to deploy with the managed application.
 - Define the user interface elements for the portal when deploying the managed application.
--Create a _.zip_ package that contains the required JSON files. The _.zip_ package file has a 120-MB limit for a service catalog's managed application definition.
+- Create a _.zip_ package that contains the required JSON files. The _.zip_ package file has a 120-MB limit for a service catalog's managed application definition.
 - Deploy the managed application definition so it's available in your service catalog.
 
 If your managed application definition is more than 120 MB or if you want to use your own storage account for your organization's compliance reasons, go to [Quickstart: Bring your own storage to create and publish an Azure Managed Application definition](publish-service-catalog-bring-your-own-storage.md).
@@ -158,7 +158,7 @@ Add the following JSON and save the file. It defines the resources to deploy an
 
 As a publisher, you define the portal experience to create the managed application. The _createUiDefinition.json_ file generates the portal's user interface. You define how users provide input for each parameter using [control elements](create-uidefinition-elements.md) like drop-downs and text boxes.
 
-Open Visual Studio Code, create a file with the case-sensitive name _createUiDefinition.json_ and save it. The user interface allows the user to input the App Service name, App Service plan's name, storage account prefix, and storage account type. During deployment, the `uniqueString` function appends a 13 character string to the name prefixes so the names are globally unique across Azure.
+Open Visual Studio Code, create a file with the case-sensitive name _createUiDefinition.json_ and save it. The user interface allows the user to input the App Service name prefix, App Service plan's name, storage account prefix, and storage account type. During deployment, the variables in _mainTemplate.json_ use the `uniqueString` function to append a 13-character string to the name prefixes so the names are globally unique across Azure.
 
 Add the following JSON to the file and save it.
 
@@ -324,13 +324,13 @@ For more information about storage authentication, see [Choose how to authorize
 
 ## Create the managed application definition
 
-In this section you'll get identity information from Azure Active Directory, create a resource group, and create the managed application definition.
+In this section you get identity information from Azure Active Directory, create a resource group, and create the managed application definition.
 
 ### Get group ID and role definition ID
 
 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'll 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` 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).
 
@@ -348,7 +348,7 @@ 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'll use this variable's value when you deploy the managed application definition.
+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.
 
 # [PowerShell](#tab/azure-powershell)
 
@@ -448,4 +448,4 @@ You have access to the managed application definition, but you want to make sure
 You've published the managed application definition. Now, learn how to deploy an instance of that definition.
 
 > [!div class="nextstepaction"]
-> [Quickstart: Deploy service catalog managed application](deploy-service-catalog-quickstart.md)
+> [Quickstart: Deploy a service catalog managed application](deploy-service-catalog-quickstart.md)

articles/azure-resource-manager/managed-applications/media/deploy-service-catalog-quickstart/view-application-group.png

@@ -1,14 +1,14 @@
 ---
-title: Bring your own storage to publish an Azure Managed Application definition
-description: Describes how to bring your own storage to publish an Azure Managed Application definition in your service catalog.
+title: Bring your own storage to create and publish an Azure Managed Application definition
+description: Describes how to bring your own storage to create and publish an Azure Managed Application definition in your service catalog.
 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
 ---
 
-# Quickstart: Bring your own storage to publish an Azure Managed Application definition
+# Quickstart: Bring your own storage to create and publish an Azure Managed Application definition
 
 This quickstart provides an introduction to bring your own storage (BYOS) for an [Azure Managed Application](overview.md). You create and publish a managed application definition in your service catalog for members of your organization. When you use your own storage account, your managed application definition can exceed the service catalog's 120-MB limit.
 
@@ -159,7 +159,7 @@ Add the following JSON and save the file. It defines the managed application's r
 
 As a publisher, you define the portal experience to create the managed application. The _createUiDefinition.json_ file generates the portal's user interface. You define how users provide input for each parameter using [control elements](create-uidefinition-elements.md) like drop-downs and text boxes.
 
-Open Visual Studio Code, create a file with the case-sensitive name _createUiDefinition.json_ and save it. The user interface allows the user to input the App Service name, App Service plan's name, storage account prefix, and storage account type. During deployment, the `uniqueString` function appends a 13 character string to the name prefixes so the names are globally unique across Azure.
+Open Visual Studio Code, create a file with the case-sensitive name _createUiDefinition.json_ and save it. The user interface allows the user to input the App Service name prefix, App Service plan's name, storage account prefix, and storage account type. During deployment, the variables in _mainTemplate.json_ use the `uniqueString` function to append a 13-character string to the name prefixes so the names are globally unique across Azure.
 
 Add the following JSON to the file and save it.
 
@@ -466,7 +466,7 @@ roleid=$(az role definition list --name Owner --query [].name --output tsv)
 
 ## Create the definition deployment template
 
-Use a Bicep file to deploy the managed application definition in your service catalog. After the deployment, the definition files are stored in your bring your own storage account.
+Use a Bicep file to deploy the managed application definition in your service catalog. After the deployment, the definition files are stored in your own storage account.
 
 Open Visual Studio Code, create a file with the name _deployDefinition.bicep_ and save it.
 
@@ -632,4 +632,4 @@ You have access to the managed application definition, but you want to make sure
 You've published the managed application definition. Now, learn how to deploy an instance of that definition.
 
 > [!div class="nextstepaction"]
-> [Quickstart: Deploy service catalog managed application](deploy-service-catalog-quickstart.md)
+> [Quickstart: Deploy a service catalog managed application](deploy-service-catalog-quickstart.md)