Azure subscriptions in the context graph and investigations
Connect an Azure subscription with one Azure Lighthouse template so Polylane adds its resources to the context graph, watches their health and investigates Azure Monitor alerts.
What changed
Connect an Azure subscription by deploying one template in the
Azure portal, the same way you connect
AWS with a CloudFormation stack. Polylane stores no
Azure credential: access is delegated through
Azure Lighthouse and you can remove it at any time.
Polylane adds the subscription's resources to the context graph with Microsoft's own icons, including the network path from a virtual machine to its subnet, security group and public IP. It syncs every 15 minutes, and Event Grid brings each resource change in between syncs. A Cloudflare tunnel that runs in an
Azure virtual network links to the
Azure resources behind it.
It charts Azure Monitor metrics and watches each production resource, checks Resource Health for resources that are down or failed to deploy, and reads Log Analytics for errors. When you allow it, Polylane creates
Azure Monitor alert rules and investigates the alerts they send. Investigations can query Resource Graph, run KQL over a Log Analytics workspace and read the Activity Log. See the Azure integration.
Why it matters
Azure often runs next to other clouds. With the subscription in the same context graph, an investigation can follow a request from a
Cloudflare tunnel to the virtual machine behind it, and read the Activity Log to see who changed what.
How to use it
- In Polylane, choose Connect
Azure and decide whether Polylane can create alert rules. Then choose Deploy on
Azure and Open the
Azure portal.
- In the portal, select the subscription and a region for the deployment record, then choose Review + create and Create. You need the Owner role on the subscription.
- Keep the Polylane page open. It continues when
Azure confirms the delegation, usually after one to two minutes.