You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: azure-local/includes/hci-download-vhdx-2.md
+4-14Lines changed: 4 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,26 +3,16 @@ author: alkohli
3
3
ms.author: alkohli
4
4
ms.service: azure-local
5
5
ms.topic: include
6
-
ms.date: 05/29/2025
6
+
ms.date: 07/08/2025
7
7
---
8
8
9
9
SDN uses a VHDX file containing either the Azure Stack HCI or Windows Server operating system (OS) as a source for creating the SDN virtual machines (VMs).
10
10
11
11
> [!NOTE]
12
12
> The version of the OS in your VHDX must match the version used by the Azure Local Hyper-V machines. This VHDX file is used by all SDN infrastructure components.
13
13
14
-
[Download an English-language versionof the VHDX file](https://aka.ms/PVvxVBVCVVC).
14
+
Depending on the OS version, download one of the following VHDX files::
15
15
16
-
Currently, a non-English VHDX file isn't available for download. If you require a non-English version, [download the corresponding ISO file](../deploy/download-23h2-software.md) and convert it to VHDX using the `Convert-WindowsImage` cmdlet. You must run this script from a Windows client computer. You'll probably need to run this script as Administrator and modify the execution policy for scripts using the `Set-ExecutionPolicy` command.
16
+
- OS version 25398.xxxx: [Download an English-language version of the VHDX file](https://aka.ms/PVvxVBVCVVC).
17
+
- OS version 26100.xxxx: [Download an English-language version of the VHDX file](https://aka.ms/AAvqy3y).
17
18
18
-
The following syntax shows an example of using `Convert-WindowsImage`:
Copy file name to clipboardExpand all lines: azure-local/manage/manage-network-security-groups.md
+11-13Lines changed: 11 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,7 +43,7 @@ This article describes how to manage network security groups (NSGs) on your Azur
43
43
44
44
---
45
45
46
-
*## Manage network securi*ty groups and network security rules
46
+
## Manage network security groups and network security rules
47
47
48
48
# [Azure CLI](#tab/azurecli)
49
49
@@ -140,7 +140,7 @@ Follow these steps to show details of a network security group:
140
140
az stack-hci-vm network nsg show -g $resource_group --name $nsgname
141
141
```
142
142
143
-
2. The command outputs the details of a specified network security group (NSG).
143
+
1. The command outputs the details of a specified network security group (NSG).
144
144
145
145
- In this example, the NSG has no network interface attached.
146
146
@@ -233,7 +233,7 @@ Follow these steps to delete a network security group:
233
233
$nsgname = "examplensg"
234
234
```
235
235
236
-
2. Run the following command to delete a network security group (NSG) on your Azure Local instance.
236
+
1. Run the following command to delete a network security group (NSG) on your Azure Local instance.
237
237
238
238
```azurecli
239
239
az stack-hci-vm network nsg delete -g $resource_group --name $nsgname --yes
@@ -257,7 +257,7 @@ In this example, we create a network interface with an existing network security
257
257
$nicname="examplenic"
258
258
```
259
259
260
-
2. Run the following command to create a network interface (NIC) on your Azure Local instance.
260
+
1. Run the following command to create a network interface (NIC) on your Azure Local instance.
261
261
262
262
```azurecli
263
263
az stack-hci-vm network nic create --resource-group $resource_group --custom-location $customLocationId --location $location --subnet-id $lnetname --ip-address $ipaddress --name $nicname --network-security-group $nsgname
@@ -469,6 +469,7 @@ In this example, we associate a static logical network with an existing network
469
469
You can dissociate a network security group from a logical network. This dissociation allows you to remove the network security rules applied to the logical network.
470
470
471
471
Follow these steps to dissociate a network security group from logical network:
472
+
472
473
1. Set the following parameters in your Azure CLI session. Make sure to pass the NSG name as an empty string encased in double quotes followed by single quotes ('""').
473
474
474
475
```azurecli
@@ -478,6 +479,7 @@ Follow these steps to dissociate a network security group from logical network:
478
479
$nsgname = '""'
479
480
$lnetname="static-lnet3"
480
481
```
482
+
481
483
2. To dissociate a network security group from a logical network, run the following command:
482
484
483
485
```azurecli
@@ -575,7 +577,8 @@ Follow these steps to dissociate a network security group from logical network:
575
577
"tags": {},
576
578
"type": "microsoft.azurestackhci/logicalnetworks"
577
579
}
578
-
```
580
+
```
581
+
579
582
</details>
580
583
581
584
## Dissociate network security group from network interface
@@ -594,7 +597,7 @@ Follow these steps to dissociate a network security group from a network interfa
594
597
$nicname ="examplenic"
595
598
```
596
599
597
-
2. To dissociate a network security group from a network interface, run the following command:
600
+
1. To dissociate a network security group from a network interface, run the following command:
598
601
599
602
```azurecli
600
603
az stack-hci-vm network nic update -g $resource_group --name $nicname --network-security-group '""'
@@ -676,8 +679,7 @@ This section describes the manage operations supported for network security rule
676
679
$nsgname = "examplensg"
677
680
```
678
681
679
-
2. Run this command to show details of a network security rule:
680
-
682
+
1. Run this command to show details of a network security rule:
681
683
682
684
```azurecli
683
685
az stack-hci-vm network nsg rule show -g $resource_group -n $securityrulename --nsg-name $nsgname
@@ -733,7 +735,6 @@ This section describes the manage operations supported for network security rule
733
735
734
736
### Update a network security rule
735
737
736
-
737
738
1. Set the following parameters in your Azure CLI session.
738
739
739
740
```azurecli
@@ -967,7 +968,7 @@ To dissociate a network security group from a network interface, follow these st
967
968
968
969
1. Go to **Azure Local resource page > Resources > Network interfaces**.
969
970
970
-
:::image type="content" source="./media/manage-network-security-groups/associate-network-security-group-network-interface-1.png" alt-text="Screenshot of selecting network interface to dissociate from the network security group." lightbox="./media/manage-network-security-groups/associate-network-security-group-network-interface-1.png":::
971
+
:::image type="content" source="./media/manage-network-security-groups/associate-network-security-group-network-interface-1.png" alt-text="Screenshot of selecting network interface to dissociate from the network security group." lightbox="./media/manage-network-security-groups/associate-network-security-group-network-interface-1.png":::
971
972
972
973
1. In the right pane, from the list of network interfaces, select an interface that has a network security group attached to it.
973
974
1. Go to **Settings > Network security groups**.
@@ -982,7 +983,6 @@ To dissociate a network security group from a network interface, follow these st
982
983
The operation takes a few minutes to complete. You can see the status of the operation in the **Notifications** pane.
983
984
After the network security group is dissociated from the network interface, the page refreshes to indicate the dissociation.
984
985
985
-
986
986
## List network security rules in a network security group
987
987
988
988
To list network security rules in a network security group, follow these steps:
@@ -1004,12 +1004,10 @@ To update a network security rule, follow these steps:
1004
1004
1005
1005
---
1006
1006
1007
-
1008
1007
## Next steps
1009
1008
1010
1009
- [Troubleshoot SDN enabled by Arc](../index.yml).
Copy file name to clipboardExpand all lines: azure-local/release-information-23h2.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,7 +60,7 @@ If your cluster supports [Solution Builder Extension software updates](./update/
60
60
61
61
### Supported versions of Azure Local
62
62
63
-
The following tables summarize the release information for Azure Local across all supported versions. All dates are listed in ISO 8601 format: *YYYY-MM-DD*.
63
+
The following tables summarize the release information for Azure Local across all supported versions. All dates are listed in ISO 8601 format: *YYYY-MM-DD*. After you upgrade your solution, you might see 10.x versions; these versions are supported.
64
64
65
65
> [!IMPORTANT]
66
66
> The new deployments of this software use the **12.2506.1001.29** build. You can also update an existing deployment from 2505 using **11.2506.1001.28**.
@@ -69,8 +69,8 @@ The following tables summarize the release information for Azure Local across al
69
69
70
70
| Solution version | OS build | Security update | What's new | Known issues |
Copy file name to clipboardExpand all lines: azure-local/upgrade/install-solution-upgrade.md
+10-2Lines changed: 10 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -122,7 +122,6 @@ Follow these steps to verify that the upgrade was successful:
122
122
1. In Azure portal, go to the resource group where you deployed the Azure Local instance.
123
123
1. On the **Overview > Resources** page, you should see the following resources:
124
124
125
-
126
125
| Resource type | Number of resources |
127
126
|---------|---------|
128
127
| Machine - Azure Arc | 1 per machine |
@@ -131,10 +130,19 @@ Follow these steps to verify that the upgrade was successful:
131
130
| Custom location | 1, *-cl* suffix by default |
132
131
| Key Vault | 1 |
133
132
134
-
Here is a screenshot of the resources in the resource group:
133
+
Here's a screenshot of the resources in the resource group:
135
134
136
135
:::image type="content" source="./media/install-solution-upgrade/verify-upgrade-portal.png" alt-text="Screenshot of Upgrade Azure Local resource health." lightbox="./media/install-solution-upgrade/verify-upgrade-portal.png":::
137
136
137
+
1. Verify your solution version.
138
+
139
+
Here's a screenshot of the **Overview** page of the Azure Local resource, showing the solution version:
140
+
141
+
:::image type="content" source="./media/install-solution-upgrade/verify-solution-version.png" alt-text="Screenshot of Azure Local overview page and solution version." lightbox="./media/install-solution-upgrade/verify-solution-version.png":::
142
+
143
+
> [!NOTE]
144
+
> After a solution upgrade, you might see a 10.x version, this is expected and supported. For more information, see [Azure Local release information summary](../release-information-23h2.md#azure-local-release-information-summary).
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments