<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Daily Cap on Anything About IT</title><link>https://www.verboon.info/tags/daily-cap/</link><description>Recent content in Daily Cap on Anything About IT</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 20 May 2022 20:18:50 +0000</lastBuildDate><atom:link href="https://www.verboon.info/tags/daily-cap/index.xml" rel="self" type="application/rss+xml"/><item><title>How to analyze Microsoft Sentinel Daily Cap Alerts - AADNonInteractiveUserSignInLogs</title><link>https://www.verboon.info/2022/05/how-to-analyze-microsoft-sentinel-daily-cap-alerts-aadnoninteractiveusersigninlogs/</link><pubDate>Fri, 20 May 2022 20:18:50 +0000</pubDate><guid>https://www.verboon.info/2022/05/how-to-analyze-microsoft-sentinel-daily-cap-alerts-aadnoninteractiveusersigninlogs/</guid><description>&lt;p&gt;To avoid unplanned costs for Microsoft Sentinel, it is recommended to set a daily cap and create an analytics rule that triggers an alert when the daily cap is reached. Microsoft has published general guidance for monitoring costs &lt;a href="https://learn.microsoft.com/azure/sentinel/billing-monitor-costs"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;In the past months I have deployed a number of Microsoft Sentinel instances and in many cases the root cause for reaching the daily cap was related to data ingested into the AADNonInteractiveUserSignInLogs table. When analyzing the data we often found an individual user that created an unusually high amount of events. This can happen for various reasons such as:&lt;/p&gt;</description></item></channel></rss>