Microsoft Azure

What Is Microsoft Azure?

Microsoft Azure is Microsoft's public cloud platform, offering virtual machines, managed application hosting, databases, networking, storage, identity, and a large catalog of higher-level services across a global footprint of regions. Launched in 2010 and rebranded from "Windows Azure" to "Microsoft Azure" in 2014 to reflect its support for both Windows and Linux, it is the natural cloud home for organizations invested in the Microsoft ecosystem and one of the "big three" public clouds.

The concise definition: Azure lets organizations build, deploy, and manage applications on Microsoft's global infrastructure on a pay-as-you-go basis, with especially deep integration into Microsoft products such as Windows Server, Active Directory, Microsoft 365, and the .NET ecosystem. When a site belongs to an enterprise standardized on Microsoft technologies, Azure is frequently the platform behind it.

On market position, Azure is consistently reported as the second-largest cloud infrastructure provider, behind AWS and ahead of Google Cloud. This ranking is well established qualitatively and published quarterly by analyst firms such as Synergy Research and Canalys; the precise share percentage shifts over time, and Microsoft's reporting historically bundled Azure within a broader "Intelligent Cloud" segment, so treat any exact figure with caution and rely on the durable fact that Azure holds a clear second place.

For detection, the important implication is that Azure fronts much of its traffic through recognizable edge and routing layers that emit x-azure-ref and related headers, hosts many applications on *.azurewebsites.net, and sets distinctive affinity cookies, all of which produce fairly clear fingerprints, subject to the usual CDN-masking caveat.

How Microsoft Azure Works

Azure is a layered catalog of services that customers compose into applications. The components most relevant to public websites, and to identifying them, are the following.

• Azure Virtual Machines. Configurable Windows or Linux VMs across many sizes. A site may run IIS, Nginx, or Apache directly on a VM, in which case the web server, not Azure, populates the Server header.
• Azure App Service. A managed platform for hosting web apps, APIs, and mobile backends, one of the most common ways to run web applications on Azure. App Service apps live on *.azurewebsites.net by default.
• Azure Functions. Serverless compute that runs code in response to events, frequently used for APIs and background processing.
• Azure Kubernetes Service (AKS). Managed Kubernetes with deep Azure integration for containerized workloads.
• Azure Front Door and Azure CDN. Global edge layers that provide load balancing, acceleration, and caching, and that emit recognizable routing headers.
• Azure Blob Storage. Object storage that serves static assets and downloads, typically from *.blob.core.windows.net, sometimes fronted by the *.azureedge.net CDN domain.

Underpinning these services, Azure organizes resources into subscriptions and resource groups, manages identity through Microsoft Entra ID (formerly Azure Active Directory), and meters usage on a pay-as-you-go basis with reservations and savings plans for discounts. Azure's signature strengths are its hybrid-cloud tooling (extending management to on-premises and other clouds through Azure Arc) and its tight coupling with the broader Microsoft stack, which is why it dominates in enterprises already running Windows Server, Active Directory, and Microsoft 365.

How to Tell if a Website Uses Microsoft Azure

Azure leaves recognizable traces across HTTP headers, hostnames, cookies, and IP ownership. Read them together, since a third-party CDN can hide the Azure origin and since some signals indicate only the edge layer.

Azure routing and edge headers

The clearest tells are the Azure-specific routing headers added by Front Door and related edge services:

• x-azure-ref is a reference identifier added by Azure Front Door and other Azure edge layers; its presence is a strong indicator that the request is being served through Azure's edge.
• X-MSEdge-Ref is a related Microsoft edge reference header seen on Azure and other Microsoft-fronted traffic.
• x-cache and Via headers may name the Azure CDN when caching is involved.

Read these with curl -I https://example.com or in the browser DevTools Network tab by clicking the document request and inspecting its response headers. Wappalyzer and similar tools also recognize Azure App Service, Front Door, and the Azure CDN.

Affinity cookies

Azure App Service uses Application Request Routing for session affinity, which sets a distinctive cookie:

• ARRAffinity (and its secure counterpart ARRAffinitySameSite) is set by Azure App Service to pin a session to a particular instance.

Spotting an ARRAffinity cookie in the Set-Cookie response header or the DevTools Application tab is one of the most reliable signs that a site runs on Azure App Service specifically.

Hostnames and asset domains

Default Azure domains are direct giveaways when they appear in URLs, redirects, or asset references:

