Merge pull request #287162 from MicrosoftDocs/main

Publish to live, Monday 4 AM PST, 9/23

Author: ttorble

articles/azure-resource-manager/managed-applications/deploy-bicep-definition.md

@@ -3,7 +3,7 @@ title: Use Bicep to deploy an Azure Managed Application definition
 description: Describes how to use Bicep to deploy an Azure Managed Application definition from your service catalog.
 ms.topic: quickstart
 ms.custom: devx-track-azurepowershell, devx-track-bicep, devx-track-azurecli
-ms.date: 06/24/2024
+ms.date: 09/22/2024
 ---
 
 # Quickstart: Use Bicep to deploy an Azure Managed Application definition
@@ -27,7 +27,7 @@ To complete the tasks in this article, you need the following items:
 
 ## Get managed application definition
 
-# [PowerShell](#tab/azure-powershell)
+# [Azure PowerShell](#tab/azure-powershell)
 
 To get the managed application's definition with Azure PowerShell, run the following commands.
 
@@ -110,18 +110,6 @@ param appServicePlanName string
 @description('Globally unique across Azure. Maximum of 47 alphanumeric characters or hyphens.')
 param appServiceNamePrefix string
 
-@maxLength(11)
-@description('Use only lowercase letters and numbers and a maximum of 11 characters.')
-param storageAccountNamePrefix string
-
-@allowed([
-  'Premium_LRS'
-  'Standard_LRS'
-  'Standard_GRS'
-])
-@description('The options are Premium_LRS, Standard_LRS, or Standard_GRS')
-param storageAccountType string
-
 @description('Resource ID for the managed application definition.')
 var appResourceId = resourceId('${definitionRG}', 'Microsoft.Solutions/applicationdefinitions', '${definitionName}')
 
@@ -142,12 +130,6 @@ resource bicepServiceCatalogApp 'Microsoft.Solutions/applications@2021-07-01' =
       appServiceNamePrefix: {
         value: appServiceNamePrefix
       }
-      storageAccountNamePrefix: {
-        value: storageAccountNamePrefix
-      }
-      storageAccountType: {
-        value: storageAccountType
-      }
     }
   }
 }
@@ -168,8 +150,6 @@ param managedAppName = 'sampleBicepManagedApp'
 param mrgName = 'placeholder for managed resource group name'
 param appServicePlanName = 'demoAppServicePlan'
 param appServiceNamePrefix = 'demoApp'
-param storageAccountNamePrefix = 'demostg1234'
-param storageAccountType = 'Standard_LRS'
 ```
 
 You need to provide several parameters to deploy the managed application:
@@ -182,12 +162,10 @@ You need to provide several parameters to deploy the managed application:
 | `mrgName` | Unique name for the managed resource group that contains the application's deployed resources. The resource group is created when you deploy the managed application. To create a managed resource group name, run the commands that follow this parameter list and use the `$mrgname` value to replace the placeholder in the parameters file. |
 | `appServicePlanName` | Create a plan name. Maximum of 40 alphanumeric characters and hyphens. For example, _demoAppServicePlan_. App Service plan names must be unique within a resource group in your subscription. |
 | `appServiceNamePrefix` | Create a prefix for the plan name. Maximum of 47 alphanumeric characters or hyphens. For example, _demoApp_. During deployment, the prefix is concatenated with a unique string to create a name that's globally unique across Azure. |
-| `storageAccountNamePrefix` | Use only lowercase letters and numbers and a maximum of 11 characters. For example, _demostg1234_. During deployment, the prefix is concatenated with a unique string to create a name globally unique across Azure. |
-| `storageAccountType` | The options are Premium_LRS, Standard_LRS, and Standard_GRS. |
 
 You can run the following commands to create a name for the managed resource group.
 
-# [PowerShell](#tab/azure-powershell)
+# [Azure PowerShell](#tab/azure-powershell)
 
 ```azurepowershell
 $mrgprefix = 'mrg-sampleBicepManagedApplication-'
@@ -213,7 +191,7 @@ The `$mrgprefix` and `$mrgtimestamp` variables are concatenated and stored in th
 
 Use Azure PowerShell or Azure CLI to create a resource group and deploy the managed application.
 
-# [PowerShell](#tab/azure-powershell)
+# [Azure PowerShell](#tab/azure-powershell)
 
 ```azurepowershell
 New-AzResourceGroup -Name bicepApplicationGroup -Location westus
@@ -254,7 +232,7 @@ After the service catalog managed application is deployed, you have two new reso
 
 After the deployment is finished, you can check your managed application's status.
 
-# [PowerShell](#tab/azure-powershell)
+# [Azure PowerShell](#tab/azure-powershell)
 
 Run the following command to check the managed application's status.
 
@@ -288,7 +266,7 @@ az managedapp show --name sampleBicepManagedApp --resource-group bicepApplicatio
 
 You can view the resources deployed to the managed resource group.
 
-# [PowerShell](#tab/azure-powershell)
+# [Azure PowerShell](#tab/azure-powershell)
 
 To display the managed resource group's resources, run the following command. You created the `$mrgname` variable when you created the parameters.
 
@@ -350,7 +328,7 @@ When you're finished with the managed application, you can delete the resource g
 
 When you delete the _bicepApplicationGroup_ resource group, the managed application, managed resource group, and all the Azure resources are deleted.
 
-# [PowerShell](#tab/azure-powershell)
+# [Azure PowerShell](#tab/azure-powershell)
 
 The command prompts you to confirm that you want to remove the resource group.
 

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

@@ -2,7 +2,7 @@
 title: Deploy a service catalog managed application
 description: Describes how to deploy a service catalog's managed application for an Azure Managed Application using Azure PowerShell, Azure CLI, or Azure portal.
 ms.topic: quickstart
-ms.date: 06/24/2024
+ms.date: 09/22/2024
 ms.custom: engagement-fy23, devx-track-azurecli, devx-track-azurepowershell
 ---
 
@@ -26,7 +26,7 @@ The examples use the resource groups names created in the _quickstart to publish
 
 ### Get managed application definition
 
-# [PowerShell](#tab/azure-powershell)
+# [Azure PowerShell](#tab/azure-powershell)
 
 To get the managed application's definition with Azure PowerShell, run the following commands.
 
@@ -107,7 +107,7 @@ To get the managed application's definition from the Azure portal, use the follo
 
 ### Create resource group and parameters
 
-# [PowerShell](#tab/azure-powershell)
+# [Azure PowerShell](#tab/azure-powershell)
 
 Create a resource group for the managed application deployment.
 
@@ -140,17 +140,13 @@ For readability, the completed JSON string uses the backtick for line continuati
 
 ```powershell
 $params="{ `"appServicePlanName`": {`"value`":`"demoAppServicePlan`"}, `
