Azure Sentinel, Microsoft's cloud-based security information and event management service, hits general availability, with prices starting at $2.46 per GB
Pricing starts at $2.46 per gigabyte (GB) of ingested data. — Microsoft today took Azure Sentinel out of public preview …
Context & Ripple Effects
Microsoft [[a:939086|unveiled Azure Sentinel in March as a cloud-native way to view and respond to security alerts across corporate networks]], and seven months later it exits public preview as a generally available product with consumption pricing: $2.46 per GB of ingested data rather than a seat or appliance license.
That metered structure matters beyond launch week. It becomes the billing foundation Microsoft later builds AI monetization on top of — [[a:1155784|Copilot for Security's 2024 general availability introduced a separate Security Compute Unit at $4 per hour]] — making the per-GB model the base layer of Microsoft's security revenue stack.
First-order effects
- Customers evaluating a cloud SIEM can now sign production contracts priced purely on data ingested, shifting their cost calculus from license counts to how much telemetry they choose to pipe into Azure.
- Azure Sentinel moves from experiment to billable product inside Azure's catalog, giving Microsoft a security offering whose revenue scales directly with customers' log volumes.
Second-order effects
- Because the price is per GB, customers have a standing financial incentive to filter or sample what they ingest — pressuring Microsoft to keep the service useful even when buyers throttle data, and pushing the value conversation toward analytics quality rather than raw collection.
- Per-GB consumption pricing gives incumbent security vendors selling seat-based or appliance-based SIEM a direct cost comparison to answer, since buyers can benchmark against a published rate card instead of opaque quotes.
Third-order effects
- If the pattern holds, security tooling follows the rest of Azure toward metered infrastructure economics — a trajectory Microsoft extended by layering hourly compute units for AI features on top of ingestion fees, meaning security spend increasingly tracks usage rather than headcount.
- Metering also concentrates leverage with the platform owner: whoever controls both the data pipeline and the pricing unit decides what customers pay as volumes grow, a structural position traditional SIEM vendors without hyperscale clouds struggle to match.
The trend: Enterprise security software is migrating from licensed seats and appliances to hyperscaler-metered consumption pricing, with Microsoft using per-GB ingestion as the foundation that later AI security products bill on top of.