<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: o365 logins in Security</title>
    <link>https://community.splunk.com/t5/Security/o365-logins/m-p/388486#M13129</link>
    <description>&lt;P&gt;a quick and dirty google research found me this &lt;A href="https://developer.microsoft.com/en-us/graph/docs/concepts/changelog"&gt;https://developer.microsoft.com/en-us/graph/docs/concepts/changelog&lt;/A&gt; &lt;/P&gt;

&lt;P&gt;Maybe you find some hints in the May 2018 changes &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
    <pubDate>Tue, 15 May 2018 03:06:57 GMT</pubDate>
    <dc:creator>MuS</dc:creator>
    <dc:date>2018-05-15T03:06:57Z</dc:date>
    <item>
      <title>o365 logins</title>
      <link>https://community.splunk.com/t5/Security/o365-logins/m-p/388482#M13125</link>
      <description>&lt;P&gt;We have been using splunk to help monitor compromised email accounts by looking for logins from countries other than the ones we operate in.  I know this insn't a foolproof method but it gives us a good start.  Last friday our queries stopped working altogether.  I suspect that microsoft changed something.  Has anyone else run into this and know a fix?&lt;/P&gt;

&lt;P&gt;index=INDEXNAME earliest=-24h sourcetype="ms:o365:management" Workload=AzureActiveDirectory Operation=UserLoggedIn | fields _time, user, src_ip | iplocation src_ip | addinfo |  where _time&amp;gt;relative_time(info_max_time, "-24h") |  where Country!="redacted" AND Country!="redacted" AND Country!="redacted" | stats latest(_time) values(user) count by Country | rename latest(&lt;EM&gt;) as * | rename values(&lt;/EM&gt;) as * | sort - _time | fieldformat _time=strftime(_time, "%Y-%m-%d %H:%M")&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 19:27:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/o365-logins/m-p/388482#M13125</guid>
      <dc:creator>pacificcreek</dc:creator>
      <dc:date>2020-09-29T19:27:30Z</dc:date>
    </item>
    <item>
      <title>Re: o365 logins</title>
      <link>https://community.splunk.com/t5/Security/o365-logins/m-p/388483#M13126</link>
      <description>&lt;P&gt;although i kinda get what your search is doing, i am not sure what you are asking here exactly.&lt;BR /&gt;
i do however remember couple times that MS changed items in Azure, or had a short outage (or anticipated one) there was a message from your company ms admin, there is a specific account name for them and message of what they are doing and when. was able to capture it and set alert on it.&lt;BR /&gt;
maybe this is what you are after?&lt;/P&gt;</description>
      <pubDate>Fri, 11 May 2018 00:41:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/o365-logins/m-p/388483#M13126</guid>
      <dc:creator>adonio</dc:creator>
      <dc:date>2018-05-11T00:41:14Z</dc:date>
    </item>
    <item>
      <title>Re: o365 logins</title>
      <link>https://community.splunk.com/t5/Security/o365-logins/m-p/388484#M13127</link>
      <description>&lt;P&gt;I think you are correct to assume that Microsoft changed something, because I also stopped receiving and user login authentication through the management API last Friday.  So did this guy:&lt;/P&gt;

&lt;P&gt;&lt;A href="https://answers.splunk.com/answers/656188/only-pulling-user-change-logs-and-not-login-attemp.html"&gt;https://answers.splunk.com/answers/656188/only-pulling-user-change-logs-and-not-login-attemp.html&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;If you find an answer to the problem please let me know.  It's not your query, its the fact you no longer are receiving that data.  I'm going to call support tomorrow and see if I can get some assistance, I encourage you to do the same as it will let them know there is an issue.&lt;/P&gt;</description>
      <pubDate>Fri, 11 May 2018 01:47:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/o365-logins/m-p/388484#M13127</guid>
      <dc:creator>centrafraserk</dc:creator>
      <dc:date>2018-05-11T01:47:55Z</dc:date>
    </item>
    <item>
      <title>Re: o365 logins</title>
      <link>https://community.splunk.com/t5/Security/o365-logins/m-p/388485#M13128</link>
      <description>&lt;P&gt;Yep, same here, we stopped getting the results on the 5th May.&lt;/P&gt;</description>
      <pubDate>Tue, 15 May 2018 02:22:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/o365-logins/m-p/388485#M13128</guid>
      <dc:creator>markhill1</dc:creator>
      <dc:date>2018-05-15T02:22:03Z</dc:date>
    </item>
    <item>
      <title>Re: o365 logins</title>
      <link>https://community.splunk.com/t5/Security/o365-logins/m-p/388486#M13129</link>
      <description>&lt;P&gt;a quick and dirty google research found me this &lt;A href="https://developer.microsoft.com/en-us/graph/docs/concepts/changelog"&gt;https://developer.microsoft.com/en-us/graph/docs/concepts/changelog&lt;/A&gt; &lt;/P&gt;

&lt;P&gt;Maybe you find some hints in the May 2018 changes &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
      <pubDate>Tue, 15 May 2018 03:06:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/o365-logins/m-p/388486#M13129</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2018-05-15T03:06:57Z</dc:date>
    </item>
    <item>
      <title>Re: o365 logins</title>
      <link>https://community.splunk.com/t5/Security/o365-logins/m-p/388487#M13130</link>
      <description>&lt;P&gt;I had the same issue:&lt;/P&gt;

&lt;P&gt;This is an issue seen across the board, not just for Splunk ingestion, but also for Cloud Access Security Brokers such as Skyhigh Networks.&lt;/P&gt;

&lt;P&gt;If you want to solve your issue, place a detailed level B support ticket with Microsoft through the Azure support portal (portal.azure.com). &lt;/P&gt;

&lt;P&gt;You will likely see logs come back within 24 hours. &lt;/P&gt;</description>
      <pubDate>Fri, 18 May 2018 13:42:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/o365-logins/m-p/388487#M13130</guid>
      <dc:creator>neades</dc:creator>
      <dc:date>2018-05-18T13:42:15Z</dc:date>
    </item>
    <item>
      <title>Re: o365 logins</title>
      <link>https://community.splunk.com/t5/Security/o365-logins/m-p/388488#M13131</link>
      <description>&lt;P&gt;The data came back on its own today.  We never did open a case with Microsoft but a sister company did.  We are now getting the alerts but it just started today.  Other individuals we knew to be traveling and logging in 5/17 were not logged.&lt;/P&gt;</description>
      <pubDate>Fri, 18 May 2018 17:09:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/o365-logins/m-p/388488#M13131</guid>
      <dc:creator>pacificcreek</dc:creator>
      <dc:date>2018-05-18T17:09:33Z</dc:date>
    </item>
  </channel>
</rss>