• *.azurewebsites.net is the default domain for Azure App Service applications.
• *.azureedge.net is the Azure CDN domain.
• *.blob.core.windows.net indicates Azure Blob Storage, while other *.core.windows.net subdomains map to Azure Storage services (files, queues, tables).
• *.trafficmanager.net indicates Azure Traffic Manager DNS-based routing.

Even when a site uses a custom domain, assets or fallback hostnames frequently reveal these underlying Azure domains.

IP ranges and reverse DNS

Network-level checks add confirmation. Resolve the domain with dig example.com or nslookup example.com, then examine the address:

• Published IP ranges. Microsoft publishes downloadable Azure IP range files (the "Azure IP Ranges and Service Tags" datasets). Checking whether a site's IP falls within Azure's ranges, and which service tag it belongs to, confirms Azure hosting and can hint at the service.
• Reverse DNS. Reverse lookups on Azure addresses sometimes resolve into Microsoft-owned netblocks or cloudapp.azure.com-style hostnames, which, combined with Azure headers, is strong corroboration.

The crucial caveat: CDNs mask the origin

As with every cloud, the edge can hide the origin and vice versa. If an Azure-hosted application sits behind a third-party CDN such as Cloudflare or Fastly, the public Server header reads cloudflare or Fastly and the Azure origin is concealed. Conversely, an x-azure-ref header confirms the request is served through Azure's edge but does not reveal which backend, App Service plan, or region ultimately handles it. And a site on a bare Azure VM may simply report IIS or Nginx in the Server header with no Azure-specific value at all. Because of this, no single header is definitive. Combine routing headers, the ARRAffinity cookie, Azure hostnames, reverse DNS, and IP-range checks, and where possible rely on a server-side analysis that correlates them rather than trusting the edge alone.

Key Features

Azure's catalog is broad, with particular depth in enterprise integration and hybrid cloud. The capabilities most relevant to hosting and identifying websites include:

• Managed application hosting. Azure App Service for web apps and APIs, plus Azure Functions for serverless workloads, both with minimal infrastructure management.
• Flexible compute. Windows and Linux virtual machines across many sizes, and AKS for managed Kubernetes.
• Deep Microsoft integration. Native ties to Microsoft Entra ID (Active Directory), Microsoft 365, Windows Server, and the .NET ecosystem, including single sign-on across thousands of SaaS apps.
• Hybrid cloud leadership. Azure Arc extends Azure management to on-premises and other clouds, and Azure Stack brings Azure services into private data centers.
• Global edge and delivery. Azure Front Door and Azure CDN for global load balancing, acceleration, and caching.
• Storage and databases. Azure Blob Storage, Azure SQL Database, and globally distributed Cosmos DB.
• Compliance breadth. One of the largest portfolios of compliance certifications across regulated industries and governments.

Pros and Cons

Azure's strengths cluster around enterprise integration, hybrid cloud, and compliance; its drawbacks relate to complexity and a reputation for occasional reliability and portal-usability friction.

Pros

• Unmatched integration with Microsoft products such as Active Directory, Microsoft 365, and Windows Server.
• The strongest hybrid-cloud story through Azure Arc and Azure Stack.
• An extensive portfolio of compliance certifications suited to regulated industries and government.
• First-class support for the .NET ecosystem and Windows workloads, plus full Linux support.
• A natural, low-friction path for organizations already standardized on Microsoft.

Cons

• A steep learning curve and a portal experience many find more complex than competitors'.
• Pricing can be intricate, with many SKUs and tiers that make cost estimation difficult.
• Historically more prone to high-profile regional outages than some rivals, demanding resilient architectures.
• Best value is realized within the Microsoft ecosystem; benefits are smaller for non-Microsoft stacks.

Azure vs Alternatives

Azure is most often compared with Amazon Web Services and Google Cloud Platform, the other two of the big three. The table summarizes the trade-offs.

Feature	Microsoft Azure	AWS	Google Cloud (GCP)
Market position	Second-largest	Largest by share	Third of the big three
Signature strength	Enterprise / Microsoft stack, hybrid	Breadth and scale	Data, analytics, AI
Identity integration	Microsoft Entra ID (Active Directory)	IAM	Cloud IAM
Edge/CDN	Azure Front Door / Azure CDN	CloudFront	Cloud CDN
Detection header tell	x-azure-ref, ARRAffinity cookie	x-amz-cf-id, AmazonS3	Server: Google Frontend
Hybrid tooling	Strongest (Azure Arc/Stack)	Outposts	Anthos

