Azure Local moves fast, and most of the time that is a good thing. Every few weeks there is a new release, a new feature, a new way to make life on-prem feel a bit more like Azure. But once in a while the news isn’t a shiny new capability, it’s a “stop what you are doing and check your clusters” moment.
TL;DR
- On Azure Local2601 to 2604, a platform component can misclassify VMs during routine operations anddelete them unintentionally. Update the MOC component via the Remediation Support Tool.
- IMDS-based attestationis failing in the field. Windows VMs activated through IMDS are flipping to“not activated”. No official statement yet, AVMA isnota reliable workaround, and the fix is realistically expected in theJuly 2026guest OS update.
Issue 1: Potential unintended VM deletion on 2601 and later
If your Azure Local instance is running 2601, 2602, 2603, or 2604, this one is for you.
A platform component can misclassify virtual machines during routine operations and end up deleting them unintentionally. That is exactly the kind of sentence you don’t want to read on a Friday afternoon. Microsoft has confirmed the issue and blocked further updates on the affected versions while the fix rolls out as a managed component update.
What you should do
- Don’t wait for the next solution update.The fix ships as a managed component update, so you need to push it manually.
- Run the Remediation Support Toolto update theMOCcomponent. This is the standard tool you already use for known-issue mitigations on Azure Local.
- Verifythe MOC component version after the run, and confirm your instance is no longer on the affected build profile.
- Pause non-essential VM lifecycle operationsuntil the MOC component is patched. The misclassification happens during routine operations, so the less churn you create in the meantime, the better.
The official write-up, the affected builds, and the remediation steps live in the Microsoft Learn release notes:
Release notes with fixed and known issues in Azure Local, Microsoft Learn(opens in new window)
If you manage multiple Azure Local instances (customers, sites, regions), this is worth turning into a quick inventory exercise: which clusters are on 2601 and above, which already have the MOC update applied, and which still need attention. The Azure Local Documenter comes in place here; https://www.gettothe.cloud/tool-azure-local-documenter/
Issue 2: IMDS attestation failures, VMs reporting as “not activated”
The second issue is more subtle, and there is no official statement on it yet, but it is showing up in the field often enough that it deserves a heads-up.
IMDS-based attestation can fail, and when it does, the Windows VMs that rely on it for activation flip to “not activated”. For anyone running Windows workloads on Azure Local with IMDS activation, that is a noisy and customer-visible problem.
A few things worth knowing:
- AVMA is not a reliable workaround.It canappearto fix the activation status, but it doesn’t hold. Don’t bake AVMA into your runbook as a permanent answer, you’ll be back to “not activated” before you know it.
- Open a support caseif you’re seeing it. Until Microsoft publishes a KB, support cases are how this gets prioritised and tracked.
- The fix is expected in a future guest OS update.Realistically,July 2026 Patch Tuesdayis the earliest plausible ship date.
What you should do
- Check your fleet for VMs in a“not activated”state on Azure Local, especially anything that recently went through a host update or a live migration cycle.
- If you find affected VMs,open a support caseand reference IMDS attestation failure. The more data points Microsoft has, the better.
- Don’t switch your activation strategy to AVMA in a panic.It is not a fix.
- Plan your guest OS update cadence so you can absorb the July 2026 cumulative update quickly once it lands.
Why this matters
Azure Local sits at a very specific intersection: it’s an Azure service, but the failure modes are on your hardware, in your datacenter, and the blast radius is your VMs. A “platform component misclassifies VMs” headline in pure Azure is a Service Health blip. The same headline on Azure Local is a potentially lost workload.
The official channels will catch up (Microsoft Learn release notes already have Issue 1 documented, and Issue 2 will surface in a KB eventually), but in the meantime the LinkedIn and community grapevine is doing real work.
If you’re running Azure Local in production, this is the time to:
- Patch MOCvia the Remediation Support Tool on every 2601 and later cluster.
- Audit activation statusof your IMDS-activated Windows VMs.
Stay safe out there.
