Skip to content

Commit 6c53f0a

Browse files
authored
Merge pull request #204113 from davidsmatlak/ds-bicep-note-0708
Adds note about Bicep in managed apps
2 parents 4e1f7ad + f33bcfa commit 6c53f0a

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

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

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -4,29 +4,32 @@ description: Shows how to create an Azure managed application that is intended f
44
author: davidsmatlak
55
ms.topic: quickstart
66
ms.custom: subject-armqs, devx-track-azurecli, devx-track-azurepowershell, subject-rbac-steps, mode-api, mode-arm
7-
ms.date: 06/23/2022
7+
ms.date: 07/08/2022
88
ms.author: davidsmatlak
99
---
1010

1111
# Quickstart: Create and publish a managed application definition
1212

13-
This quickstart provides an introduction to working with [Azure Managed Applications](overview.md). You can create and publish a managed application that is intended for members of your organization.
13+
This quickstart provides an introduction to working with [Azure Managed Applications](overview.md). You can create and publish a managed application that's intended for members of your organization.
1414

1515
To publish a managed application to your service catalog, you must:
1616

17-
- Create a template that defines the resources to deploy with the managed application.
17+
- Create an Azure Resource Manager template (ARM template) that defines the resources to deploy with the managed application.
1818
- Define the user interface elements for the portal when deploying the managed application.
1919
- Create a _.zip_ package that contains the required template files.
2020
- Decide which user, group, or application needs access to the resource group in the user's subscription.
2121
- Create the managed application definition that points to the _.zip_ package and requests access for the identity.
2222

23+
> [!NOTE]
24+
> Bicep files can't be used in a managed application. You must convert a Bicep file to ARM template JSON with the Bicep [build](../bicep/bicep-cli.md#build) command.
25+
2326
## Create the ARM template
2427

2528
Every managed application definition includes a file named _mainTemplate.json_. In it, you define the Azure resources to deploy. The template is no different than a regular ARM template.
2629

2730
Create a file named _mainTemplate.json_. The name is case-sensitive.
2831

29-
Add the following JSON to your file. It defines the parameters for creating a storage account, and specifies the properties for the storage account.
32+
Add the following JSON and save the file. It defines the parameters for creating a storage account, and specifies the properties for the storage account.
3033

3134
```json
3235
{
@@ -69,8 +72,6 @@ Add the following JSON to your file. It defines the parameters for creating a st
6972
}
7073
```
7174

72-
Save the _mainTemplate.json_ file.
73-
7475
## Define your create experience
7576

7677
As a publisher, you define the portal experience for creating the managed application. The _createUiDefinition.json_ file generates the portal interface. You define how users provide input for each parameter using [control elements](create-uidefinition-elements.md) including drop-downs, text boxes, and password boxes.

0 commit comments

Comments
 (0)