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/faq.yml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,7 @@ sections:
44
44
45
45
- question: Are there bandwidth or latency requirements between Azure Local and the cloud?
46
46
answer: |
47
-
Yes. Limited-bandwidth connections like rural T1 lines or satellite/cellular connections are adequate for Azure Local to sync. The minimum required connectivity is 10 Mb per day. More services might require extra bandwidth, especially to replicate or back up whole VMs, download large software updates, or upload verbose logs for analysis and monitoring in the cloud.
47
+
Yes. Limited-bandwidth connections like rural T1 lines or satellite/cellular connections are adequate for Azure Local to sync. The minimum required connectivity is 10 Mbit. More services might require extra bandwidth, especially to replicate or back up whole VMs, download large software updates, or upload verbose logs for analysis and monitoring in the cloud.
48
48
49
49
- question: Does Azure Local require continuous connectivity to the cloud?
Copy file name to clipboardExpand all lines: azure-local/known-issues.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,15 +23,15 @@ For more information about new features in this release, see [What's new for Azu
23
23
24
24
## Known issues for version 2506
25
25
26
-
For the 2506 release of Azure Local, Microsoft released two security updates: one for existing deployments and another for new deployments. The following table provides information about different deployment types, their corresponding security updates, and OS builds:
26
+
For the 2506 release of Azure Local, Microsoft released two security updates, each aligned with a specific OS build. The following table provides the specific versions and their OS builds:
> The new deployments of this software use the **12.2506.1001.29** build. You can also update an existing deployment from 2504 using **11.2506.1001.28**.
34
+
> 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**.
35
35
36
36
Release notes for this version include the issues fixed in this release, known issues in this release, and release note issues carried over from previous versions.
| Governance | [Security baseline](.././concepts/secure-baseline.md) | Maintains the security defaults on each node. Helps protect against changes. | Yes |
121
+
| Governance | [Security baseline](#view-and-download-security-settings) | Maintains the security defaults on each node. Helps protect against changes. | Yes |
| Application control | [Windows Defender Application control](/windows/security/threat-protection/windows-defender-application-control/wdac-and-applocker-overview#windows-defender-application-control) | Controls which drivers and apps are allowed to run directly on each node. | No |
124
124
| Data at-rest encryption | [BitLocker for OS boot volume](/windows/security/information-protection/bitlocker/bitlocker-overview) | Encrypts the OS startup volume on each node. | No |
Copy file name to clipboardExpand all lines: azure-local/release-information-23h2.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,6 +62,9 @@ If your cluster supports [Solution Builder Extension software updates](./update/
62
62
63
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*.
64
64
65
+
> [!IMPORTANT]
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**.
For more information, see [Release information summary](./release-information-23h2.md).
30
30
@@ -41,16 +41,14 @@ This release has the following features and improvements:
41
41
Existing deployments of Azure Local continue to use OS version **25398.1665**. For more information, see [Release information summary](./release-information-23h2.md).
42
42
43
43
- If you 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.2506** and driver compatible with OS version **26100.4349** or Windows Server 2025.
44
-
45
-
- The new OS media uses consistent device naming (CDN) if the hardware supports it and ensures consistent network adapter naming.
46
44
47
45
-**.NET updates**: This build uses .NET version **8.0.17** for both .NET Runtime and ASP.NET Core. For more information, see [Download .NET 8.0](https://dotnet.microsoft.com/download/dotnet/8.0).
48
46
49
47
-**Software-Defined Networking (SDN) enabled by Azure Arc (Preview)**: Azure Local now supports creating Networking Security Groups (NSGs), configuring Network Security Rules, and assigning them to logical networks and network interfaces. This provides a consistent networking experience across your cloud and edge environment. For more information, see [Software-Defined Networking (SDN) enabled by Azure Arc](./concepts/sdn-overview.md).
50
48
51
49
-**Deployment changes**: To ensure consistent validation before you deploy Azure Local, deployment validators for Microsoft On-premises Cloud and Azure resource bridge are now a part of environment checker.
52
50
53
-
-**Overprovisioning alert**: An alert is added to indicate if a cluster is overprovisioned. Make sure to acknowledge the alert warning before you update as VM workloads are paused during the update run.
51
+
-**Overprovisioning alert**: A warning is shown prior to starting an update if an Azure Local instance is overprovisioned. This alert indicates there is insufficient compute capacity (memory) to live migrate workloads during an update. You must acknowledge this alert before proceeding with an update, as VM workloads will be paused due to the lack of available compute or memory capacity.
54
52
55
53
-**Security improvements**:
56
54
-**New security baseline**: The 2506 release introduces a security baseline with 407 evaluated rules, a 25% increase from the previous 324. Key improvements include:
0 commit comments