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/deploy/deploy-via-portal.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Deploy an Azure Local instance using the Azure portal
3
3
description: Learn how to deploy an Azure Local instance from the Azure portal
4
4
author: alkohli
5
5
ms.topic: how-to
6
-
ms.date: 03/11/2025
6
+
ms.date: 03/24/2025
7
7
ms.author: alkohli
8
8
ms.service: azure-local
9
9
#CustomerIntent: As an IT Pro, I want to deploy an Azure Local instance of 1-16 machines via the Azure portal so that I can host VM and container-based workloads on it.
@@ -60,6 +60,10 @@ This article helps you deploy an Azure Local instance using the Azure portal.
60
60
61
61
:::image type="content" source="./media/deploy-via-portal/basics-tab-5.png" alt-text="Screenshot of successful validation on the Basics tab in deployment via Azure portal." lightbox="./media/deploy-via-portal/basics-tab-5.png":::
62
62
63
+
If the validation fails with wrong extension version, go to **Install extensions** to install the appropriate version of extension.
64
+
65
+
After the extensions are installed successfully, **Add machines** by selecting from the same list of machines and then **Validate selected machines**.
66
+
63
67
1.**Select an existing Key Vault** or select **Create a new Key Vault**. Create an empty key vault to securely store secrets for this system, such as cryptographic keys, local admin credentials, and BitLocker recovery keys.
64
68
65
69
1. On the **Create a new key vault** page, provide information for the specified parameters and select **Create**:
Copy file name to clipboardExpand all lines: azure-local/known-issues.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -151,7 +151,7 @@ The following table lists the known issues in this release:
151
151
152
152
|Feature |Issue |Workaround |
153
153
|---------|---------|---------|
154
-
| Deployment | During Azure Local deployment via portal, **Validate selected machines** fails with this error emssage: `Mandatory extension [Lcm controller] installed version [30.2503.0.907] is not equal to the required version [30.2411.2.789] for Arc machine [Name of the machine]. Please create EdgeDevice resource again for this machine to fix the issue.`| Reinstall the correct version of `AzureEdgeLifecycleManager` extension. Follow these steps: <br> 1. Select the machine and then select **Install extensions**. <br> 2. Repeat this step for each machine you intend to cluster. It takes roughly 15 minutes for the installation to complete. <br> 3. Verify that the `AzureEdgeLifecycleManager` extension version is 30.2411.2.789. <br> 4. After the extensions are installed on all the machines in the list, select **Add machines** to refresh the list. <br> 5. Select **Validate selected machines**. The validation should succeed. |
154
+
| Deployment | During Azure Local deployment via portal, **Validate selected machines** fails with this error message: `Mandatory extension [Lcm controller] installed version [30.2503.0.907] is not equal to the required version [30.2411.2.789] for Arc machine [Name of the machine]. Please create EdgeDevice resource again for this machine to fix the issue.` | Reinstall the correct version of `AzureEdgeLifecycleManager` extension. Follow these steps: <br> 1. Select the machine and then select **Install extensions**. <br> <br><br> <br> 2. Repeat this step for each machine you intend to cluster. It takes roughly 15 minutes for the installation to complete. <br> 3. Verify that the `AzureEdgeLifecycleManager` extension version is 30.2411.2.789. <br><br>  <br><br> 4. After the extensions are installed on all the machines in the list, select **Add machines** to refresh the list. <br> 5. Select **Validate selected machines**. The validation should succeed. |
155
155
| Deployment | During the Azure Local deployment, `DeviceManagementExtension` fails to install when a proxy is configured. | Install previous `DeviceManangementExtension` version 1.2502.0.3012 when using a proxy. |
156
156
| Operating system | Restoring the registry using *RegBack* isn't supported on Azure Local. This operation can remove the Lifecycle Manager (LCM) and Microsoft On-premises Cloud (MOC) settings on your Azure Local instance, which can corrupt the solution. ||
Copy file name to clipboardExpand all lines: azure-local/release-information-23h2.md
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: alkohli
5
5
ms.author: alkohli
6
6
ms.topic: conceptual
7
7
ms.service: azure-local
8
-
ms.date: 02/19/2025
8
+
ms.date: 03/27/2025
9
9
---
10
10
11
11
# Azure Local release information
@@ -22,7 +22,7 @@ This article provides the release information for Azure Local, including the rel
22
22
23
23
## About Azure Local releases
24
24
25
-
The Azure Local includes multiple release trains: 2311, 2402, 2405, 2408, and 2411. Each release train includes a feature build and subsequent cumulative updates.
25
+
The Azure Local includes multiple release trains: 2402, 2405, 2408, 2411, and 2503. Each release train includes a feature build and subsequent cumulative updates.
26
26
27
27
-**Feature build**: The feature update build is the initial version of the software in a release train. Feature releases go beyond quality and security fixes, incorporating product enhancements, including updates for Azure Local services and agents.
28
28
@@ -62,6 +62,7 @@ The following table summarizes the release information for Azure Local across al
62
62
63
63
|Version| OS Build |Security update| What's new | Known issues |
Copy file name to clipboardExpand all lines: azure-local/whats-new.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,6 +28,7 @@ This is a baseline release with the following features and improvements:
28
28
- Several security enhancements were done for the Bootstrap service.
29
29
- Service Principal Name (SPN) is deprecated for Arc registration.
30
30
- The Arc installer script is simplified to only use `Start-ArcBootstrap` to register Azure Local machines with Arc.
31
+
-**Deployment of current version and previous versions**: Starting with this release, you can deploy the current version of Azure Local using the Azure portal. To deploy a previous version, use an Azure Resource Manager template that matches the version you wish to deploy. For more information, see [Deploy via ARM template](./deploy/deployment-azure-resource-manager-template.md).
31
32
-**Environment checker related changes**
32
33
- Environment checker is now integrated for connectivity tests.
33
34
- Environment checker validates the composed image used for bootstrap.
0 commit comments