edits

Author: v-albemi

learn-pr/azure/child-extension-bicep-templates/4-exercise-define-child-resources.yml

@@ -1,18 +1,18 @@
-### YamlMime:ModuleUnit
-uid: learn.azure.child-extension-bicep-templates.exercise-define-child-resources
-title: Exercise - Define child resources
-sandbox: true
-metadata:
-  unitType: exercise
-  title: Exercise - Define child resources
-  description: Learn how to create child resources in your Bicep template.
-  ms.date: 01/31/2025
-  author: mumian
-  ms.author: jgao
-  ms.topic: unit
-  ms.custom: devx-track-bicep
-  zone_pivot_groups: azure-shell-interface
-durationInMinutes: 10
-content: |
-  [!include[](includes/4-exercise-define-child-resources.md)]
-
+### YamlMime:ModuleUnit
+uid: learn.azure.child-extension-bicep-templates.exercise-define-child-resources
+title: Exercise - Define child resources
+sandbox: true
+metadata:
+  unitType: exercise
+  title: Exercise - Define child resources
+  description: Learn how to create child resources in your Bicep template.
+  ms.date: 05/28/2025
+  author: mumian
+  ms.author: jgao
+  ms.topic: unit
+  ms.custom: devx-track-bicep
+  zone_pivot_groups: azure-shell-interface
+durationInMinutes: 10
+content: |
+  [!include[](includes/4-exercise-define-child-resources.md)]
+

learn-pr/azure/child-extension-bicep-templates/5-define-extension-resources.yml

@@ -1,17 +1,17 @@
-### YamlMime:ModuleUnit
-uid: learn.azure.child-extension-bicep-templates.define-extension-resources
-title: Define extension resources
-metadata:
-  unitType: learning-content
-  title: Define extension resources
-  description: Learn how to create extension resources in your Bicep template.
-  ms.date: 01/31/2025
-  author: mumian
-  ms.author: jgao
-  ms.topic: unit
-  ms.custom:
-    - devx-track-bicep
-durationInMinutes: 2
-content: |
-  [!include[](includes/5-define-extension-resources.md)]
-
+### YamlMime:ModuleUnit
+uid: learn.azure.child-extension-bicep-templates.define-extension-resources
+title: Define extension resources
+metadata:
+  unitType: learning-content
+  title: Define extension resources
+  description: Learn how to create extension resources in your Bicep template.
+  ms.date: 05/28/2025
+  author: mumian
+  ms.author: jgao
+  ms.topic: unit
+  ms.custom:
+    - devx-track-bicep
+durationInMinutes: 2
+content: |
+  [!include[](includes/5-define-extension-resources.md)]
+

learn-pr/azure/child-extension-bicep-templates/includes/4-exercise-define-child-resources.md

@@ -21,7 +21,7 @@ First, you create a new Bicep template that contains an Azure Cosmos DB account.
 
 1. Save the empty file so that Visual Studio Code loads the Bicep tooling.
 
-   You can either select **File** > **Save As** or select <kbd>Ctrl+S</kbd> in Windows (<kbd>⌘+S</kbd> on macOS). Be sure to remember where you saved the file. For example, you might want to create a *scripts* folder to save it in.
+   You can either select **File** > **Save As** or select <kbd>Ctrl+S</kbd> in Windows (<kbd>⌘+S</kbd> on macOS). Be sure to remember where you saved the file. For example, you might want to create a *templates* folder to save it in.
 
 1. Add the following content to the file. It's a good idea to enter it manually rather than copy and paste it. That way, you can see how the tooling helps you write your Bicep files.
 
@@ -79,7 +79,7 @@ Now you add another child resource. This time, you add it as a nested resource i
 
 ## Verify your Bicep file
 
-After you've completed all of the preceding changes, your _main.bicep_ file should look like this example:
+After you complete the preceding steps, your _main.bicep_ file should look like this example:
 
 :::code language="bicep" source="code/4-complete.bicep" :::
 
@@ -127,7 +127,7 @@ New-AzResourceGroupDeployment -Name main -TemplateFile main.bicep
 
 1. Select **<rgn>[sandbox resource group name]</rgn>**.
 
-1. In **Overview**, you can see that one deployment succeeded.
+1. In the **Overview** pane, you can see that one deployment succeeded.
 
     :::image type="content" source="../media/4-deployment-succeeded.png" alt-text="Screenshot of the Azure portal interface for the resource group overview, with the deployments section showing that one succeeded." border="true":::
 

