Azure Local 2607 is a classic operator-focused release.
Don’t expect major new platform capabilities. Instead, Microsoft has spent this cycle fixing the kind of issues that actually wake people up at 02:00. VM lifecycle operations, large-scale environment stability, Arc Resource Bridge deployments, network management and platform scalability all received attention.
If you’re running Azure Local in production, especially at scale, 2607 is worth a look purely for the reliability improvements.
New Features
There are no new Azure Local platform features currently called out for 2607. The available release information focuses on reliability improvements and bug fixes across Azure Local VM management and underlying platform services.
Improvements
The 2607 release is:
- Azure Local version 12.2607.1003.69
- OS build 26100.33158
The biggest improvements are around VM operations and large-scale deployments.
VM Lifecycle Reliability
Several long-standing operational issues have been resolved:
- VM deletion no longer fails when network interfaces have invalid or missing IP assignments.
- VM placement settings are now preserved when VMs are updated using older APIs or tooling.
- VM cluster resources are protected during networking reconciliation failures, reducing VM availability risks.
- Capacity checks before VM operations now return accurate results again.
Networking Improvements
Administrators who encountered logical network issues after upgrades should welcome this release.
Microsoft fixed scenarios where:
- Network interface updates failed after upgrades due to overlapping IP ranges.
- DNS server configuration disappeared from Azure Portal and Azure CLI views despite remaining functional.
- Obsolete logical network status fields created operational confusion.
Scalability Improvements
2607 contains multiple fixes specifically targeting larger Azure Local environments:
- VM agent crashes on clusters up to 64 nodes were resolved.
- Monitoring services received memory allocation improvements.
- VM management components no longer exceed memory limits and get terminated.
- Excessive background logging and unnecessary update activity were reduced.
- Internal configuration database scaling improvements prevent space exhaustion in environments with more than 2,000 VMs.
Arc Resource Bridge Deployment Improvements
A version mismatch between internal deployment components previously caused Arc Resource Bridge deployments to stall and eventually time out after approximately two hours.
Microsoft aligned the deployment components to eliminate this issue.
Fixed Issues
From an operations perspective, the most important fixes in 2607 are:
VM Deletion Reliability
VM deletion operations could fail with:
“An invalid IP address was specified”
This could leave a VM and its network interface stuck in Azure Local. Microsoft has corrected the underlying issue.
Placement Preservation
Updating VMs through older tooling could silently remove placement configuration, potentially impacting workload placement behaviour. Placement settings are now preserved during updates.
VM Availability Protection
If networking reconciliation failed during VM management operations, Azure Local could previously remove the underlying cluster resource, putting VM availability at risk. This behaviour has been corrected.
Large-Scale Stability
Multiple memory, logging and component stability fixes were implemented for environments running thousands of VMs. These fixes target monitoring reliability, cluster operations and management plane health.
KNOWN ISSUES
Azure Key Vault Extension Shows Failed After Upgrade
This is currently the only release-specific issue listed for 2607.
Impact
After upgrading to Azure Local 2607, the Azure Key Vault extension might remain in a Failed state. This can create confusion when validating extension health after an upgrade.
Workaround
Microsoft currently documents the issue but does not publish a workaround in the release notes. Administrators should be aware of the behaviour when validating upgrade success.
Additional Operational Issues Still Worth Reviewing
Although not introduced by 2607, the following carried-over issues remain relevant:
- Windows Admin Center volume deletion risks when older Cluster Manager extensions are used.
- Arc registration failures (AZCMAgent exit code 42).
- Mochostagent service becoming unhealthy while appearing operational.
- Azure Portal update status mismatches.
- Defender and Attack Surface Reduction settings blocking updates.
- Add-node and repair-node failures on recalled images.
Upgrade Planning Notes
Before upgrading:
- Validate OS and hardware compatibility with build 26100.33158.
- Review environments using older VM automation tooling.
- Review large-scale deployments for opportunities to benefit from the memory and scalability fixes.
- Validate Azure Key Vault extension health after the upgrade and be prepared for the documented false Failed state.
2607 is not about shiny new features.
It’s about making Azure Local behave more predictably under pressure.
If you run large clusters, rely heavily on Azure Local VM operations, or have experienced Arc Resource Bridge deployment issues, this release delivers meaningful operational improvements and should be on your radar.
