split resource content

Author: tfitzmac

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

@@ -1,19 +1,19 @@
 ---
 title: Reference existing resource in Bicep
 description: Describes how to reference a resource that already exists.
-author: mumian
-ms.author: jgao
 ms.topic: conceptual
-ms.date: 02/03/2022
+ms.date: 02/04/2022
 ---
 
-# Existing resources
+# Existing resources in Bicep
 
-To reference a resource that's outside of the current Bicep file, use the `existing` keyword in a resource declaration.
+To reference an existing resource that isn't deployed in your current Bicep file, declare the resource with the `existing` keyword. Use the `existing` keyword when you're deploying a resource that needs to get a value from an existing resource. You access the existing resource's properties through its symbolic name.
 
-## Syntax
+The resource isn't redeployed when referenced with the `existing` keyword.
 
-When using the `existing` keyword, provide the `name` of the resource. The following example gets an existing storage account in the same resource group as the current deployment.
+## Same scope
+
+The following example gets an existing storage account in the same resource group as the current deployment. Notice that you provide only the name of the existing resource. The properties are available through the symbolic name.
 
 ```bicep
 resource stg 'Microsoft.Storage/storageAccounts@2019-06-01' existing = {
@@ -23,7 +23,9 @@ resource stg 'Microsoft.Storage/storageAccounts@2019-06-01' existing = {
 output blobEndpoint string = stg.properties.primaryEndpoints.blob
 ```
 
-Optionally, you can set the `scope` property to access a resource in a different scope. The following example references an existing storage account in a different resource group.
+## Different scope
+
+Set the `scope` property to access a resource in a different scope. The following example references an existing storage account in a different resource group.
 
 ```bicep
 resource stg 'Microsoft.Storage/storageAccounts@2019-06-01' existing = {
@@ -34,12 +36,12 @@ resource stg 'Microsoft.Storage/storageAccounts@2019-06-01' existing = {
 output blobEndpoint string = stg.properties.primaryEndpoints.blob
 ```
 
-If you attempt to reference a resource that doesn't exist, you get the `NotFound` error and your deployment fails.
-
 For more information about setting the scope, see [Scope functions for Bicep](bicep-functions-scope.md).
 
-The preceding examples don't deploy the storage account. Instead, you can access properties on the existing resource by using the symbolic name.
+## Troubleshooting
+
+If you attempt to reference a resource that doesn't exist, you get the `NotFound` error and your deployment fails. Check the name and scope of the resource you're trying to reference.
 
 ## Next steps
 
-- To conditionally deploy a resource, see [Conditional deployment in Bicep](./conditional-resource-deployment.md).
+For the syntax to deploy a resource, see [Resource declaration in Bicep](resource-declaration.md).

articles/azure-resource-manager/bicep/media/resource-declaration/bicep-resource-visualizer.png renamed to articles/azure-resource-manager/bicep/media/resource-dependencies/bicep-resource-visualizer.png

@@ -1,10 +1,8 @@
 ---
 title: Declare resources in Bicep
 description: Describes how to declare resources to deploy in Bicep.
-author: mumian
-ms.author: jgao
 ms.topic: conceptual
-ms.date: 11/12/2021
+ms.date: 02/04/2022
 ---
 
 # Resource declaration in Bicep
