Skip to content

Commit 813ed02

Browse files
committed
update
1 parent 83c0716 commit 813ed02

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

articles/azure-resource-manager/bicep/deploy-what-if.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Bicep deployment what-if
33
description: Determine what changes will happen to your resources before deploying a Bicep file.
44
ms.topic: conceptual
55
ms.custom: devx-track-bicep, devx-track-azurecli, devx-track-azurepowershell
6-
ms.date: 08/04/2025
6+
ms.date: 08/12/2025
77
---
88

99
# Bicep deployment what-if operation
@@ -50,7 +50,7 @@ When one of the limits is reached, the remaining resources' [change type](#chang
5050

5151
### Short-circuiting
5252

53-
The what-if operation in Bicep deployments may encounter "short-circuiting," a scenario where the service cannot fully analyze a module or resource due to the deployment's structure or dependencies on external state. Short-circuiting of an individual resource occurs when its resource ID or API version cannot be calculated outside the deployment context, often due to unresolved expressions or external dependencies. While rare, short-circuiting of modules or nested deployment resources can also happen, resulting in all resources within the module being excluded from the what-if analysis results. In such cases, the API response includes a diagnostic message to indicate the issue.
53+
The what-if operation in Bicep deployments may encounter "short-circuiting," a scenario where the service cannot fully analyze a module or resource due to the deployment's structure or dependencies on external state. Short-circuiting of an individual resource occurs when its resource ID or API version cannot be calculated outside the deployment context, often due to unresolved expressions or external dependencies. For more information, see [Unevaluated expressions](#unevaluated-expressions). While rare, short-circuiting of modules or nested deployment resources can also happen, resulting in all resources within the module being excluded from the what-if analysis results. In such cases, the API response includes a diagnostic message to indicate the issue.
5454

5555
## Running the what-if operation
5656

@@ -302,7 +302,7 @@ Resource and property changes are indicated with these symbols:
302302

303303
The deployment will update the following scope:
304304

305-
Scope: /subscriptions/a1bfa635-f2bf-42f1-86b5-848c674fc321/resourceGroups/ExampleGroup
305+
Scope: /subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourceGroups/ExampleGroup
306306

307307
~ Microsoft.Network/virtualNetworks/vnet-001 [2024-07-01]
308308
- properties.privateEndpointVNetPolicies: "Disabled"
@@ -502,7 +502,7 @@ Resource and property changes are indicated with this symbol:
502502

503503
The deployment will update the following scope:
504504

505-
Scope: /subscriptions/a1bfa635-f2bf-42f1-86b5-848c674fc321/resourceGroups/jgaotest
505+
Scope: /subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourceGroups/jgaotest
506506

507507
~ Microsoft.Storage/storageAccounts/acct0808 [2025-01-01]
508508
~ tags.lastDeployedOn: "20250808T200145Z" => "[utcNow()]"
1.13 KB
Loading

0 commit comments

Comments
 (0)