Skip to content

Commit 28a3aef

Browse files
authored
Adding note that AMA does not support Bicep languageVersion 2.0
1 parent 00d376d commit 28a3aef

File tree

4 files changed

+12
-0
lines changed

4 files changed

+12
-0
lines changed

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,9 @@ To complete the tasks in this article, you need the following items:
3232

3333
## Create a Bicep file
3434

35+
> [!Note]
36+
> Azure Managed Applications only supports ARM templates using languageVersion 1.0 and **does not** support languageVersion 2.0. Refer to the [ARM Template documentation](https://learn.microsoft.com/azure/azure-resource-manager/templates/syntax#languageversion-20) to see what features will automatically enable version 2.0.
37+
3538
Every managed application definition includes a file named _mainTemplate.json_. The template defines the Azure resources to deploy and is no different than a regular ARM template. You can develop the template using Bicep and then convert the Bicep file to JSON.
3639

3740
Open Visual Studio Code, create a file with the case-sensitive name _mainTemplate.bicep_ and save it.

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -33,6 +33,9 @@ To complete this quickstart, you need the following items:
3333

3434
## Create the ARM template
3535

36+
> [!Note]
37+
> Azure Managed Applications only supports ARM templates using languageVersion 1.0 and **does not** support languageVersion 2.0. Refer to the [ARM Template documentation](https://learn.microsoft.com/azure/azure-resource-manager/templates/syntax#languageversion-20) to see what features will automatically enable version 2.0.
38+
3639
Every managed application definition includes a file named _mainTemplate.json_. The template defines the Azure resources to deploy and is no different than a regular ARM template.
3740

3841
Open Visual Studio Code, create a file with the case-sensitive name _mainTemplate.json_ and save it.

articles/azure-resource-manager/managed-applications/publish-service-catalog-bring-your-own-storage.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,9 @@ To complete this quickstart, you need the following items:
3434

3535
## Create the ARM template
3636

37+
> [!Note]
38+
> Azure Managed Applications only supports ARM templates using languageVersion 1.0 and **does not** support languageVersion 2.0. Refer to the [ARM Template documentation](https://learn.microsoft.com/azure/azure-resource-manager/templates/syntax#languageversion-20) to see what features will automatically enable version 2.0.
39+
3740
Every managed application definition includes a file named _mainTemplate.json_. The template defines the Azure resources to deploy and is no different than a regular ARM template.
3841

3942
Open Visual Studio Code, create a file with the case-sensitive name _mainTemplate.json_ and save it.

articles/azure-resource-manager/managed-applications/reference-main-template-artifact.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,9 @@ This article is a reference for a _mainTemplate.json_ artifact in Azure Managed
1111

1212
## Deployment template
1313

14+
> [!Note]
15+
> Azure Managed Applications only supports ARM templates using languageVersion 1.0 and **does not** support languageVersion 2.0. Refer to the [ARM Template documentation](https://learn.microsoft.com/azure/azure-resource-manager/templates/syntax#languageversion-20) to see what features will automatically enable version 2.0.
16+
1417
The following JSON shows an example of _mainTemplate.json_ file for Azure Managed Applications:
1518

1619
```json

0 commit comments

Comments
 (0)