learn-pr/azure/child-extension-bicep-templates/includes/5-define-extension-resources.md

@@ -16,7 +16,7 @@ For example, consider a lock, which can be used to prevent the deletion or modif
 
 ## How are extension resources defined?
 
-In Bicep, you define an extension resource in mostly the same way as a normal resource. However, you add the `scope` property to tell Bicep that the resource should be attached to another resource defined elsewhere in the Bicep file. You use the resource's symbolic name to refer to it. For example, here's the definition of an Azure Cosmos DB account that we created previously:
+In Bicep, you mostly define an extension resource in the same way as you define a normal resource. However, you add the `scope` property to inform Bicep that the resource should be attached to another resource that's defined elsewhere in the Bicep file. You use the resource's symbolic name to refer to it. For example, here's the definition of an Azure Cosmos DB account that you created previously:
 
 ```bicep
 resource cosmosDBAccount 'Microsoft.DocumentDB/databaseAccounts@2024-05-15' = {
@@ -28,24 +28,24 @@ resource cosmosDBAccount 'Microsoft.DocumentDB/databaseAccounts@2024-05-15' = {
 }
 ```
 
-Let's add a resource lock, which prevents anybody from deleting the Azure Cosmos DB account:
+You can add a resource lock, which prevents anybody from deleting the Azure Cosmos DB account:
 
 :::code language="bicep" source="code/5-scope.bicep" highlight="2":::
 
-Notice that the example uses the `scope` property with the Azure Cosmos DB account's symbolic name. This property setting tells Bicep to deploy the resource lock onto the Azure Cosmos DB account, which means that it can no longer be deleted.
+Notice that the example uses the `scope` property with the Azure Cosmos DB account's symbolic name. This property setting informs Bicep to deploy the resource lock onto the Azure Cosmos DB account, so the account can no longer be deleted.
 
 ## Extension resource IDs
 
-An extension resource has a slightly different ID than other resources. It consists of its parent resource ID, the separator `/providers/`, and the extension resource ID.
+An ID for an extension resource is slightly different than IDs for other resources. It consists of its parent resource ID, the separator `/providers/`, and the extension resource ID.
 
-Let's say you deployed the previously mentioned Azure Cosmos DB account, and the account was named `toyrnd`. Here's what the lock's resource ID would look like:
+Say you deployed the previously mentioned Azure Cosmos DB account, and the account was named `toyrnd`. Here's what the lock's resource ID would look like:
 
 ```
-/subscriptions/A123b4567c-1234-1a2b-2b1a-1234abc12345/resourceGroups/ToyDevelopment/providers/Microsoft.DocumentDB/databaseAccounts/toyrnd/providers/Microsoft.Authorization/locks/DontDelete
+/subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourceGroups/ToyDevelopment/providers/Microsoft.DocumentDB/databaseAccounts/toyrnd/providers/Microsoft.Authorization/locks/DontDelete
 ```
 
 Here's a visual representation:
 
-:::image type="content" source="../media/5-extension-resource-id.png" alt-text="Extension resource ID for a resource lock applied to an Azure Cosmos DB account, split with the key-value pair on a separate line." border="false":::
+:::image type="content" source="../media/5-extension-resource-id.png" alt-text="Diagram that shows an extension resource ID for a resource lock that's applied to an Azure Cosmos DB account. Each element of the ID appears on a separate line." border="false":::
 
-If you see a resource ID that starts with a normal resource ID and then adds `/providers/` and another resource type and name, it means that you're looking at an extension resource ID.
+If you see a resource ID that starts with a normal resource ID and then includes `/providers/` and another resource type and name, you're looking at an extension resource ID.

learn-pr/azure/child-extension-bicep-templates/includes/6-work-with-existing-resources.md

@@ -10,7 +10,7 @@ Bicep provides the `existing` keyword for you to use in these situations.
 
 ## Refer to existing resources
 
