Merge pull request #177380 from tfitzmac/1025existing

add NotFound error for existing

Author: PRMerger19

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

@@ -4,7 +4,7 @@ description: Describes the functions to use in a Bicep file to retrieve values a
 author: mumian
 ms.author: jgao
 ms.topic: conceptual
-ms.date: 09/30/2021
+ms.date: 10/25/2021
 ---
 
 # Resource functions for Bicep
@@ -517,8 +517,9 @@ resource stg 'Microsoft.Storage/storageAccounts@2019-06-01' existing = {
 output blobAddress string = stg.properties.primaryEndpoints.blob
 ```
 
-For more information, see [Reference resources](./compare-template-syntax.md#reference-resources) and the [JSON template reference function](../templates/template-functions-resource.md#reference).
+If you attempt to reference a resource that doesn't exist, you get the `NotFound` error and your deployment fails.
 
+For more information, see [Reference resources](./compare-template-syntax.md#reference-resources) and the [JSON template reference function](../templates/template-functions-resource.md#reference).
 
 ## resourceId
 

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

@@ -4,7 +4,7 @@ description: Describes how to declare resources to deploy in Bicep.
 author: mumian
 ms.author: jgao
 ms.topic: conceptual
-ms.date: 10/19/2021
+ms.date: 10/25/2021
 ---
 
 # Resource declaration in Bicep
@@ -285,6 +285,8 @@ 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.