-`"appServiceNamePrefix`": {`"value`":`"demoApp`"}, `
-`"storageAccountNamePrefix`": {`"value`":`"demostg1234`"}, `
-`"storageAccountType`": {`"value`":`"Standard_LRS`"} }"
+`"appServiceNamePrefix`": {`"value`":`"demoApp`"} }"
 ```
 
 The parameters to create the managed resources:
 
 - `appServicePlanName`: Create a plan name. Maximum of 40 alphanumeric characters and hyphens. For example, _demoAppServicePlan_. App Service plan names must be unique within a resource group in your subscription.
 - `appServiceNamePrefix`: Create a prefix for the plan name. Maximum of 47 alphanumeric characters or hyphens. For example, _demoApp_. During deployment, the prefix is concatenated with a unique string to create a name that's globally unique across Azure.
-- `storageAccountNamePrefix`: Use only lowercase letters and numbers and a maximum of 11 characters. For example, _demostg1234_. During deployment, the prefix is concatenated with a unique string to create a name globally unique across Azure. Although you're creating a prefix, the control checks for existing names in Azure and might post a validation message that the name already exists. If so, choose a different prefix.
-- `storageAccountType`: The options are Premium_LRS, Standard_LRS, and Standard_GRS.
 
 # [Azure CLI](#tab/azure-cli)
 
@@ -186,17 +182,13 @@ For readability, the completed JSON string uses the backslash for line continuat
 
 ```azurecli
 params="{ \"appServicePlanName\": {\"value\":\"demoAppServicePlan\"}, \
-\"appServiceNamePrefix\": {\"value\":\"demoApp\"}, \
-\"storageAccountNamePrefix\": {\"value\":\"demostg1234\"}, \
-\"storageAccountType\": {\"value\":\"Standard_LRS\"} }"
+\"appServiceNamePrefix\": {\"value\":\"demoApp\"} }"
 ```
 
 The parameters to create the managed resources:
 
 - `appServicePlanName`: Create a plan name. Maximum of 40 alphanumeric characters and hyphens. For example, _demoAppServicePlan_. App Service plan names must be unique within a resource group in your subscription.
 - `appServiceNamePrefix`: Create a prefix for the plan name. Maximum of 47 alphanumeric characters or hyphens. For example, _demoApp_. During deployment, the prefix is concatenated with a unique string to create a name that's globally unique across Azure.
-- `storageAccountNamePrefix`: Use only lowercase letters and numbers and a maximum of 11 characters. For example, _demostg1234_. During deployment, the prefix is concatenated with a unique string to create a name globally unique across Azure. Although you're creating a prefix, the control checks for existing names in Azure and might post a validation message that the name already exists. If so, choose a different prefix.
-- `storageAccountType`: The options are Premium_LRS, Standard_LRS, and Standard_GRS.
 
 # [Portal](#tab/azure-portal)
 
@@ -217,18 +209,11 @@ The parameters to create the managed resources:
    - **App Service plan name**: Create a plan name. Maximum of 40 alphanumeric characters and hyphens. For example, _demoAppServicePlan_. App Service plan names must be unique within a resource group in your subscription.
    - **App Service name prefix**: Create a prefix for the plan name. Maximum of 47 alphanumeric characters or hyphens. For example, _demoApp_. During deployment, the prefix is concatenated with a unique string to create a name that's globally unique across Azure.
 
-1. Enter a prefix for the storage account name and select the storage account type. Select **Next**.
-
-   :::image type="content" source="./media/deploy-service-catalog-quickstart/storage-settings.png" alt-text="Screenshot that shows the information needed to create a storage account.":::
-
-   - **Storage account name prefix**: Use only lowercase letters and numbers and a maximum of 11 characters. For example, _demostg1234_. During deployment, the prefix is concatenated with a unique string to create a name globally unique across Azure. Although you're creating a prefix, the control checks for existing names in Azure and might post a validation message that the name already exists. If so, choose a different prefix.
-   - **Storage account type**: Select **Change type** to choose a storage account type. The default is Standard_LRS. The other options are Premium_LRS, Standard_LRS, and Standard_GRS.
-
 ---
 
 ### Deploy the managed application
 
-# [PowerShell](#tab/azure-powershell)
+# [Azure PowerShell](#tab/azure-powershell)
 
 Run the following command to deploy the managed application.
 
@@ -294,7 +279,7 @@ After the service catalog managed application is deployed, you have two new reso
 
 After the deployment is finished, you can check your managed application's status.
 
-# [PowerShell](#tab/azure-powershell)
+# [Azure PowerShell](#tab/azure-powershell)
 
 Run the following command to check the managed application's status.
 
@@ -338,7 +323,7 @@ Select the managed application's name to get more information like the link to t
 
 You can view the resources deployed to the managed resource group.
 
-# [PowerShell](#tab/azure-powershell)
+# [Azure PowerShell](#tab/azure-powershell)
 
 To display the managed resource group's resources, run the following command. You created the `$mrgname` variable when you created the parameters.
 
@@ -415,7 +400,7 @@ The role assignment gives the application's publisher access to manage the stora
 
 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_.
 
-# [PowerShell](#tab/azure-powershell)
+# [Azure PowerShell](#tab/azure-powershell)
 
 The command prompts you to confirm that you want to remove the resource group.