<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Known Issues on The Black Cloud</title><link>https://theblackcloud.tech/tags/known-issues/</link><description>Recent content in Known Issues on The Black Cloud</description><generator>Hugo</generator><language>en</language><copyright>Copyright © 2026, The Black Cloud.</copyright><lastBuildDate>Tue, 28 Jul 2026 09:00:00 +0100</lastBuildDate><atom:link href="https://theblackcloud.tech/tags/known-issues/index.xml" rel="self" type="application/rss+xml"/><item><title>Azure Local - 2607 known issues</title><link>https://theblackcloud.tech/blog/azl2607knownissues/</link><pubDate>Tue, 28 Jul 2026 09:00:00 +0100</pubDate><guid>https://theblackcloud.tech/blog/azl2607knownissues/</guid><description>&lt;p>Very brief post to make some of you aware of the &amp;ldquo;known issues&amp;rdquo; page for Azure Local for 2607 release.&lt;/p>
&lt;p>Not much there, but what is there is pretty important.&lt;/p>
&lt;h2 id="microsofts-known-issues">Microsoft&amp;rsquo;s known issues&lt;/h2>
&lt;p>The official list can be found - &lt;a href="https://learn.microsoft.com/en-us/azure/azure-local/known-issues?view=azloc-2607#known-issues">Known issues in Azure Local 2607&lt;/a>.&lt;/p>



&lt;style>
 .known-issues-table {
 width: 100%;
 margin-bottom: 20px;
 table-layout: fixed;
 overflow-wrap: break-word;
 border: 1px solid #1d3b53;
 border-collapse: collapse;
 color: #d6deeb;
 }

 .known-issues-table th {
 padding: 10px;
 border: 1px solid #1d3b53;
 background-color: #1d3b53;
 color: #7fdbca;
 font-weight: 700;
 text-align: left;
 vertical-align: top;
 }

 .known-issues-table td {
 padding: 10px;
 border: 1px solid #1d3b53;
 text-align: left;
 vertical-align: top;
 }

 .known-issues-table tbody tr:nth-child(even) {
 background-color: rgba(127, 219, 202, 0.06);
 }

 .known-issues-table tbody tr:hover {
 background-color: rgba(127, 219, 202, 0.12);
 }

 .known-issues-table caption {
 padding-bottom: 10px;
 color: #7fdbca;
 font-size: 20px;
 font-weight: 700;
 text-align: left;
 }

 .known-issues-table th:nth-child(1),
 .known-issues-table td:nth-child(1) {
 width: 16%;
 }

 .known-issues-table th:nth-child(2),
 .known-issues-table td:nth-child(2) {
 width: 40%;
 }

 .known-issues-table th:nth-child(3),
 .known-issues-table td:nth-child(3) {
 width: 44%;
 }

 .known-issues-table-wrapper {
 width: 100%;
 overflow-x: auto;
 margin-bottom: 20px;
 }

 @media screen and (max-width: 700px) {
 .known-issues-table {
 min-width: 650px;
 table-layout: auto;
 }

 .known-issues-table th,
 .known-issues-table td {
 padding: 8px;
 }
 }
&lt;/style>

&lt;div
 class="known-issues-table-wrapper"
 role="region"
 aria-label="Azure Local 2607 known issues"
 tabindex="0"
>
 &lt;table class="known-issues-table">
 &lt;caption>Azure Local 2607 known issues&lt;/caption>

 &lt;thead>
 &lt;tr>
 &lt;th scope="col">Feature&lt;/th>
 &lt;th scope="col">Issue&lt;/th>
 &lt;th scope="col">Workaround&lt;/th>
 &lt;/tr>
 &lt;/thead>

 &lt;tbody>
 &lt;tr>
 &lt;td>Update&lt;/td>
 &lt;td>
 After updating Azure Local to version 2607, the Azure Key Vault
 extension might remain in a &lt;strong>Failed&lt;/strong> state.
 &lt;/td>
 &lt;td>
 There's no known workaround in this release.
 &lt;/td>
 &lt;/tr>

 &lt;tr>
 &lt;td>Azure Local VMs&lt;/td>
 &lt;td>
 Trusted Launch VMs (TVMs) created in earlier releases of Azure Local
 fail to start after the cluster is upgraded to 2607.
 &lt;/td>
 &lt;td>
 There's no known workaround in this release. If your Azure Local
 cluster has TVMs, don't upgrade to 2607. If you already upgraded to
 2607, don't start any existing TVMs.
 &lt;/td>
 &lt;/tr>
 &lt;/tbody>
 &lt;/table>
&lt;/div>



&lt;h2 id="key-takeaways">Key takeaways&lt;/h2>
&lt;ul>
&lt;li>&lt;strong>Update Issue&lt;/strong>: If you update to 2607, you might need to manually fix the Azure Key Vault extension. Or just wait for the next release which will hopefully resolve this issue.&lt;/li>
&lt;li>&lt;strong>TVM Issue&lt;/strong>: If you have Trusted Launch VMs, do NOT upgrade to 2607 or do NOT start existing TVMs after upgrading. I guess the first option is the only reasonable one, as I do not really believe that those who use those VMs can afford NOT to power them on. Unclear if there will be a hotfix for 2607 or 2608 will fix those issues, but this seems pretty critical to get fixed ASAP.&lt;/li>
&lt;/ul>
&lt;div class="alert alert-danger">
 &lt;div class="alert-heading">&lt;svg xmlns="http://www.w3.org/2000/svg" width="18" height="18" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round">&lt;path d="M10.29 3.86L1.82 18a2 2 0 0 0 1.71 3h16.94a2 2 0 0 0 1.71-3L13.71 3.86a2 2 0 0 0-3.42 0z"/>&lt;line x1="12" y1="9" x2="12" y2="13"/>&lt;line x1="12" y1="17" x2="12.01" y2="17"/>&lt;/svg>
 &lt;span>CRITICAL&lt;/span>
 &lt;/div>
 &lt;div class="alert-content">
 Do NOT upgrade to 2607 if you have Trusted Launch VMs!
 &lt;/div>
&lt;/div>
&lt;h2 id="useful-links">Useful links&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://learn.microsoft.com/en-us/azure/azure-local/release-information-23h2?view=azloc-2607&amp;amp;tabs=OS-build-26100-xxxx%2COS-build-26100-xxx">Azure Local release information&lt;/a>&lt;/li>
&lt;/ul></description></item></channel></rss>