If an organization is choosing between clouds, the most common cross-shop is AWS for breadth and scale, while Azure tends to win where Microsoft integration, hybrid cloud, and compliance are decisive.

Use Cases

• Enterprise .NET and Windows workloads. Web apps, APIs, and services built on the Microsoft stack, hosted on App Service or Windows VMs.
• Hybrid and multi-cloud management. Extending consistent governance to on-premises and other clouds through Azure Arc.
• Identity-centric applications. Apps that authenticate users through Microsoft Entra ID with single sign-on across corporate and SaaS systems.
• Regulated-industry hosting. Healthcare, finance, and government workloads that depend on Azure's compliance breadth.
• Containerized and serverless apps. AKS for orchestrated microservices and Azure Functions for event-driven backends.
• Infrastructure and competitive research. Detecting Azure, and which services a site uses, supports lead generation, vendor analysis, and architecture review. See our guides on how to find out where a website is hosted and how to read a website's HTTP headers.

Frequently Asked Questions

How can I tell if a website is hosted on Microsoft Azure?

Use several signals together. Inspect HTTP headers with curl -I https://example.com or the DevTools Network tab and look for x-azure-ref or X-MSEdge-Ref, which indicate Azure's edge. Check for an ARRAffinity cookie, which strongly implies Azure App Service. Examine hostnames and asset domains for *.azurewebsites.net, *.azureedge.net, or *.blob.core.windows.net. Then resolve the domain with dig or nslookup, do a reverse-DNS lookup, and check the IP against Microsoft's published Azure IP range and service-tag files. Our guide on how to find out where a website is hosted covers the broader methodology.

What does the ARRAffinity cookie tell me?

The ARRAffinity cookie is set by Azure App Service's Application Request Routing feature to provide session affinity, pinning a visitor's session to a specific server instance so stateful applications behave consistently. Its presence is one of the most reliable indicators that a site runs specifically on Azure App Service, as opposed to a bare VM or another platform. You will see it in the Set-Cookie response header or under Cookies in the browser DevTools Application tab. Note that operators can disable affinity or rename the cookie, so its absence does not rule out App Service, but its presence is strong positive evidence.

What is the x-azure-ref header?

x-azure-ref is a reference identifier that Azure Front Door and other Azure edge services attach to responses, primarily to help Microsoft support trace a specific request through their infrastructure. For detection purposes, its presence is a strong indication that the request is being served through Azure's edge or routing layer. Like other tracing headers it is informational and usually left in place, which makes it a useful fingerprint, though it can be stripped by a proxy in front. Importantly, it tells you the request passed through Azure's edge, not which backend service or region ultimately handled it, so corroborate with other signals.

Why does Azure use the azurewebsites.net domain?

*.azurewebsites.net is the default domain that Azure App Service automatically assigns to every web app, so a freshly created app is reachable at something like myapp.azurewebsites.net before any custom domain is configured. Even after a custom domain is added, the underlying azurewebsites.net hostname usually continues to work and frequently appears in redirects, certificates, or asset references. Spotting that domain, whether in the address bar, a redirect chain, or a resource URL, is a direct indication that the site is hosted on Azure App Service. The analogous default domains are *.appspot.com and *.run.app on Google Cloud.

Is Azure bigger than AWS?

No. Azure is consistently reported as the second-largest cloud infrastructure provider, behind AWS and ahead of Google Cloud. This ordering has held for years and is published quarterly by analyst firms. The exact share percentages shift over time, and Microsoft has historically reported Azure inside a broader cloud segment rather than as a standalone figure, which complicates precise comparisons. The reliable takeaway is the durable ranking, Azure is a clear second, rather than any specific percentage that may be out of date or defined differently by different analysts.

Why might an Azure-hosted site show no Azure headers at all?

Because a layer in front of Azure can hide them, or because the site runs on infrastructure that does not emit Azure-specific headers. If the site sits behind a third-party CDN such as Cloudflare or Fastly, that CDN sets its own Server header and the Azure origin is masked. And a site running on a plain Azure virtual machine will typically report its web server, such as IIS or Nginx, in the Server header, with no Azure-specific value, because the VM is just infrastructure. In both cases the absence of Azure headers does not rule out Azure; you need hostname checks, reverse DNS, IP-range lookups, and ideally a server-side analysis to identify the origin, as explained in our guide on how to read a website's HTTP headers.

Need to look past the edge and confirm whether a site's true origin runs on Microsoft Azure? Run a server-side analysis with StackOptic.