Announcing pricing changes to Azure Sentinel and Azure Monitor Log Analytics to help you save costs

Published Jun 02 2021 07:08 AM 6,577 Views

As a cloud-native SIEM, Azure Sentinel offers significant cost benefits. We have seen Azure Sentinel and the promise of cloud-native SIEM result in cost savings, both direct and indirect, for many of our customers. The 2020 commissioned Forrester Consulting Total Economic Impact™ of Microsoft Azure Sentinel study, for example, found that Azure Sentinel delivered a 48% reduction in costs compared to legacy SIEMs, saving on expenses like licensing, storage, and infrastructure costs.


Today, we are pleased to announce changes to the pricing of Azure Sentinel and Azure Monitor Log Analytics that will offer you additional cost savings. These changes take effect on June 2.


The changes include:


New capacity reservation naming

Capacity reservations are now called commitment tiers. You will see this change reflected in your user interface, in documentation, as well as on Azure Sentinel and Azure Monitor pricing pages and in the pricing calculator.


New, higher commitment tiers

We are introducing new commitment tiers for both Azure Sentinel and Azure Monitor Log Analytics for higher data ingestion: 1 TB/Day, 2 TB/Day, and 5 TB/Day.


Changes to how we bill for data ingestion over your commitment tiers

We are also changing the way we bill for overage. Data ingested beyond your selected commitment tier will now be billed using the effective commitment tier rate, instead of the Pay-as-you-go rate, resulting in a lower bill.

For example, for Azure Sentinel in the East US region, if you are on a 500 GB/day commitment tier, you will now be billed for overage at $0.80/GB (i.e. the effective rate for that tier) instead of the $2/GB pay-as-you-go rate.


Simplification of commitment tiers

We are simplifying commitment tiers to make them easier to manage. You can now select from eight distinct commitment tiers, per your needs, and no longer need to manage tiers due to minor changes in data ingestion patterns.


As part of this change, any workspaces with commitment tiers greater than 500 GB/day will be reset to the lowest available commitment tier – 500 GB/day, 1 TB/day, 2 TB/day, or 5 TB/day. This change should lower your costs due to the lowered cost of overage.


For example, if you were previously on a 600 GB/day commitment tier, your commitment tier would now be to 500 GB/day. Due to the change in overage billing, on days when you ingest more than 600GB, you would get billed at the 500GB effective tier rate, and on days you ingest less than 600GB, you save money because you are at a lower commitment tier – saving you costs overall.


Learn More

We’re excited to help you save costs with these changes, and look forward to continuing to innovate with Azure Sentinel and Azure Monitor Log Analytics. If you would like to learn more, please visit the Azure Sentinel pricing page or Azure Monitor Log Analytics pricing page. Thank you for being an Azure Sentinel and Azure Monitor Log Analytics user!

Occasional Contributor

Appreciate the competitive pricing.

But I never understood why MS can't stick to the names it starts off with.

Azure Monitor-LA was changed

ATP name's changed

This is now called that, that was previously called that..this statement is there so much in the docs.

I really hope Sentinel is not renamed to something cuter.


If we name a baby Jack, let's not call him John after he's 5 years old.

On a personal note, I really think 'Capacity Reservation' was a better suited term, but that's just my opinion.

However, if possible could you explain how this new name is better.

Am just interested in understanding what transpires in Teams calls when such decisions are taken.


Agreed. And if you do insist on changing the names of things make sure it is consistent across all docs and portals. I'm fed up having to remember what stuff was called and align it to the new name.

Senior Member

Hi how do we get access to Azure Sentinel TCO analysis estimator of Forrester?

Version history
Last update:
‎Jun 03 2021 01:12 PM
Updated by: