revisions

Author: tfitzmac

articles/azure-resource-manager/managed-applications/concepts-custom-role-definition.md

@@ -15,7 +15,7 @@ This article provides an overview of the custom role definition artifact and its
 
 ## Custom role definition artifact
 
-You need to name the custom role definition artifact customRoleDefinition.json. Place it at the same level as createUiDefinition.json and mainTemplate.json in the .zip package that creates a managed application definition. To learn how to create the .zip package and publish a managed application definition, see [Publish a managed application definition.](publish-managed-app-definition-quickstart.md)
+You need to name the custom role definition artifact customRoleDefinition.json. Place it at the same level as createUiDefinition.json and mainTemplate.json in the .zip package that creates a managed application definition. To learn how to create the .zip package and publish a managed application definition, see [Publish a managed application definition.](publish-service-catalog-app.md)
 
 ## Custom role definition schema
 

articles/azure-resource-manager/managed-applications/concepts-view-definition.md

@@ -15,7 +15,7 @@ This article provides an overview of view definition artifact and its capabiliti
 
 ## View definition artifact
 
-The view definition artifact must be named **viewDefinition.json** and placed at the same level as **createUiDefinition.json** and **mainTemplate.json** in the .zip package that creates a managed application definition. To learn how to create the .zip package and publish a managed application definition, see [Publish an Azure Managed Application definition](publish-managed-app-definition-quickstart.md)
+The view definition artifact must be named **viewDefinition.json** and placed at the same level as **createUiDefinition.json** and **mainTemplate.json** in the .zip package that creates a managed application definition. To learn how to create the .zip package and publish a managed application definition, see [Publish an Azure Managed Application definition](publish-service-catalog-app.md)
 
 ## View definition schema
 

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

@@ -9,7 +9,7 @@ ms.author: tomfitz
 ---
 # Quickstart: Deploy service catalog app through Azure portal
 
-In the [preceding quickstart](publish-managed-app-definition-quickstart.md), you published a managed application definition. In this quickstart, you create a service catalog app from that definition.
+In the [preceding quickstart](publish-service-catalog-app.md), you published a managed application definition. In this quickstart, you create a service catalog app from that definition.
 
 ## Create service catalog app
 

articles/azure-resource-manager/managed-applications/overview.md

@@ -79,4 +79,4 @@ You can apply an [Azure Policy](../../governance/policy/overview.md) to your man
 In this article, you learned about benefits of using managed applications. Go to the next article to create a managed application definition.
 
 > [!div class="nextstepaction"]
-> [Quickstart: Publish an Azure managed application definition](publish-managed-app-definition-quickstart.md)
+> [Quickstart: Publish an Azure managed application definition](publish-service-catalog-app.md)

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

@@ -189,13 +189,13 @@ az storage blob upload \
 
 ### Create an Azure Active Directory user group or application
 
-The next step is to select a user group, user, or application for managing the resources on behalf of the customer. This identity has permissions on the managed resource group according to the role that is assigned. The role can be any built-in Role-Based Access Control (RBAC) role like Owner or Contributor. To create a new Active Directory user group, see [Create a group and add members in Azure Active Directory](../../active-directory/fundamentals/active-directory-groups-create-azure-portal.md).
+The next step is to select a user group, user, or application for managing the resources for the customer. This identity has permissions on the managed resource group according to the role that is assigned. The role can be any built-in Role-Based Access Control (RBAC) role like Owner or Contributor. To create a new Active Directory user group, see [Create a group and add members in Azure Active Directory](../../active-directory/fundamentals/active-directory-groups-create-azure-portal.md).
 
 You need the object ID of the user group to use for managing the resources. 
 
 # [PowerShell](#tab/azure-powershell)
 
-```powershell
+```azurepowershell-interactive
 $groupID=(Get-AzADGroup -DisplayName mygroup).Id
 ```
 
@@ -213,7 +213,7 @@ Next, you need the role definition ID of the RBAC built-in role you want to gran
 
 # [PowerShell](#tab/azure-powershell)
 
-```powershell
+```azurepowershell-interactive
 $ownerID=(Get-AzRoleDefinition -Name Owner).Id
 ```
 
@@ -231,7 +231,7 @@ If you don't already have a resource group for storing your managed application
 
 # [PowerShell](#tab/azure-powershell)
 
-```powershell
+```azurepowershell-interactive
 New-AzResourceGroup -Name appDefinitionGroup -Location westcentralus
 ```
 
@@ -247,7 +247,7 @@ Now, create the managed application definition resource.
 
 # [PowerShell](#tab/azure-powershell)
 
-```powershell
+```azurepowershell-interactive
 $blob = Get-AzStorageBlob -Container appcontainer -Blob app.zip -Context $ctx
 
 New-AzManagedApplicationDefinition `
@@ -264,6 +264,8 @@ New-AzManagedApplicationDefinition `
 # [Azure CLI](#tab/azure-cli)
 
 ```azurecli-interactive
+blob=$(az storage blob url --account-name mystorageaccount --container-name appcontainer --name app.zip --output tsv)
+
 az managedapp definition create \
   --name "ManagedStorage" \
   --location "westcentralus" \
@@ -272,7 +274,7 @@ az managedapp definition create \
   --display-name "Managed Storage Account" \
   --description "Managed Azure Storage Account" \
   --authorizations "$groupid:$ownerid" \
-  --package-file-uri "https://github.com/Azure/azure-managedapp-samples/raw/master/Managed%20Application%20Sample%20Packages/201-managed-storage-account/managedstorage.zip"
+  --package-file-uri "$blob"
 ```
 
 ---
@@ -288,7 +290,7 @@ Some of the parameters used in the preceding example are:
 
 ## Bring your own storage for the managed application definition
 
-You can choose to store your managed application definition within a storage account provided by you during creation so that it's location and access can be fully managed by you for your regulatory needs.
+You can choose to store your managed application definition within a storage account provided by you during creation so that its location and access can be fully managed by you for your regulatory needs.
 
 > [!NOTE]
 > Bring your own storage is only supported with ARM Template or REST API deployments of the managed application definition.
@@ -307,7 +309,7 @@ Before your managed application definition can be deployed to your storage accou
 1. Select **Access control (IAM)** to display the access control settings for the storage account. Select the **Role assignments** tab to see the list of role assignments.
 1. In the **Add role assignment** window, select the **Contributor** role. 
 1. From the **Assign access to** field, select **Azure AD user, group, or service principal**.
-1. Under **Select** search for **Appliance Resource Provider** role and select it.
+1. Under **Select**, search for **Appliance Resource Provider** role and select it.
 1. Save the role assignment.
 
 ### Deploy the managed application definition with an ARM Template 
@@ -384,7 +386,7 @@ Use the following ARM Template to deploy your packaged managed application as a
 }
 ```
 
-We have added a new property named **storageAccountId** to your applicationDefintion's properties and provide storage account id you wish to store your definition in as its value:
+We have added a new property named **storageAccountId** to your applicationDefintion's properties and provide storage account ID you wish to store your definition in as its value:
 
 You can verify that the application definition files are saved in your provided storage account in a container titled **applicationdefinitions**.
 

articles/marketplace/cloud-partner-portal/azure-applications/cpp-create-technical-assets.md

@@ -28,7 +28,7 @@ Review the following Azure application documentation, which provides Quickstarts
 
   - [Azure Quickstart templates](https://azure.microsoft.com/documentation/templates/)
   - [GitHub Azure Quickstart templates](https://github.com/azure/azure-quickstart-templates)
-  - [Publish application definition](https://docs.microsoft.com/azure/managed-applications/publish-managed-app-definition-quickstart)
+  - [Publish application definition](https://docs.microsoft.com/azure/managed-applications/publish-service-catalog-app)
   - [Deploy service catalog app](https://docs.microsoft.com/azure/managed-applications/deploy-service-catalog-quickstart)
 
 

articles/marketplace/partner-center-portal/create-new-azure-apps-offer.md

@@ -53,7 +53,7 @@ Review the following Azure application documentation, which provides Quickstarts
 
     * [Azure Quickstart templates](https://azure.microsoft.com/documentation/templates/)
     * [GitHub Azure Quickstart templates](https://github.com/azure/azure-quickstart-templates)
-    * [Publish application definition](https://docs.microsoft.com/azure/managed-applications/publish-managed-app-definition-quickstart)
+    * [Publish application definition](https://docs.microsoft.com/azure/managed-applications/publish-service-catalog-app)
     * [Deploy service catalog app](https://docs.microsoft.com/azure/managed-applications/deploy-service-catalog-quickstart)
 
 * Tutorials: