Download websites that use Azure Monitor

A page carrying Azure Monitor was not fitted out by a marketing team. The telemetry comes from whoever runs the infrastructure, and it arrives as the tail end of a decision about where the company's servers live rather than as a choice about the public site.

Microsoft built the product as the observability layer for its own cloud, pulling metrics, logs and traces out of virtual machines, containers, managed services and application code into one queryable workspace. Consolidated under its current name in 2016 and sold on a Proprietary basis tied to Azure consumption, the platform becomes visible to us at one narrow point: the browser instrumentation that application performance monitoring injects into a page so that load timings, script errors and user sessions are reported back from the client.

Detection therefore reads a corner of a much larger deployment. A company can route every server metric and every container log into the platform and never place a single line of telemetry in front of a visitor, in which case we will not see it at all. The signal only works in one direction and should be treated that way. Where the browser snippet is present the conclusion is strong, because nobody instruments a page for a cloud they do not use. Where it is absent, nothing follows.

As a procurement signal, that corner is still worth having. Analytics tooling from a cloud vendor is rarely bought on its own. A site reporting into Azure telemetry belongs to an engineering organisation with a subscription, an identity tenant, a billing relationship and a set of internal skills that make the next Azure service an easier sale than a competing one. Vendors of security tooling, log pipelines, cost management and consulting all care about that boundary, and so do people mapping which industries and which countries have moved their hosting to a single hyperscaler.

As of October 2026 we see Azure Monitor on 6,233 sites, and the list of those sites is the part a per-domain lookup cannot reproduce. Checking one company tells you what one company runs. Downloading the set lets you sort it by industry, by country, by co-installed frameworks and by the ecommerce or content platform underneath, then compare it against the equivalent lists for competing observability products. The dataset carries the raw detections and the accompanying fields rather than a score, so the caveat above stays visible: these are the sites that instrument the browser, which is a real population and a conservative one.