fix links for moved files

Author: tfitzmac

articles/azure-resource-manager/bicep/best-practices.md

@@ -92,7 +92,7 @@ For more information about Bicep variables, see [Variables in Bicep](variables.m
 
 * Make sure you don't create outputs for sensitive data. Output values can be accessed by anyone who has access to the deployment history. They're not appropriate for handling secrets.
 
-* Instead of passing property values around through outputs, use the [existing keyword](resource-declaration.md#existing-resources) to look up properties of resources that already exist. It's a best practice to look up keys from other resources in this way instead of passing them around through outputs. You'll always get the most up-to-date data.
+* Instead of passing property values around through outputs, use the [existing keyword](existing-resource.md) to look up properties of resources that already exist. It's a best practice to look up keys from other resources in this way instead of passing them around through outputs. You'll always get the most up-to-date data.
 
 For more information about Bicep outputs, see [Outputs in Bicep](outputs.md).
 

articles/azure-resource-manager/bicep/conditional-resource-deployment.md

@@ -42,7 +42,7 @@ module dnsZone 'dnszones.bicep' = if (deployZone) {
 }
 ```
 
-Conditions may be used with dependency declarations. For [explicit dependencies](resource-declaration.md#dependencies), Azure Resource Manager automatically removes it from the required dependencies when the resource isn't deployed. For implicit dependencies, referencing a property of a conditional resource is allowed but may produce a deployment error.
+Conditions may be used with dependency declarations. For [explicit dependencies](resource-dependencies.md), Azure Resource Manager automatically removes it from the required dependencies when the resource isn't deployed. For implicit dependencies, referencing a property of a conditional resource is allowed but may produce a deployment error.
 
 ## New or existing resource
 

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

@@ -340,4 +340,4 @@ resource share 'Microsoft.Storage/storageAccounts/fileServices/shares@2021-06-01
 
 ## Next steps
 
-- To set dependencies on resources that are created in a loop, see [Resource dependencies](./resource-declaration.md#dependencies).
+- To set dependencies on resources that are created in a loop, see [Resource dependencies](resource-dependencies.md).

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

@@ -55,7 +55,7 @@ To deploy **more than one instance** of a module, add the `for` expression. You
 
 ::: code language="bicep" source="~/azure-docs-bicep-samples/syntax-samples/modules/iterative-definition.bicep" highlight="3" :::
 
-Like resources, modules are deployed in parallel unless they depend on other modules or resources. Typically, you don't need to set dependencies as they're determined implicitly. If you need to set an explicit dependency, you can add `dependsOn` to the module definition. To learn more about dependencies, see [Resource dependencies](resource-declaration.md#dependencies).
+Like resources, modules are deployed in parallel unless they depend on other modules or resources. Typically, you don't need to set dependencies as they're determined implicitly. If you need to set an explicit dependency, you can add `dependsOn` to the module definition. To learn more about dependencies, see [Resource dependencies](resource-dependencies.md).
 
 ::: code language="bicep" source="~/azure-docs-bicep-samples/syntax-samples/modules/dependsOn-definition.bicep" highlight="6-8" :::
 

articles/azure-resource-manager/bicep/scenarios-secrets.md

@@ -93,7 +93,7 @@ When you deploy your Azure resources by using a pipeline, you need to take care
   - [Azure Key Vault](../../key-vault/general/overview.md)
 - Bicep features
   - [Secure parameters](parameters.md#secure-parameters)
-  - [Referencing existing resources](resource-declaration.md#existing-resources)
+  - [Referencing existing resources](existing-resource.md)
   - [`getSecret` function](bicep-functions-resource.md#getsecret)
 - Quickstart templates
   - [Create a user-assigned managed identity and role assignments](https://github.com/Azure/azure-quickstart-templates/tree/master/modules/Microsoft.ManagedIdentity/user-assigned-identity-role-assignment/1.0)

articles/azure-resource-manager/bicep/scenarios-virtual-networks.md

@@ -31,7 +31,7 @@ When you redeploy the same Bicep file, the same deployment sequence occurs. Howe
 
 ### Access subnet resource IDs
 
-You often need to refer to a subnet's resource ID. When you use the `subnets` property to define your subnet, [you can use the `existing` keyword](resource-declaration.md#existing-resources) to also obtain a strongly typed reference to the subnet, and then access the subnet's `id` property:
+You often need to refer to a subnet's resource ID. When you use the `subnets` property to define your subnet, [you can use the `existing` keyword](existing-resource.md) to also obtain a strongly typed reference to the subnet, and then access the subnet's `id` property:
 
 ::: code language="bicep" source="~/azure-docs-bicep-samples/samples/scenarios-virtual-networks/vnet.bicep" range="7-42" highlight="26-28, 30-32, 35-36" :::
 

articles/azure-resource-manager/troubleshooting/create-troubleshooting-template.md

@@ -39,7 +39,7 @@ The following ARM template and Bicep file get information from an existing stora
 }
 ```
 
-In Bicep, use the `existing` keyword and run the deployment from the resource group where the storage account exists. Use `scope` to access a resource in a different resource group. For more information, see [existing resources](../bicep/resource-declaration.md#existing-resources).
+In Bicep, use the `existing` keyword and run the deployment from the resource group where the storage account exists. Use `scope` to access a resource in a different resource group. For more information, see [existing resources](../bicep/existing-resource.md).
 
 ```bicep
 param storageName string

articles/azure-resource-manager/troubleshooting/error-invalid-template.md

@@ -87,7 +87,7 @@ You may see this error in earlier deployments because you were limited to five t
 
 You receive this error when resources depend on each other in a way that prevents the deployment from starting. A combination of interdependencies makes two or more resource wait for other resources that are also waiting. For example, resource1 depends on resource3, resource2 depends on resource1, and resource3 depends on resource2. You can usually solve this problem by removing unnecessary dependencies.
 
-Bicep creates an implicit dependency when one resource uses the symbolic name of another resource. An explicit dependency using `dependsOn` usually isn't necessary. For more information, see Bicep [dependencies](../bicep/resource-declaration.md#dependencies).
+Bicep creates an implicit dependency when one resource uses the symbolic name of another resource. An explicit dependency using `dependsOn` usually isn't necessary. For more information, see Bicep [dependencies](../bicep/resource-dependencies.md).
 
 To solve a circular dependency:
 

articles/azure-resource-manager/troubleshooting/error-job-size-exceeded.md

@@ -33,7 +33,7 @@ Other template limits are:
 
 # [Bicep](#tab/bicep)
 
-Use an [implicit dependency](../bicep/resource-declaration.md#implicit-dependency) that's created when a resource references another resource by its symbolic name. For most deployments, it's not necessary to use `dependsOn` and create an [explicit dependency](../bicep/resource-declaration.md#explicit-dependency).
+Use an [implicit dependency](../bicep/resource-dependencies.md#implicit-dependency) that's created when a resource references another resource by its symbolic name. For most deployments, it's not necessary to use `dependsOn` and create an [explicit dependency](../bicep/resource-dependencies.md#explicit-dependency).
 
 # [JSON](#tab/json)
 

articles/azure-resource-manager/troubleshooting/error-not-found.md

@@ -51,7 +51,7 @@ For example, when you deploy a web app, the App Service plan must exist. If you
 
 # [Bicep](#tab/bicep)
 
-Use an [implicit dependency](../bicep/resource-declaration.md#implicit-dependency) rather than the [resourceId](../bicep/bicep-functions-resource.md#resourceid) function. The dependency is created using a resource's [symbolic name](../bicep/file.md#bicep-format) and ID property.
+Use an [implicit dependency](../bicep/resource-dependencies.md#implicit-dependency) rather than the [resourceId](../bicep/bicep-functions-resource.md#resourceid) function. The dependency is created using a resource's [symbolic name](../bicep/file.md#bicep-format) and ID property.
 
 For example, the web app's `serverFarmId` property uses `servicePlan.id` to create a dependency on the App Service plan.
 
@@ -67,7 +67,7 @@ resource servicePlan 'Microsoft.Web/serverfarms@2021-02-01' = {
   ...
 ```
 
-For most deployments, it's not necessary to use `dependsOn` to create an [explicit dependency](../bicep/resource-declaration.md#explicit-dependency).
+For most deployments, it's not necessary to use `dependsOn` to create an [explicit dependency](../bicep/resource-dependencies.md#explicit-dependency).
 
 Avoid setting dependencies that aren't needed. Unnecessary dependencies prolong the deployment's duration because resources aren't deployed in parallel. Also, you might create circular dependencies that block the deployment.
 
@@ -119,7 +119,7 @@ When you see dependency problems, you need to gain insight into the order of res
 
 # [Bicep](#tab/bicep)
 
-Bicep uses the symbolic name to create an [implicit dependency](../bicep/resource-declaration.md#implicit-dependency) on another resource. The [existing](../bicep/resource-declaration.md#existing-resources) keyword references a deployed resource. If an existing resource is in a different resource group than the resource you want to deploy, include [scope](../bicep/bicep-functions-scope.md#resource-group-example) and use the [resourceGroup](../bicep/bicep-functions-scope.md#resourcegroup) function.
+Bicep uses the symbolic name to create an [implicit dependency](../bicep/resource-dependencies.md#implicit-dependency) on another resource. The [existing](../bicep/existing-resource.md) keyword references a deployed resource. If an existing resource is in a different resource group than the resource you want to deploy, include [scope](../bicep/bicep-functions-scope.md#resource-group-example) and use the [resourceGroup](../bicep/bicep-functions-scope.md#resourcegroup) function.
 
 In this example, a web app is deployed that uses an existing App Service plan from another resource group.
 
@@ -158,7 +158,7 @@ The following example gets the resource ID for a resource that exists in a diffe
 
 # [Bicep](#tab/bicep)
 
-If you're deploying a resource with a [managed identity](../../active-directory/managed-identities-azure-resources/overview.md), you must wait until that resource is deployed before retrieving values on the managed identity. Use an [implicit dependency](../bicep/resource-declaration.md#implicit-dependency) for the resource that the identity is applied to. This approach ensures the resource and the managed identity are deployed before Resource Manager uses the dependency.
+If you're deploying a resource with a [managed identity](../../active-directory/managed-identities-azure-resources/overview.md), you must wait until that resource is deployed before retrieving values on the managed identity. Use an [implicit dependency](../bicep/resource-dependencies.md#implicit-dependency) for the resource that the identity is applied to. This approach ensures the resource and the managed identity are deployed before Resource Manager uses the dependency.
 
 You can get the principal ID and tenant ID for a managed identity that's applied to a virtual machine. For example, if a virtual machine resource has a symbolic name of `vm`, use the following syntax:
 
@@ -203,7 +203,7 @@ Or, to get the tenant ID for a managed identity that is applied to a virtual mac
 
 # [Bicep](#tab/bicep)
 
-You can use a resource's symbolic name to get values from a resource. You can reference a storage account in the same resource group or another resource group using a symbolic name. To get a value from a deployed resource, use the [existing](../bicep/resource-declaration.md#existing-resources) keyword. If a resource is in a different resource group, use `scope` with the [resourceGroup](../bicep/bicep-functions-scope.md#resourcegroup) function. For most cases, the [reference](../bicep/bicep-functions-resource.md#reference) function isn't needed.
+You can use a resource's symbolic name to get values from a resource. You can reference a storage account in the same resource group or another resource group using a symbolic name. To get a value from a deployed resource, use the [existing](../bicep/existing-resource.md) keyword. If a resource is in a different resource group, use `scope` with the [resourceGroup](../bicep/bicep-functions-scope.md#resourcegroup) function. For most cases, the [reference](../bicep/bicep-functions-resource.md#reference) function isn't needed.
 
 The following example references an existing storage account in a different resource group.