Controlling Microsoft Sentinel costs across customer workspaces
Reviewed by ContraForce
Microsoft Security · Best practice · Intermediate · 5 min read
How to keep Microsoft Sentinel spend under control in each customer workspace: table tiers, commitment tiers, retention, ingestion-time filtering, free data sources and usage monitoring.
Each of your customers has its own Microsoft Sentinel workspace and its own Azure bill. The size of that bill comes down to a few decisions: which tier each table lands in, which pricing tier the workspace uses, how long data is kept, and what gets filtered before it is stored.
Prices change and vary by region, so this guide leaves them out. Check the Microsoft Sentinel pricing page for current rates.
How is Microsoft Sentinel billed?
Sentinel charges depend on the tier data lands in. The analytics tier is billed pay-as-you-go or through a commitment tier. The data lake tier has its own meters for ingestion, data processing, storage, queries and notebook compute. Other services, such as Logic Apps, add their own charges.
Workspaces older than July 2023 may still use classic pricing, which bills Log Analytics separately. Learn suggests moving them to simplified pricing.
What is the difference between Analytics, Basic and Auxiliary logs?
Log Analytics offers three table plans: Analytics, Basic and Auxiliary, which Azure Monitor now labels Auxiliary / Lake. In the Defender portal, Sentinel manages two tiers per table: analytics and data lake.
- Analytics: for high-value data used in real-time detection. Queries are included in the price, and analytics rules, hunting, workbooks and playbooks all work.
- Basic: reduced ingestion cost for data used in troubleshooting and incident response. Queries are charged separately, and alerting is limited to simple log alerts. You manage Basic tables from the Log Analytics workspace, not the Defender portal.
- Data lake (Auxiliary / Lake): minimal ingestion cost for high-volume, low-touch data. Queries are slower and charged separately, and analytics rules, hunting queries, workbooks and playbooks are limited. You reach the data through KQL jobs, notebooks, search jobs and summary rules.
Moving a table changes what works
Move a table from the analytics tier to the data lake tier and its alerting, advanced hunting, analytics rules and custom detection rules stop working. Some XDR and Sentinel solution tables cannot change tier at all.
Should a customer be on a commitment tier or pay-as-you-go?
The analytics tier can be paid for in two ways. Pay-as-you-go is the default and bills the volume actually ingested. Commitment tiers start at 100 GB per day and bill usage above the commitment at the same discounted effective rate as the tier.
You can raise a commitment tier at any time, but you can lower it only every 31 days. Size it from a full month of billable analytics volume, not a busy week.
How long should you keep data, and where?
Sentinel retains data ingested into the workspace at no charge for the first 90 days. Analytics retention can go up to two years at a prorated long-term retention charge. Total retention, held in the data lake at lower cost, can go up to 12 years. What used to be called Archive is now long-term retention.
If you shorten total retention, Microsoft waits 30 days before removing data, so you can revert a mistake. Shorter analytics retention takes effect immediately, but older data stays in the data lake while total retention covers it.
Defender XDR hunting data is kept for 30 days, included in the XDR license. Extending XDR tables to up to 90 days in the analytics tier adds Sentinel ingestion charges, with free storage. Sending them to the data lake only is billed for lake ingestion, storage and processing.
How do you filter noisy tables before you pay for them?
Use ingestion-time transformations: KQL in a data collection rule (DCR) that runs on incoming data before storage, dropping rows or columns you never use. Azure Monitor Agent connectors, such as Windows Security Events, Syslog and CEF, use DCRs tied to the agent. Service-to-service connectors such as Office 365 and Entra ID use the workspace transformation DCR, where the table supports it.
In a Sentinel-enabled workspace, transformations into Analytics tables carry no Azure Monitor filtering charge. Basic tables do incur it when a transformation drops more than half of the incoming data.
For workspaces onboarded to the Defender portal, you can also create filter and split rules from Microsoft Sentinel, Configuration, Tables, without writing a DCR. A filter rule discards matching data from both tiers. A split rule keeps matching data in the analytics tier, mirrored to the lake, and sends everything else to the data lake only. Split rules need the workspace onboarded to the data lake and the table in the analytics tier.
A worked example: a customer's firewall team points its logs at Sentinel, and CommonSecurityLog becomes the largest table in the workspace. Most rows are routine allow events. You add a split rule that keeps deny and higher-severity events in the analytics tier for detections and sends allow events to the data lake for investigations and audits. Check any existing DCR on that table first: Learn warns that a DCR and a filter rule can conflict so that nothing is ingested.
Which data sources are free in Microsoft Sentinel?
Learn lists these as free: Azure Activity logs, Sentinel health data, Office 365 audit logs (SharePoint, Exchange admin activity and Teams), Defender XDR alerts and incidents, and security alerts from the Defender products and Entra ID Protection.
Alerts are free, raw logs are not
Raw logs for some Defender XDR, Defender product, Entra ID and Azure Information Protection data types are paid. When a connector offers both free and paid data types, enable only the paid ones you use.
How do you see where each customer's spend comes from?
- Usage queries: query the Usage table for billable volume over the last 31 days, summarized by DataType or Solution. The largest tables are your first candidates for filtering or a tier change.
- Workspace Usage Report workbook: shows free and billable data and volume per table.
- Cost Management: filter cost analysis to the Sentinel, Log Analytics and Azure Monitor services, and set budgets with alerts.
- Data lake usage: Microsoft Sentinel, Cost management in the Defender portal (preview) shows usage by meter, alerts on thresholds and can block further data lake queries and notebook runs once a limit is passed. Enforcement can take up to four hours.
What should a per-customer cost review cover?
Run it monthly for each customer workspace, and after any connector change.
- Pricing model: simplified or classic, and pay-as-you-go or a commitment tier that matches 31 days of analytics volume.
- Top five tables by billable volume, and whether each one feeds a detection.
- Tier per table: detection data in analytics, low-touch and compliance data in the data lake.
- Filter, split or DCR transformations on the noisiest tables, checked for conflicts.
- Free sources connected, and paid data types switched on only where they are used.
- Retention per table, matched to contract and compliance needs.
- XDR tables extended past 30 days only where you need them in Sentinel.
- Budgets and alerts, plus data lake thresholds if the lake is in use.
If you manage these workspaces with ContraForce, add its Sentinel module resources to the review. The module deploys a Logic App and automation rule in the customer's Azure subscription to stream incidents, and standard Azure charges may apply for Logic App executions. See Microsoft Sentinel Module Deployment.
Keep learning
- GDAP, Azure Lighthouse or an enterprise app? Least-privilege access to customer tenants. How GDAP, Azure Lighthouse and admin-consented Entra ID enterprise apps each give an MSSP access to customer tenants, where each stops, and how to keep that access small and time-bound.
- Getting started: connect your first customer workspace. Pre-onboard a customer in the Workspace Center, send the invite, have their admin grant the core and module consents, then confirm the workspace is live with the onboarding checklist.
- Defender XDR incidents vs alerts: how correlation works and how to triage. How Microsoft Defender XDR groups alerts into incidents, what the incident queue shows, where attack disruption, AIR and ZAP fit, and why MSSPs should triage incidents, not alerts.
Sources
- Microsoft Learn, Plan costs and understand Microsoft Sentinel pricing and billing, verified 2026-11-20
- Microsoft Learn, Manage and monitor costs for Microsoft Sentinel, verified 2026-11-20
- Microsoft Learn, Manage tables, tiers, and retention in Sentinel, verified 2026-11-20
- Microsoft Learn, Azure Monitor Logs overview: table plans, verified 2026-11-20
- Microsoft Learn, Custom data ingestion and transformation in Microsoft Sentinel, verified 2026-11-20
- Microsoft Learn, Transform data using filter and split in Microsoft Sentinel, verified 2026-11-20