Skip to content

Commit aadfd99

Browse files
v-aljev-alje
committed
Merge branch 'main' into release-preview-sentinel-lake
2 parents 793c186 + ae125ad commit aadfd99

File tree

8 files changed

+333
-66
lines changed

8 files changed

+333
-66
lines changed

‎articles/azure-fluid-relay/concepts/customer-managed-keys.md

Lines changed: 168 additions & 51 deletions
Large diffs are not rendered by default.

‎articles/azure-resource-manager/bicep/bicep-core-diagnostics.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.custom:
77
- devx-track-bicep
88
- devx-track-arm-template
99
- build-2025
10-
ms.date: 06/19/2025
10+
ms.date: 07/16/2025
1111
---
1212

1313
# Bicep core diagnostics
@@ -152,7 +152,7 @@ If you need more information about a particular diagnostic code, select the **Fe
152152
| <a id='BCP141' />BCP141 | Error | The expression can't be used as a decorator as it isn't callable. |
153153
| <a id='BCP142' />BCP142 | Error | Property value for-expressions can't be nested. |
154154
| <a id='BCP143' />BCP143 | Error | For-expressions can't be used with properties whose names are also expressions. |
155-
| <a id='BCP144' />BCP144 | Error | Directly referencing a resource or module collection isn't currently supported here. Apply an array indexer to the expression. |
155+
| <a id='BCP144' />[BCP144](./diagnostics/bcp144.md) | Error | Directly referencing a resource or module collection isn't currently supported here. Apply an array indexer to the expression. |
156156
| <a id='BCP145' />BCP145 | Error | Output `{identifier}` is declared multiple times. Remove or rename the duplicates. |
157157
| <a id='BCP147' />[BCP147](./diagnostics/bcp147.md) | Error | Expected a parameter declaration after the decorator. |
158158
| <a id='BCP148' />BCP148 | Error | Expected a variable declaration after the decorator. |

‎articles/azure-resource-manager/bicep/diagnostics/bcp144.md

Lines changed: 111 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,111 @@
1+
---
2+
title: BCP144
3+
description: Directly referencing a resource or module collection isn't currently supported here. Apply an array indexer to the expression.
4+
ms.topic: reference
5+
ms.custom: devx-track-bicep
6+
ms.date: 07/16/2025
7+
---
8+
9+
# Bicep diagnostic code - BCP144
10+
11+
This diagnostic occurs when you try to reference a resource or module collection (for example, one defined using a `for`-loop) without specifying an index. Bicep requires that such references explicitly indicate which resource or module in the collection you're referring to using an array index.
12+
13+
## Description
14+
15+
Directly referencing a resource or module collection isn't currently supported here. Apply an array indexer to the expression.
16+
17+
## Level
18+
19+
Error
20+
21+
## Solutions
22+
23+
To resolve BCP144, use an array index to access each specific resource or module in the collection. Instead of looping over the collection directly, loop over the input array and use the index to reference the corresponding item.
24+
25+
## Examples
26+
27+
The following example raises the diagnostic because it references a resource collection without specifying an index.
28+
29+
```bicep
30+
param names array = [
31+
'one'
32+
'two'
33+
]
34+
35+
resource demo 'Microsoft.Storage/storageAccounts@2022-09-01' = [for name in names: {
36+
name: 'demo${name}'
37+
location: resourceGroup().location
38+
sku: {
39+
name: 'Standard_LRS'
40+
}
41+
kind: 'StorageV2'
42+
properties: {}
43+
}]
44+
45+
// ❌ This line triggers BCP144.
46+
output storageNames array = [for r in demo: r.name]
47+
```
48+
49+
To resolve BCP144, use an array index to access each specific resource in the collection.
50+
51+
```bicep
52+
param names array = [
53+
'one'
54+
'two'
55+
]
56+
57+
resource demo 'Microsoft.Storage/storageAccounts@2022-09-01' = [for name in names: {
58+
name: 'demo${name}'
59+
location: resourceGroup().location
60+
sku: {
61+
name: 'Standard_LRS'
62+
}
63+
kind: 'StorageV2'
64+
properties: {}
65+
}]
66+
67+
// ✅ Correct usage with indexing.
68+
output storageNames array = [for (name, i) in names: demo[i].name]
69+
```
70+
71+
The following example shows the error code with a module collection.
72+
73+
```bicep
74+
param locations array = [
75+
'eastus'
76+
'westus'
77+
]
78+
79+
module storageModule 'storage.bicep' = [for loc in locations: {
80+
name: 'storage-${loc}'
81+
params: {
82+
location: loc
83+
}
84+
}]
85+
86+
// ❌ This line triggers BCP144.
87+
output moduleOutputs array = [for m in storageModule: m.outputs.storageAccountName]
88+
```
89+
90+
To resolve BCP144, use an array index to access each specific module in the collection.
91+
92+
```bicep
93+
param locations array = [
94+
'eastus'
95+
'westus'
96+
]
97+
98+
module storageModule 'storage.bicep' = [for loc in locations: {
99+
name: 'storage-${loc}'
100+
params: {
101+
location: loc
102+
}
103+
}]
104+
105+
// ✅ Correct usage with indexing.
106+
output moduleOutputs array = [for (loc, i) in locations: storageModule[i].outputs.storageAccountName]
107+
```
108+
109+
## Next steps
110+
111+
For more information about Bicep diagnostics, see [Bicep core diagnostics](../bicep-core-diagnostics.md).

‎articles/azure-resource-manager/bicep/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -694,6 +694,8 @@ items:
694694
href: diagnostics/bcp135.md
695695
- name: BCP139
696696
href: diagnostics/bcp139.md
697+
- name: BCP144
698+
href: diagnostics/bcp144.md
697699
- name: BCP147
698700
href: diagnostics/bcp147.md
699701
- name: BCP152

