Sourcemap Explorer
Stack · PaaS

Azure

Azure is a cloud computing service for building, testing, deploying, and managing applications and services through Microsoft-managed data centers.

PaaS

What detecting Azure tells you about a site

Microsoft Azure is detected from delivery and edge artefacts rather than the page itself: assets on *.azureedge.net or blob.core.windows.net, an x-azure-ref / x-ms-* response header, or an *.azurewebsites.net App Service hostname. Finding Azure leans enterprise — it is the cloud of choice for organisations already invested in Microsoft (Active Directory, .NET, Office 365), so its presence often correlates with a corporate or regulated environment and a .NET-leaning backend more than a startup's greenfield stack.

Azure in a real-world stack

When you find Azure, it rarely travels alone. Frequently paired with a .NET/ASP.NET backend, Azure AD / Entra ID for identity, and Azure Front Door or CDN on the edge.

About

Azure is a cloud computing service for building, testing, deploying, and managing applications and services through Microsoft-managed data centers.

Categories: PaaS

Quick facts

CategoriesPaaS

Detection methodology for PaaS

Platform-as-a-Service offerings show up as response headers and deployment domains. Heroku's `Server: Cowboy` plus `*.herokuapp.com`; Render's `*.onrender.com`; Fly.io's `*.fly.dev`. We pair the host detection with framework signals so you can tell what's running on the platform — a Heroku dyno serving Rails looks very different from a Heroku dyno serving Node, even though both fit the same hosting fingerprint.

How we detect Azure

Sourcemap Explorer carries 10 fingerprint signals for Azure, spread across 2 channels — response header and cookie. The exact patterns are listed below, and you can replay each one in Chrome DevTools to confirm a match by hand.

Each signal alone is rarely conclusive — Sourcemap Explorer cross-references all of them and weights by confidence. You can reproduce any of these checks yourself in Chrome DevTools.

Response header

Server-side fingerprint: the response header reveals the technology behind the page. Visible in DevTools → Network → response headers.

azure-regionname:
azure-sitename:
azure-slotname:
azure-version:
server: ^Windows-Azure
x-ms-client-request-id:
x-ms-correlation-request-id:
x-ms-gateway-requestid:
Cookie

Cookies set by the platform. Visible in DevTools → Application → Cookies.

ARRAffinity
TiPMix

FAQ

How do I check if a website is using Azure?

Open the page in Chrome, click the Sourcemap Explorer toolbar icon, and read the Stack tab. Azure's specific fingerprints here are response header and cookie, and the popup flags Azure whenever any combination of them is found. The same checks can be reproduced manually in DevTools — see the "How we detect" section above.

What Azure version can Sourcemap Explorer detect?

Azure ships as a hosted paas rather than a bundled npm package, so version-specific detection isn't always possible. Where the platform leaks a version in response headers (`X-Powered-By`, `Server`, generator meta tags) we surface it; otherwise we report presence only.

Where can I read more about Azure?

Official site: https://azure.microsoft.com. For Sourcemap Explorer's detection guide, see the deep-dive link below or the related guides in the cross-link section.

Keep reading on Sourcemap Explorer

Alternative tools

Detected by Sourcemap Explorer

Open the popup on any page running Azureand you'll see the exact version pulled from the bundled package.json when sourcemaps are exposed.

Install free on Chrome