Merge pull request #301870 from mumian/0625-bcp139

update the BCP139 samples

Author: v-dirichards

articles/azure-resource-manager/bicep/diagnostics/bcp139.md

@@ -3,7 +3,7 @@ title: BCP139
 description: A resource's scope must match the scope of the Bicep file for it to be deployable. You must use modules to deploy resources to a different scope.
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 02/12/2025
+ms.date: 06/25/2025
 ---
 
 # Bicep diagnostic code - BCP139
@@ -32,13 +32,14 @@ To deploy resources to a scope that isn't the target scope, add a `module`.
 The following example deploys a storage account resource to a different resource group in the same subscription. The example raises the diagnostic because the `module` declaration type isn't used:
 
 ```bicep
-param otherResourceGroup string
+param targetResourceGroup string
+param storageAccountName string 
 param location string 
 
 // resource deployed to a different resource group in the same subscription
 resource storage 'Microsoft.Storage/storageAccounts@2023-05-01' = {
-  name: uniqueString(resourceGroup().id)
-  scope: resourceGroup(otherResourceGroup)
+  name: storageAccountName
+  scope: resourceGroup(targetResourceGroup)
   location: location
   sku: {
     name: 'Standard_LRS'
@@ -50,12 +51,17 @@ resource storage 'Microsoft.Storage/storageAccounts@2023-05-01' = {
 You can fix the diagnostic by using the `module` declaration type:
 
 ```bicep
-param otherResourceGroup string
-
-// module deployed to a different resource group in the same subscription
-module exampleModule 'module.bicep' = {
-  name: 'deployStorageToAnotherRG'
-  scope: resourceGroup(otherResourceGroup)
+param targetResourceGroup string 
+param storageAccountName string = uniqueString(resourceGroup().id)
+param location string = 'eastus'
+
+module storageModule './module.bicep' = {
+  name: 'deployStorage'
+  scope: resourceGroup(targetResourceGroup)
+  params: {
+    storageAccountName: storageAccountName
+    location: location
+  }
 }
 ```
 
@@ -64,13 +70,15 @@ The following example deploys a resource group to a different subscription. The
 ```bicep
 targetScope = 'subscription'
 
-param otherSubscriptionID string
+param targetSubscriptionID string
+param resourceGroupName string
+param location string 
 
 // resource deployed to a different subscription
 resource exampleResource 'Microsoft.Resources/resourceGroups@2024-03-01' =  {
-  name: 'deployToDifferentSub'
-  scope: subscription(otherSubscriptionID)
-  location: 'eastus'
+  name: resourceGroupName
+  scope: subscription(targetSubscriptionID)
+  location: location
 }
 ```
 
@@ -80,11 +88,17 @@ You can fix the diagnostic by using the `module` declaration type:
 targetScope = 'subscription'
 
 param otherSubscriptionID string
+param resourceGroupName string
+param location string
 
 // module deployed to a different subscription
 module exampleModule 'module.bicep' = {
   name: 'deployToDifferentSub'
   scope: subscription(otherSubscriptionID)
+  params: {
+    resourceGroupName: resourceGroupName
+    location: location
+  }
 }
 ```