Microsoft Sentinel for mid-sized companies: what drives the costs and when it pays off
Key takeaways
- Microsoft Sentinel costs depend mainly on the volume of data you ingest into the analytics tier. Billing is per gigabyte, either pay-as-you-go or through commitment tiers starting at 100 GB per day.
- Free data includes the Azure activity log, the Office 365 audit logs for SharePoint, Exchange and Teams, and alerts and incidents from Microsoft Defender. Raw data such as Entra sign-in logs or Defender device tables is charged.
- In the analytics tier, Sentinel data can be retained for up to 90 days at no extra charge. For long-term retention and data with lower detection value there is the Sentinel data lake, with its own usage-based meters.
- After 31 March 2027, Microsoft Sentinel will only be supported in the Defender portal. There, Defender raw data can be queried for 30 days without ingesting it into Sentinel.
- Measure the volume before deciding: with the
Usagetable in an existing workspace, during the 31-day trial and with Microsoft’s cost estimator.
“What does Sentinel cost?” is one of the first questions management asks us when a SIEM is on the table. A SIEM (security information and event management) collects logs from many sources and analyses them centrally. There is no serious answer without knowing your data sources, because Sentinel has no price per user or device. You pay for data. For mid-sized companies that is good news, because the choice of sources controls the costs. It is also a risk, because a single verbose firewall can break the budget. This article explains the pricing model, the cost drivers and how to calculate before you start. We deliberately do not quote prices. They change and depend on region and contract; current figures are on the Microsoft Sentinel pricing page.
How is Microsoft Sentinel billed?
Sentinel runs on a Log Analytics workspace in Azure. Since July 2023, Microsoft has combined the costs for Log Analytics and Sentinel into simplified pricing tiers. Older workspaces may still be on classic tiers with separate line items and can be switched.
Analytics tier. This is where the data your detection rules run on lives. There are two ways to pay:
- Pay-as-you-go: you pay per gigabyte (10^9 bytes) and optionally for retention beyond 90 days.
- Commitment tiers: you commit to a daily volume, starting at 100 GB per day, at a lower price per gigabyte. Usage above the commitment is billed at the same discounted rate. You can move up at any time; moving to a lower tier is only possible after 31 days.
Microsoft additionally offers a pre-purchase plan with commit units for one year.
Data lake tier. The Microsoft Sentinel data lake has its own meters: ingestion and processing per gigabyte for tables that live only in the data lake, storage per gigabyte per month at a flat 6:1 compression rate, queries per gigabyte of data scanned, and compute hours for notebooks. Data you ingest into the analytics tier is mirrored to the data lake automatically. As long as total retention equals analytics retention, there are no additional data lake costs for it.
Other costs. Playbooks based on Azure Logic Apps and data connectors that use Azure Functions are billed separately.
Which data is free and which drives the costs?
Microsoft lists the following data types as free:
| Free | Typically charged |
|---|---|
Azure activity log (AzureActivity) | Entra sign-in and audit logs (SigninLogs, AuditLogs) |
Office 365 audit logs for SharePoint, Exchange and Teams (OfficeActivity) | Raw data from Defender for Endpoint, Identity, Office 365 and Cloud Apps |
Alerts from Defender XDR, Defender for Endpoint, Identity, Office 365, Cloud Apps, Defender for Cloud and Entra ID Protection (SecurityAlert) | Windows security events (SecurityEvent) |
Incidents from Defender XDR (SecurityIncident) | Firewall, proxy and network logs, for example through CEF or Syslog |
Sentinel health data (SentinelHealth) | Logs from line-of-business applications and Azure resources |
Two benefits matter for many companies. With Defender for Servers Plan 2 you receive 500 MB of free ingestion per server per day for certain security tables, including SecurityEvent. Microsoft 365 E5 customers also receive an allowance for certain Microsoft data, which appears on the bill as “Free Benefit - M365 Defender Analysis”. Check the scope and conditions of this allowance with Microsoft or your licensing partner before planning.
In assessments we see three typical cost drivers: firewall and proxy logs recording every single connection, Windows security events collected with the “All events” setting, and Defender raw data tables connected in full without a specific purpose. For Windows events, data collection rules help: instead of “All events”, choose the “Common” or “Minimal” sets or filter specific event IDs at the source.
Analytics tier or data lake: which data belongs where?
Microsoft distinguishes two categories. Primary security data is needed for detection rules, correlation and fast search, such as sign-in logs, EDR data and audit logs from cloud platforms. It belongs in the analytics tier, where it can be retained for up to 90 days at no extra charge and, for a fee, for up to two years. Check the setting per table; the default is often 30 days. Secondary security data is high in volume and of limited value on its own, such as NetFlow, firewall or proxy logs. It belongs in the data lake, where it can be kept for up to twelve years and queried with KQL. KQL jobs summarise it and write the result to the analytics tier where needed.
One point matters for planning: detection rules only run on data in the analytics tier. Anything that needs continuous monitoring belongs there.
Older documents and invoices still mention basic logs, auxiliary logs and archive. After onboarding to the data lake, Microsoft bills long-term retention, search and auxiliary ingestion through the data lake meters, and auxiliary tables become part of the data lake. Onboarding takes place in the Defender portal and requires a primary Sentinel workspace connected there. For regulated organisations it is important that customer-managed keys (CMK) are not supported for data stored in the data lake; that data is encrypted with Microsoft-managed keys. Check this against your encryption requirements before moving data into the data lake.
What does the move to the Defender portal change for costs?
Microsoft Sentinel is generally available in the Defender portal, even without Defender XDR or an E5 licence. After 31 March 2027, Sentinel will no longer be supported in the Azure portal. Many customers who first set up Sentinel after 1 July 2025 were onboarded to the Defender portal automatically.
One point is particularly relevant for costs: in the Defender portal, the advanced hunting raw data from Defender XDR is available for queries for 30 days without ingesting it into Sentinel. Custom detection rules can query Defender and Sentinel tables together. Microsoft explicitly recommends this approach for use cases involving Defender and Sentinel data where you do not need the Defender data for longer than 30 days. Only ingest Defender raw data into Sentinel if you must keep it longer or a specific analysis requires it. How Defender XDR and Sentinel work together is covered in detail in our article on Defender XDR and Microsoft Sentinel.
How do you estimate the volume before you start?
By measuring rather than assuming. Three ways, in this order:
- Analyse an existing workspace. If you already send data to a Log Analytics workspace, for example Entra logs through a diagnostic setting, the
Usagetable shows the billable volume per table for the past 31 days:
Usage
| where TimeGenerated > ago(32d)
| where StartTime >= startofday(ago(31d)) and EndTime < startofday(now())
| where IsBillable == true
| summarize BillableGB = round(sum(Quantity) / 1000., 2) by DataType
| order by BillableGB desc
- Use the trial. After you enable Sentinel on a workspace, the first 10 GB per day in the analytics tier are free for 31 days. Connect the planned sources during this period and measure with the same query. Charges for automation and the data lake still apply during the trial.
- Cost estimator. With the measured values, the Microsoft Sentinel cost estimator produces a reliable monthly estimate.
Then record for each source whether it goes into the analytics tier, into the data lake or is not connected at all, and for what purpose. Operational data without a security purpose belongs in a separate workspace without Sentinel, so that it does not incur Sentinel costs. A budget with an alert in Microsoft Cost Management reports rising volumes.
When does Sentinel pay off for a mid-sized company?
If your environment consists essentially of Microsoft 365, Entra ID and managed Windows devices, a well-run Defender XDR is the foundation and often sufficient. Sentinel pays off when at least one of these applies:
- You need to analyse sources outside Microsoft, such as firewalls, Linux servers or line-of-business applications.
- You need logs for longer than 30 days, for example as evidence for auditors, supervisors or insurers.
- You want to run your own detection rules for your environment.
- You manage several tenants.
Sentinel does not pay off if nobody assesses the alerts. The licence costs are then the smaller item; the bigger risk is a tool that finds incidents nobody responds to. Plan the operating model as well: who triages, within what time and following which procedure.
Next step
In our Security Assessment, at a fixed price, we determine which sources make sense for you, how much volume they generate and whether Defender XDR alone is enough. If you do not want to run Sentinel yourself, our Managed Security service takes over data onboarding, cost control and triage according to agreed procedures.
Frequently asked questions
What does Sentinel cost for a company with 200 employees?
The number of employees does not determine it. What matters are the connected sources and their daily volume. Two companies of the same size can differ considerably, depending for example on whether firewall logs flow into the analytics tier in full. Measure the volume during the trial and calculate from there.
Is a commitment tier worth it?
Only when your daily volume is consistently close to the smallest tier of 100 GB per day. Below that, pay-as-you-go remains the right choice. Review the trend monthly; moving down a tier is only possible after 31 days.
Can we put a hard limit on costs?
Log Analytics offers a daily cap. When it is reached, data collection stops until the next day and the data from that period is lost. Microsoft itself advises against using it to reduce costs. For a security system we recommend budget alerts, ingestion-time filtering through transformations and a deliberate choice of sources.
Are the free sources a sensible start?
Yes. The Azure activity log, Office 365 audit logs and Defender alerts incur no ingestion charges and cover important cases, such as suspicious forwarding rules or deleted Azure resources. Entra sign-in logs are charged, but because of their high detection value they belong in almost every environment.
Book an introductory call