Home / Azure Local

News | Azure Local 2606
Azure LocalNews

News | Azure Local 2606

mmAlex ter Neuzen··Reading Time: 3 min
Reading Time: 3 minutes

The June 2026 update (2606) for Azure Local is a maintenance release. If you were hoping for headline features this month, there aren’t any: build 12.2606.1003.205 is about reliability, bug fixes, and keeping the platform current. Here’s what actually matters when you plan your next update window.

New features
Nothing is specific to 2606. The recent feature waves landed in 2604 (SAN storage GA, disaggregated SAN-only deployments that scale past 16 nodes, GPU acceleration for VMs GA, local identity with Azure Key Vault GA) and 2605 (external SAN over iSCSI in preview, GPU-P metrics). If you skipped those, they are worth a read before you jump on 2606.

Improvements
This build rolls up reliability improvements and bug fixes. The OS moves to 26100.32995 (download the image from the Azure portal), and the .NET runtimes are refreshed to 8.0.28 and 10.0.9. You will need a driver compatible with OS 26100.32995 or Windows Server 2025. On Integrated System or Premier hardware the OS is preinstalled, so coordinate with your OEM for the matching image and driver.

Fixed issues
None are called out as specific to 2606.

Known issues (read before you touch production)
There are no new known issues introduced in 2606, but the carried-over list still applies. The ones worth your attention:

  • Volume deletion in Windows Admin Center can cause data loss.Impact: instances running the Cluster Manager extension below 5.2.6 can hit problems deleting volumes, with potential data loss. Workaround: update the Cluster Manager extension to 5.2.6 (or run WAC 2511 build 2.6.6.18 or higher), and do not delete volumes in WAC until you have.
  • RegBack registry restore is not supported.Impact: restoring the registry via RegBack can strip the LCM and MOC settings and corrupt the solution. Workaround: don’t use RegBack on Azure Local; recover through supported paths.
  • Arc registration fails (AZCMAgent exit code 42).Impact: blocks deployment when registering machines with Azure Arc. Workaround: follow the troubleshooting guide referenced in the release notes (aka.ms/arc/azcmerror).
  • Defender Restrict App Execution breaks Day-2 ops.Impact: Update and Repair can fail when Defender for Endpoint has Restrict App Execution enabled. Workaround: disable Restrict App Execution in the Defender portal and reboot; open a support case if it persists.
  • ASR rule blocks Solution Update.Impact: if the attack surface reduction rule “Block process creations originating from PSExec and WMI commands” is set to Block, Solution Update fails. Workaround: adjust the rule per the troubleshooting guide before updating.
  • Add node / repair node on recalled images.Impact: add and repair operations fail on 11.2510.1002.87 or 12.2510.1002.88 (recalled builds). Workaround: move to 11.2510.1002.93 / 12.2510.1002.94; if you must run the operation mid-update, open a support case to override image validation.
  • Update status misreported in the portal.Impact: the portal can show Failed or In progress when the update actually completed, which risks a duplicate action. Workaround: confirm via PowerShell (get-solutionupdate, then check $Update.state); if Installed, wait up to 24 hours, or restart the Cloud Management cluster group to refresh sooner.
  • Mochostagent service silently stuck.Impact: the service looks healthy but stops updating logs, affecting VM management. Workaround: check C:\ProgramData\mochostagent\logs for fresh entries, then run restart-service mochostagent.
  • VM stop fails with CLI 1.14.x on pre-2604 clusters.Impact: az stack-hci-vm stop fails. Workaround: use the latest CLI with the –skip-shutdown parameter, or downgrade to CLI 1.13.0 or earlier.

Upgrade planning notes
2606 is a low-drama update, but plan the basics: stage the 26100.32995 OS image from the portal, confirm driver compatibility (or get the OEM image for Integrated System and Premier hardware), and make sure any AKS Arc clusters are already on a supported Kubernetes version before you update. If you run Windows Admin Center, patch the Cluster Manager extension first given the volume-deletion data-loss risk. Otherwise this is a clean, incremental hop.

https://learn.microsoft.com/en-us/azure/azure-local/whats-new?view=azloc-2606

Share and Enjoy !

Shares
Tagged:
Related storiesMore in Azure Local →
Designer (23)

Stay close to the action—follow GetToThe.Cloud across social!
Deep dives and hands‑on how‑tos on Azure Local, hybrid cloud, automation, PowerShell/Bicep, AVD + FSLogix, image pipelines, monitoring, networking, and resilient design when the internet/Azure is down.

🔗 Our channels
▶️ YouTube: https://www.youtube.com/channel/UCa33PgGdXt-Dr4w3Ub9hrdQ
💼 LinkedIn Group: https://www.linkedin.com/groups/9181126/
✖️ X (Twitter): https://x.com/Gettothecloud
🎵 TikTok: https://www.tiktok.com/@gettothecloud
🐙 GitHub: https://github.com/GetToThe-Cloud/Website
💬 Slack: DM us for an invite
📲 WhatsApp: DM for the community link

Share

We use cookies to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners. View more
Cookies settings
Accept
Privacy & Cookie policy
Privacy & Cookies policy
Cookies list
Cookie name Active

Who we are

Our website address is: https://www.gettothe.cloud

Comments

When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.An anonymized string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service privacy policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.

Media

If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.

Cookies

If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.If you visit our login page, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select "Remember Me", your login will persist for two weeks. If you log out of your account, the login cookies will be removed.If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.

Embedded content from other websites

Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracking your interaction with the embedded content if you have an account and are logged in to that website.

Who we share your data with

If you request a password reset, your IP address will be included in the reset email.

How long we retain your data

If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.

What rights you have over your data

If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.

Where we send your data

Visitor comments may be checked through an automated spam detection service.
Save settings
Cookies settings