<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Azure Arc on The Black Cloud</title><link>https://theblackcloud.tech/tags/azure-arc/</link><description>Recent content in Azure Arc on The Black Cloud</description><generator>Hugo</generator><language>en</language><copyright>Copyright © 2026, The Black Cloud.</copyright><lastBuildDate>Fri, 23 Oct 2026 08:00:00 +0100</lastBuildDate><atom:link href="https://theblackcloud.tech/tags/azure-arc/index.xml" rel="self" type="application/rss+xml"/><item><title>Azure Local - 2610 adds post-deployment networking flexibility</title><link>https://theblackcloud.tech/blog/azl2610postdeploymentnetworking/</link><pubDate>Fri, 23 Oct 2026 08:00:00 +0100</pubDate><guid>https://theblackcloud.tech/blog/azl2610postdeploymentnetworking/</guid><description>&lt;p>Yet again, Cristian Edwards has highlighted a very practical Azure Local update 🙌 The important part of 2610 is not just a new deployment option: it gives existing deployments more room to adapt when proxy, security or connectivity requirements change.&lt;/p>
&lt;h2 id="azure-local-2610-networking-updates">Azure Local 2610 networking updates&lt;/h2>
&lt;p>The 2610 release introduces three related post-deployment capabilities:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Update proxy settings and bypass lists&lt;/strong> across an existing Azure Local instance.&lt;/li>
&lt;li>&lt;strong>Enable Azure Arc gateway&lt;/strong> on an existing deployment, rather than having to start again.&lt;/li>
&lt;li>&lt;strong>Move an existing deployment from public-path to private-path connectivity&lt;/strong>, using Azure Firewall explicit proxy and a private network connection.&lt;/li>
&lt;/ul>
&lt;p>Cristian made a great post again, and this graphic is his too 😊 Thanks for sharing it 😊&lt;/p></description></item></channel></rss>