Skip to content

Commit 3a7607d

Browse files
authored
Merge pull request #174707 from mumian/1005-bicep-module-api-version
update api version
2 parents 8a1a80a + d76ac3c commit 3a7607d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/azure-resource-manager/bicep/modules.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Describes how to define and consume a module, and how to use module
44
author: mumian
55
ms.author: jgao
66
ms.topic: conceptual
7-
ms.date: 09/14/2021
7+
ms.date: 10/05/2021
88
---
99

1010
# Use Bicep modules
@@ -134,7 +134,7 @@ param namePrefix string
134134
param location string = deployment().location
135135
136136
var resourceGroupName = '${namePrefix}rg'
137-
resource myResourceGroup 'Microsoft.Resources/resourceGroups@2020-01-01' = {
137+
resource myResourceGroup 'Microsoft.Resources/resourceGroups@2021-04-01' = {
138138
name: resourceGroupName
139139
location: location
140140
scope: subscription()
@@ -184,7 +184,7 @@ module storage2 'storageAccount.bicep' = {
184184
}
185185
```
186186

187-
The scope property must be set to a valid scope object. If your Bicep file deploys a resource group, subscription, or management group, you can set the scope for a module to the symbolic name for that resource. Or, you can use the scope functions to get a valid scope.
187+
The scope property must be set to a valid scope object. If your Bicep file deploys a resource group, subscription, or management group, you can set the scope for a module to the symbolic name for that resource. Or, you can use the scope functions to get a valid scope.
188188

189189
Those functions are:
190190

0 commit comments

Comments
 (0)