‎articles/operator-nexus/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -38,6 +38,8 @@
3838
href: concepts-network-fabric.md
3939
- name: Network Fabric Controller
4040
href: concepts-network-fabric-controller.md
41+
- name: Network Fabric management upgrade
42+
href: concepts-fabric-management-upgrade.md
4143
- name: Network Fabric Services
4244
href: concepts-network-fabric-services.md
4345
- name: Network Fabric resource update and commit

‎articles/operator-nexus/concepts-cluster-management-upgrade.md

Lines changed: 15 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,28 +1,30 @@
11
---
2-
title: Azure Operator Nexus cluster management upgrade overview
3-
description: Get an overview of cluster management upgrade for Azure Operator Nexus.
4-
author: matternst7258
5-
ms.author: matthewernst
2+
title: Azure Operator Nexus Cluster management upgrade overview
3+
description: Get an overview of Cluster management upgrade for Azure Operator Nexus.
4+
author: bartpinto
5+
ms.author: bpinto
66
ms.service: azure-operator-nexus
77
ms.topic: conceptual
8-
ms.date: 11/19/2024
8+
ms.date: 07/16/2025
99
ms.custom: template-concept
1010
---
1111

12-
# Operator Nexus management upgrades
13-
14-
Operator Nexus releases various functionality and bug fixes throughout the month to update the Azure resources and on-premises extensions, critical in communications back to Azure.
12+
# Operator Nexus Cluster management upgrades
13+
Operator Nexus releases various functionality and bug fixes throughout the product lifecycle to update the Azure resources and on-premises extensions, critical in communications back to Azure.
1514

1615
## Scope
17-
18-
The releases update components on the Cluster Manager and Network Fabric Controller to enable new functionality, while maintaining backwards compatibility for the customer. Additionally, new runtime releases make available and accessed via [Cluster Runtime Upgrades](./howto-cluster-runtime-upgrade.md) and [Network Fabric Upgrades](./howto-upgrade-nexus-fabric.md).
16+
The releases update components on the Cluster Manager to enable new functionality, while maintaining backwards compatibility for the customer. Additionally, new runtime releases are made available and accessed via [Cluster Runtime Upgrades](./howto-cluster-runtime-upgrade.md).
1917

2018
For Compute management, Microsoft delivers new software to the extensions and agents that exist on the platform to provide new functionality and maintain security and communication back to Azure.
2119

22-
## Impact to customer workloads
20+
## Delivery
21+
Cluster Manager update is triggered independently when the release is available in the region.
2322

24-
The intent of these releases is no disruption to running workloads, instantiating new workloads, and on-premises resources retain availability throughout the upgrade. Therefore, the customer should see no impact.
23+
## Impact to customer workloads
24+
There's no disruption to running workloads or instantiating new workloads, and on-premises resources retain availability throughout the upgrade. Therefore, the customer sees no impact.
2525

2626
## Duration of on-premises updates
27+
Updates take up to one hour to complete per cluster.
2728

28-
These updates take up to one hour to complete per cluster.
29+
## Related Information
30+
For concepts on Network Fabric management upgrades, see [Azure Operator Nexus Network Fabric management upgrade overview](./concepts-fabric-management-upgrade.md).

‎articles/operator-nexus/concepts-fabric-management-upgrade.md

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
---
2+
title: Azure Operator Nexus Network Fabric management upgrade overview
3+
description: Get an overview of Network Fabric management upgrade for Azure Operator Nexus.
4+
author: bartpinto
5+
ms.author: bpinto
6+
ms.service: azure-operator-nexus
7+
ms.topic: conceptual
8+
ms.date: 07/16/2025
9+
ms.custom: template-concept
10+
---
11+
12+
# Operator Nexus Network Fabric management upgrades
13+
Operator Nexus releases various functionality and bug fixes throughout the product lifecycle to update the Azure resources and on-premises extensions, critical in communications back to Azure.
14+
15+
## Scope
16+
The releases update components on the Network Fabric Controller to enable new functionality, while maintaining backwards compatibility for the customer. Additionally, new runtime releases are made available and accessed via [Network Fabric Upgrades](./howto-upgrade-nexus-fabric.md).
17+
18+
For Fabric Device management, Microsoft delivers new software to the extensions and agents that exist on the platform to provide new functionality and maintain security and communication back to Azure.
19+
20+
## Delivery
21+
Network Fabric Controller update is triggered independently when the release is available in the region.
22+
23+
## Impact to customer workloads
24+
There's no disruption to running workloads or instantiating new workloads, and on-premises resources retain availability throughout the upgrade. Therefore, the customer sees no impact.
25+
26+
## Duration of on-premises updates
27+
Updates take approximately 45 minutes to complete per Network Fabric.
28+
29+
## Related Information
30+
For concepts on Cluster management upgrades, see [Azure Operator Nexus Cluster management upgrade overview](./concepts-cluster-management-upgrade.md).

‎articles/static-web-apps/custom-domain.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,9 @@ ms.author: wujia
1111

1212
# Custom domains with Azure Static Web Apps
1313

14+
> [!NOTE]
15+
> Custom domain validation for Enterprise Grade Edge Static Web Apps now requires TXT token method - CNAME validation is no longer supported for new domains.
16+
1417
By default, Azure Static Web Apps provides an autogenerated domain name for your website, but you can point a custom domain to your site. Free SSL/TLS certificates are automatically created for the autogenerated domain name and any custom domains you may add.
1518

1619
When you map a custom domain to a static web app, you have a few options available, which include configuring subdomains and an apex domain.

0 commit comments

Comments
 (0)