Skip to content

Commit eacd59e

Browse files
authored
Merge pull request #18024 from ManikaDhiman/md-revert-changes-to-main
Urgent: to go live at 10 AM: Revert changes to main--config app, docfx, KI
2 parents ebfed56 + 7fef69d commit eacd59e

File tree

6 files changed

+51
-54
lines changed

6 files changed

+51
-54
lines changed

azure-local/deploy/deployment-arc-register-configurator-app.md

Lines changed: 28 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to use the Configurator app to bootstrap and quickly regi
44
author: alkohli
55
ms.author: alkohli
66
ms.topic: how-to
7-
ms.date: 05/23/2025
7+
ms.date: 05/22/2025
88
ms.service: azure-local
99
#CustomerIntent: As an IT Pro, I want to bootstrap and Arc register Azure Local machines via the Arc registration script.
1010
---
@@ -28,6 +28,7 @@ Before you begin, make sure that you complete the following prerequisites:
2828
[!INCLUDE [hci-registration-azure-local-machine-prerequisites](../includes/hci-registration-azure-local-machine-prerequisites.md)]
2929

3030
- Download the [Configurator App for Azure Local](https://aka.ms/ConfiguratorAppForHCI).
31+
3132
- Note down:
3233

3334
- The serial number for each machine.
@@ -150,7 +151,7 @@ Follow these steps to configure network settings and connect the machines to Azu
150151
151152
1. On the resource group used to bootstrap, you should see your Arc-enabled machines. In this example, you see a single machine.
152153
153-
:::image type="content" source="media/deployment-arc-register-configurator-app/setup-arc-enabled-servers.png" alt-text="Screenshot that shows the Azure Arc agent Arc-enabled servers in Azure portal for Azure Local." lightbox="media/deployment-arc-register-configurator-app/setup-arc-enabled-servers.png":::
154+
:::image type="content" source="media/deployment-arc-register-configurator-app/setup-arc-enabled-servers.png" alt-text="Screenshot that shows the Azure Arc agent Arc-enabled servers in Azure portal for Azure Local ." lightbox="media/deployment-arc-register-configurator-app/setup-arc-enabled-servers.png":::
154155
155156
## Troubleshooting
156157
@@ -193,11 +194,11 @@ Here's a table that describes the diagnostic tests:
193194
194195
### Collect a Support log package from the app
195196
196-
A Support log package is composed of all the relevant logs that can help Microsoft Support troubleshoot any machine issues. You can generate a Support package via the app.
197+
A Support package is composed of all the relevant logs that can help Microsoft Support troubleshoot any machine issues. You can generate a Support package via the app.
197198
198199
#### Download the Support log package
199200
200-
Follow these steps to collect and download a Support log package:
201+
Follow these steps to collect and download a Support package:
201202
202203
1. Select the help icon in the top-right corner of the app to open the **Support + troubleshooting** pane. Select **Create** to begin support package collection. The package collection could take several minutes.
203204
@@ -207,25 +208,38 @@ Follow these steps to collect and download a Support log package:
207208
208209
#### Upload the Support log package
209210
210-
> [!IMPORTANT]
211-
> - Make sure to run the Configurator app as an administrator to upload the Support log package.
212-
> - Uploading the Support log package to Microsoft can take up to 20 minutes. Make sure to leave the app open and running to complete this process.
213-
214-
Collect a Support log package before you upload it. Follow these steps to upload the Support log package to Microsoft:
211+
>[!IMPORTANT]
212+
> Uploading the Support package to Microsoft can take up to 20 minutes. Make sure to leave the app open and running to complete this process.
215213
214+
Follow these steps to upload the Support package to Microsoft:
216215
1. Select the help icon in the top-right corner of the app to open the **Support + troubleshooting** pane. Select **Upload** to upload the Support package to Microsoft.
217216
218217
:::image type="content" source="media/deployment-arc-register-configurator-app/upload-support-package-1.png" alt-text="Screenshot that shows the Support and troubleshooting pane with Upload package selected." lightbox="media/deployment-arc-register-configurator-app/upload-support-package-1.png":::
219218
220-
1. Provide the required information in the **Upload Support package to Microsoft** dialog:
219+
1. Provide the required information in the **Upload Support package** dialog:
221220
222221
:::image type="content" source="media/deployment-arc-register-configurator-app/upload-support-package-2.png" alt-text="Screenshot that shows the Upload Support Package dialog filled out." lightbox="media/deployment-arc-register-configurator-app/upload-support-package-2.png":::
223222
224-
The fields in the dialog are prepopulated with the information you provided during [Step 1: Configure the network and connect to Azure](#step-1-configure-the-network-and-connect-to-azure). You can modify the fields as needed.
223+
1. The **Cloud type** is populated automatically as `Azure`.
224+
225+
1. Enter a **Subscription ID** to register the machine.
226+
227+
1. Provide a **Resource group** name. This resource group contains the machine and system resources that you create.
228+
229+
1. Specify the **Region** where you want to create the resources. The region should be the same as the region where you want to deploy the Azure Local instance.
230+
231+
> [!IMPORTANT]
232+
> Specify the region with spaces removed. For example, specify the East US region as `EastUS`.
233+
234+
1. Provide a **Tenant ID**. The tenant ID is the directory ID of your Microsoft Entra tenant. To get the tenant ID, see [Find your Microsoft Entra tenant](/azure/azure-portal/get-subscription-tenant-id).
235+
236+
1. If you set up an Azure Arc gateway, specify the Arc gateway ID. This is the resource ID of the Arc gateway that you set up. For more information, see [About Azure Arc gateways](./deployment-azure-arc-gateway-overview.md).
225237
238+
> [!IMPORTANT]
239+
> Make sure to verify all the inputs before you proceed. Any incorrect inputs here might result in an upload failure.
226240
227-
1. Select **Begin upload** to upload the Support package.
228-
1. Authenticate in the browser with the same account that you used to sign in to register with Azure Arc. The upload process might take several minutes. Leave the app open and running until the upload is complete.
241+
1. Select **Upload** to upload the Support package.
242+
1. Authenticate in the browser with the same account that you used to sign in to the Configurator app. The upload process might take several minutes.
229243
230244
:::image type="content" source="media/deployment-arc-register-configurator-app/upload-support-package-3.png" alt-text="Screenshot that shows the Support and troubleshooting pane with Upload selected and authentication guidance." lightbox="media/deployment-arc-register-configurator-app/upload-support-package-3.png":::
231245
@@ -243,4 +257,4 @@ If you have more than one version of the app installed, when you try to open the
243257
244258
- After your machines are registered with Azure Arc, proceed to deploy your Azure Local system via one of the following options:
245259
- [Deploy via Azure portal](./deploy-via-portal.md).
246-
- [Deploy via ARM template](./deployment-azure-resource-manager-template.md).
260+
- [Deploy via ARM template](./deployment-azure-resource-manager-template.md).

azure-local/docfx.json

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -86,14 +86,14 @@
8686
},
8787
"fileMetadata": {
8888
"monikerRange": {
89-
"./*.md": ">=azloc-24111 || =azloc-previous",
90-
"./*.yml": ">=azloc-24111 || =azloc-previous"
89+
"./*.md": ">=azloc-2411 || =azloc-previous",
90+
"./*.yml": ">=azloc-2411 || =azloc-previous"
9191
}
9292
},
9393
"template": [],
9494
"groups": {
9595
"version-azlocal": {
96-
"moniker_range": ">=azloc-24111 || =azloc-previous",
96+
"moniker_range": ">=azloc-2411 || =azloc-previous",
9797
"dest": "azure-local"
9898
}
9999
}

azure-local/known-issues.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -344,7 +344,7 @@ The following table lists the known issues from previous releases:
344344

345345
::: moniker-end
346346

347-
::: moniker range="=azloc-previous"
347+
::: moniker range="=azloc-2411"
348348

349349
## Known issues for version 2411
350350

@@ -397,6 +397,10 @@ The following table lists the known issues from previous releases:
397397
| Update | When updating the Azure Local instance via the Azure Update Manager, the update progress and results may not be visible in the Azure portal.| To work around this issue, on each node, add the following registry key (no value needed):<br><br>`New-Item -Path "HKLM:\SYSTEM\CurrentControlSet\Services\HciCloudManagementSvc\Parameters" -force`</br><br> Then on one of the nodes, restart the Cloud Management cluster group. </br><br>`Stop-ClusterGroup "Cloud Management"`</br><br>`Start-ClusterGroup "Cloud Management"`</br><br> This won't fully remediate the issue as the progress details may still not be displayed for a duration of the update process. To get the latest update details, you can [Retrieve the update progress with PowerShell](./update/update-via-powershell-23h2.md#step-6-track-update-progress). |
398398
| Update <!--26659432--> |In some cases, `SolutionUpdate` commands could fail if run after the `Send-DiagnosticData` command. | Make sure to close the PowerShell session used for `Send-DiagnosticData`. Open a new PowerShell session and use it for `SolutionUpdate` commands.|
399399

400+
::: moniker-end
401+
402+
::: moniker range="=azloc-previous"
403+
400404
## Known issues for version 2408.2
401405

402406
This software release maps to software version number **2408.2.7**.
@@ -1206,4 +1210,4 @@ Here are the known issues from previous releases:
12061210

12071211
## Next steps
12081212

1209-
- Read the [Deployment overview](./deploy/deployment-introduction.md).
1213+
- Read the [Deployment overview](./deploy/deployment-introduction.md).

azure-local/manage/add-server.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -182,4 +182,4 @@ You might need to provide diagnostic logs from the new node that's to be added t
182182
183183
## Next steps
184184
185-
- Learn more about how to [Repair a node](./repair-server.md).
185+
- Learn more about how to [Repair a node](./repair-server.md).

azure-local/security-update/security-update.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Security updates for Azure Local, version 23H2
33
description: Security updates for Azure Local, version 23H2.
44
author: alkohli
55
ms.topic: conceptual
6-
ms.date: 05/12/2025
6+
ms.date: 04/25/2025
77
ms.author: alkohli
88
ms.reviewer: alkohli
99
---
@@ -306,7 +306,7 @@ For a list of the files that are provided in this update, download the file info
306306
307307
::: moniker-end
308308
309-
::: moniker range="azloc-previous"
309+
::: moniker range="azloc-2411"
310310
311311
## November OS security update (KB) for Azure Local
312312
@@ -344,6 +344,10 @@ To install the LCU on your Azure Local instance, see [Update Azure Stack Local i
344344
345345
For a list of the files that are provided in this update, download the file information for [Cumulative update KB 5046618](https://go.microsoft.com/fwlink/?linkid=2296832).
346346
347+
::: moniker-end
348+
349+
::: moniker range="azloc-previous"
350+
347351
## October OS security update (KB 5044288) for Azure Local
348352
349353
<!-- [!INCLUDE [applies-to](../includes/hci-applies-to-23h2.md)] -->

azure-local/whats-new.md

Lines changed: 7 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ ms.topic: overview
55
author: alkohli
66
ms.author: alkohli
77
ms.service: azure-local
8-
ms.date: 05/22/2025
8+
ms.date: 05/08/2025
99
---
1010

1111
# What's new in Azure Local?
@@ -16,35 +16,6 @@ ms.date: 05/22/2025
1616

1717
This article lists the various features and improvements that are available in Azure Local. The latest version of Azure Local solution focuses on cloud-based deployment and updates, cloud-based monitoring, new and simplified experience for Azure Local virtual machine (VM) management, security, and more.
1818

19-
::: moniker range="=azloc-2505"
20-
21-
There are two 2505 releases for May. Here are the details of each release:
22-
23-
|Solution version |OS version |Deployment |
24-
|---------|---------|---------|
25-
|12.2505.1001.23 | 26100.4061 | New deployments only. |
26-
|11.2505.1001.22 | 25398.1611 | Existing deployments only. |
27-
28-
For more information, see [Release information summary](./release-information-23h2.md).
29-
30-
## Features and improvements in 2505
31-
32-
This release has the following features and improvements:
33-
34-
- **OS version changes**:
35-
36-
- In the last release (2504), a new operating system was introduced for Azure Local deployments. For 2505, all the new deployments of Azure Local will run OS version **26100.4061**. You can download the 2505 OS image from the Azure portal. You also need to get the driver compatible with Azure Local 12.2505 or Windows Server 2025. If a compatible driver is not available, you can use the 2503 image.
37-
38-
Existing deployments of Azure Local will continue to use OS version **25398.1611**. For more information, see [Release information summary](./release-information-23h2.md).
39-
40-
- If you've purchased Integrated System or Premier solution hardware from the [Azure Local Catalog](https://aka.ms/AzureStackHCICatalog) through your preferred Microsoft hardware partner, the OS should be preinstalled. Work with your Original Equipment Manufacturer (OEM) to get the OS image compatible with **12.2505** and driver compatible with Azure Local 12.2505 or Windows Server 2025.
41-
42-
- **.NET updates**: This build uses .NET version **8.0.16** for both .NET Runtime and ASP.NET Core. For more details, see [Download .NET 8.0](https://dotnet.microsoft.com/download/dotnet/8.0).
43-
44-
- **Update changes**: This release includes reliability improvements to the update process. For more information, see [Fixed issues in 2505](./known-issues.md?view=azloc-2505&preserve-view=true#fixed-issues).
45-
46-
::: moniker-end
47-
4819
::: moniker range="=azloc-2504"
4920

5021
Starting with 2504 release, Microsoft introduced a new versioning schema. There are two 2504 releases for April. Here are the details of each release:
@@ -199,7 +170,7 @@ For more information on improvements in this release, see the [Fixed issues in 2
199170

200171
::: moniker-end
201172

202-
::: moniker range="=azloc-previous"
173+
::: moniker range="=azloc-2411"
203174

204175
## Features and improvements in 2411
205176

@@ -248,6 +219,10 @@ This release has the following features and improvements:
248219

249220
- **AKS on Azure Local** - This release has several new features and enhancements for AKS on Azure Local. For more information, see [What's new in AKS on Azure Local](/azure/aks/hybrid/aks-whats-new-23h2).
250221

222+
::: moniker-end
223+
224+
::: moniker range="=azloc-previous"
225+
251226
## Features and improvements in 2408.2
252227

253228
This release has the following features and improvements:
@@ -695,4 +670,4 @@ For more information, see [Optimize storage with ReFS deduplication and compress
695670
- Read the [blog announcing the general availability of Azure Local](https://techcommunity.microsoft.com/t5/azure-stack-blog/azure-stack-hci-version-23h2-is-generally-available/ba-p/4046110).
696671
- For Azure Local deployments:
697672
- Read the [Deployment overview](./deploy/deployment-introduction.md).
698-
- Learn how to [Deploy Azure Local via the Azure portal](./deploy/deploy-via-portal.md).
673+
- Learn how to [Deploy Azure Local via the Azure portal](./deploy/deploy-via-portal.md).

0 commit comments

Comments
 (0)