<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>KQL - GetToTheCloud</title><link>https://www.gettothe.cloud/tag/kql/</link><description>Latest KQL posts on GetToTheCloud</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 10 Nov 2026 09:56:00 +0100</lastBuildDate><atom:link href="https://www.gettothe.cloud/tag/kql/index.xml" rel="self" type="application/rss+xml"/><item><title>Azure Local | Extended Monitoring</title><link>https://www.gettothe.cloud/azure-local-extended-monitoring/</link><pubDate>Tue, 10 Nov 2026 09:56:00 +0100</pubDate><guid>https://www.gettothe.cloud/azure-local-extended-monitoring/</guid><category>Azure</category><category>Azure Local</category><category>Infrastructure</category><description>Azure Local ships with health alerts, platform metrics, Insights and Resource Health, but none of it is wired to a person and plain Hyper-V VMs are invisible to Azure. This post walks through a Bicep baseline that routes the right signals and watches the state of every VM on the cluster, plus a script that checks and fixes the prerequisites before it deploys.</description></item></channel></rss>