@@ -187,111 +185,8 @@ resource stg 'Microsoft.Storage/storageAccounts@2019-06-01' = {
 }
 ```
 
-## Dependencies
-
-When deploying resources, you may need to make sure some resources exist before other resources. For example, you need a logical SQL server before deploying a database. You establish this relationship by marking one resource as dependent on the other resource. Order of resource deployment can be influenced in two ways: [implicit dependency](#implicit-dependency) and [explicit dependency](#explicit-dependency)
-
-Azure Resource Manager evaluates the dependencies between resources, and deploys them in their dependent order. When resources aren't dependent on each other, Resource Manager deploys them in parallel. You only need to define dependencies for resources that are deployed in the same Bicep file.
-
-### Implicit dependency
-
-An implicit dependency is created when one resource declaration references another resource in the same deployment. For example, *dnsZone* is referenced by the second resource definition in the following example:
-
-```bicep
-resource dnsZone 'Microsoft.Network/dnszones@2018-05-01' = {
-  name: 'myZone'
-  location: 'global'
-}
-
-resource otherResource 'Microsoft.Example/examples@2020-06-01' = {
-  name: 'exampleResource'
-  properties: {
-    // get read-only DNS zone property
-    nameServers: dnsZone.properties.nameServers
-  }
-}
-```
-
-A nested resource also has an implicit dependency on its containing resource.
-
-```bicep
-resource myParent 'My.Rp/parentType@2020-01-01' = {
-  name: 'myParent'
-  location: 'West US'
-
-  // depends on 'myParent' implicitly
-  resource myChild 'childType' = {
-    name: 'myChild'
-  }
-}
-```
-
-When an implicit dependency exists, **don't add an explicit dependency**.
-
-For more information about nested resources, see [Set name and type for child resources in Bicep](./child-resource-name-type.md).
-
-### Explicit dependency
-
-An explicit dependency is declared with the `dependsOn` property. The property accepts an array of resource identifiers, so you can specify more than one dependency.
-
-The following example shows a DNS zone named `otherZone` that depends on a DNS zone named `dnsZone`:
-
-```bicep
-resource dnsZone 'Microsoft.Network/dnszones@2018-05-01' = {
-  name: 'demoeZone1'
-  location: 'global'
-}
-
-resource otherZone 'Microsoft.Network/dnszones@2018-05-01' = {
-  name: 'demoZone2'
-  location: 'global'
-  dependsOn: [
-    dnsZone
-  ]
-}
-```
-
-While you may be inclined to use `dependsOn` to map relationships between your resources, it's important to understand why you're doing it. For example, to document how resources are interconnected, `dependsOn` isn't the right approach. You can't query which resources were defined in the `dependsOn` element after deployment. Setting unnecessary dependencies slows deployment time because Resource Manager can't deploy those resources in parallel.
-
-Even though explicit dependencies are sometimes required, the need for them is rare. In most cases, you can use a symbolic name to imply the dependency between resources. If you find yourself setting explicit dependencies, you should consider if there's a way to remove it.
-
-### Visualize dependencies
-
-Visual Studio Code provides a tool for visualizing the dependencies. Open a Bicep file in Visual Studio Code, and then select the visualizer button on the upper left corner.  The following screenshot shows the dependencies of a virtual machine.
-
-:::image type="content" source="./media/resource-declaration/bicep-resource-visualizer.png" alt-text="Screenshot of Visual Studio Code Bicep resource visualizer":::
-
-## Existing resources
-
-To reference a resource that's outside of the current Bicep file, use the `existing` keyword in a resource declaration.
-
-When using the `existing` keyword, provide the `name` of the resource. The following example gets an existing storage account in the same resource group as the current deployment.
-
-```bicep
-resource stg 'Microsoft.Storage/storageAccounts@2019-06-01' existing = {
-  name: 'examplestorage'
-}
-
-output blobEndpoint string = stg.properties.primaryEndpoints.blob
-```
-
-Optionally, you can set the `scope` property to access a resource in a different scope. The following example references an existing storage account in a different resource group.
-
-```bicep
-resource stg 'Microsoft.Storage/storageAccounts@2019-06-01' existing = {
-  name: 'examplestorage'
-  scope: resourceGroup(exampleRG)
-}
-
-output blobEndpoint string = stg.properties.primaryEndpoints.blob
-```
-
-If you attempt to reference a resource that doesn't exist, you get the `NotFound` error and your deployment fails.
-
-For more information about setting the scope, see [Scope functions for Bicep](bicep-functions-scope.md).
-
-The preceding examples don't deploy the storage account. Instead, you can access properties on the existing resource by using the symbolic name.
-
 ## Next steps
 
 - To conditionally deploy a resource, see [Conditional deployment in Bicep](./conditional-resource-deployment.md).
+- To reference an existing resource, see [Existing resources in Bicep](existing-resource.md).
+- To learn about how deployment order is determined, see [Resource dependencies in Bicep](resource-dependencies.md).

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

@@ -1,24 +1,22 @@
 ---
 title: Set resource dependencies in Bicep
 description: Describes how to specify the order resources are deployed.
-author: mumian
-ms.author: jgao
 ms.topic: conceptual
-ms.date: 02/03/2022
+ms.date: 02/04/2022
 ---
 
 # Resource dependencies in Bicep
 
-When deploying resources, you may need to make sure some resources exist before other resources. For example, you need a logical SQL server before deploying a database. You establish this relationship by marking one resource as dependent on the other resource. Order of resource deployment can be influenced in two ways: [implicit dependency](#implicit-dependency) and [explicit dependency](#explicit-dependency)
+When deploying resources, you may need to make sure some resources are deployed before other resources. For example, you need a logical SQL server before deploying a database. You establish this relationship by marking one resource as dependent on the other resource. The order of resource deployment is determined in two ways: [implicit dependency](#implicit-dependency) and [explicit dependency](#explicit-dependency)
 
 Azure Resource Manager evaluates the dependencies between resources, and deploys them in their dependent order. When resources aren't dependent on each other, Resource Manager deploys them in parallel. You only need to define dependencies for resources that are deployed in the same Bicep file.
 
 ## Implicit dependency
 
-An implicit dependency is created when one resource declaration references another resource in the same deployment. For example, *dnsZone* is referenced by the second resource definition in the following example:
+An implicit dependency is created when one resource declaration references another resource in the same deployment. In the following example, `otherResource` gets a property from  `exampleDnsZone`. The resource named `otherResource` is implicitly dependent on `exampleDnsZone`.
 
 ```bicep