-Within a Bicep file, you can define a resource that already exists. The declaration looks similar to a normal resource definition, but there are a few key differences. In the following example of an existing resource definition, the definition refers to a storage account named `toydesigndocs`. The storage account is in the same resource group that your Bicep template is deploying resources to.
+In a Bicep file, you can define a resource that already exists. The declaration looks similar to a normal resource definition, but there are a few key differences. In the following example of an existing resource definition, the definition refers to a storage account named `toydesigndocs`. The storage account is in the same resource group that your Bicep template is deploying resources to.
 
 ```bicep
 resource storageAccount 'Microsoft.Storage/storageAccounts@2023-05-01' existing = {
@@ -23,15 +23,15 @@ Let's look closely at what makes up this definition:
 - As you would with a normal resource, you include the `resource` keyword, a symbolic name, and the resource type and API version.
 
   > [!NOTE]
-  > Remember, the symbolic name is used only within this Bicep file. If you create this resource by using one Bicep file and refer to it by using the `existing` resource in a different Bicep file, the symbolic names don't have to match.
+  > Remember, the symbolic name is used only in the current Bicep file. If you create this resource by using one Bicep file and refer to it by using the `existing` resource in a different Bicep file, the symbolic names don't have to match.
 
-- The `existing` keyword indicates to Bicep that this resource definition is a reference to an already-created resource, and that Bicep shouldn't try to deploy it.
+- The `existing` keyword indicates to Bicep that the resource definition is a reference to a resource that's arleady created, and that Bicep shouldn't try to deploy it.
 - The `name` property is the Azure resource name of the storage account that was previously deployed.
-- You don't need to specify the `location`, `sku`, or `properties`, because the template doesn't deploy the resource. It merely references an existing resource. Think of it as a placeholder resource.
+- You don't need to specify the `location`, `sku`, or `properties` because the template doesn't deploy the resource. It just references an existing resource. Think of it as a placeholder resource.
 
 ### Refer to child resources
 
-You can refer to an existing child resource, too. Use the same kind of syntax that you used when you deployed a child resource. The following example shows how you can refer to an existing subnet, which is a child resource of a virtual network. The example uses a nested child resource, as shown here:
+You can also refer to an existing child resource. Use the same kind of syntax that you used when you deployed a child resource. The following example shows how you can refer to an existing subnet, which is a child resource of a virtual network. The example uses a nested child resource:
 
 :::code language="bicep" source="code/6-child-existing.bicep" highlight="4-6":::
 
@@ -45,17 +45,17 @@ output managementSubnetResourceId string = vnet::managementSubnet.id
 
 ### Refer to resources outside the resource group
 
-Often, you need to refer to resources in a different resource group. For example, if you have a virtual network in a centralized resource group, you might want to deploy a virtual machine into that virtual network in its own resource group. You can use the `scope` keyword to refer to existing resources in a different resource group. The following example shows how you could refer to a virtual network named `toy-design-vnet` within the `networking-rg` resource group:
+You often need to refer to resources in a different resource group. For example, if you have a virtual network in a centralized resource group, you might want to deploy a virtual machine into that virtual network in its own resource group. You can use the `scope` keyword to refer to existing resources in a different resource group. The following example shows how you can refer to a virtual network named `toy-design-vnet` in the `networking-rg` resource group:
 
 :::code language="bicep" source="code/6-resource-group-scope.bicep" highlight="2":::
 
 Notice that the `scope` uses the `resourceGroup()` keyword to refer to the resource group that contains the virtual network.
 
-You can even refer to resources within a different Azure subscription, as long as the subscription is within your Microsoft Entra tenant. If your networking team provisions the virtual network in a different subscription, the template could refer to it, as in this example:
+You can even refer to resources within a different Azure subscription, as long as the subscription is within your Microsoft Entra tenant. If your networking team provisions the virtual network in a different subscription, the template can refer to it as shown in this example:
 
 :::code language="bicep" source="code/6-subscription-scope.bicep" highlight="2":::
 
-Notice that the `scope` uses the `resourceGroup()` keyword to refer to the Azure subscription ID (`A123b4567c-1234-1a2b-2b1a-1234abc12345`) and resource group name that contains the virtual network.
+Notice that the `scope` uses the `resourceGroup()` keyword to refer to the Azure subscription ID (`aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e`) and resource group name that contains the virtual network.
 
 Now that you understand how to refer to existing resources, let's look at how you can use this capability in your templates.
 

learn-pr/azure/child-extension-bicep-templates/includes/code/6-subscription-scope.bicep

@@ -1,4 +1,4 @@
 resource vnet 'Microsoft.Network/virtualNetworks@2024-05-01' existing = {
-  scope: resourceGroup('A123b4567c-1234-1a2b-2b1a-1234abc12345', 'networking-rg')
+  scope: resourceGroup('aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e', 'networking-rg')
   name: 'toy-design-vnet'
 }