-resource dnsZone 'Microsoft.Network/dnszones@2018-05-01' = {
+resource exampleDnsZone 'Microsoft.Network/dnszones@2018-05-01' = {
   name: 'myZone'
   location: 'global'
 }
@@ -27,7 +25,7 @@ resource otherResource 'Microsoft.Example/examples@2020-06-01' = {
   name: 'exampleResource'
   properties: {
     // get read-only DNS zone property
-    nameServers: dnsZone.properties.nameServers
+    nameServers: exampleDnsZone.properties.nameServers
   }
 }
 ```
@@ -39,7 +37,7 @@ resource myParent 'My.Rp/parentType@2020-01-01' = {
   name: 'myParent'
   location: 'West US'
 
-  // depends on 'myParent' implicitly
+  // implicit dependency on 'myParent'
   resource myChild 'childType' = {
     name: 'myChild'
   }
@@ -77,10 +75,10 @@ Even though explicit dependencies are sometimes required, the need for them is r
 
 ## Visualize dependencies
 
-Visual Studio Code provides a tool for visualizing the dependencies. Open a Bicep file in Visual Studio Code, and then select the visualizer button on the upper left corner.  The following screenshot shows the dependencies of a virtual machine.
+Visual Studio Code provides a tool for visualizing the dependencies. Open a Bicep file in Visual Studio Code, and select the visualizer button on the upper left corner.  The following screenshot shows the dependencies of a virtual machine.
 
-:::image type="content" source="./media/resource-declaration/bicep-resource-visualizer.png" alt-text="Screenshot of Visual Studio Code Bicep resource visualizer":::
+:::image type="content" source="./media/resource-dependencies/bicep-resource-visualizer.png" alt-text="Screenshot of Visual Studio Code Bicep resource visualizer":::
 
 ## Next steps
 
-- To conditionally deploy a resource, see [Conditional deployment in Bicep](./conditional-resource-deployment.md).
+For the syntax to deploy a resource, see [Resource declaration in Bicep](resource-declaration.md).