Forum Discussion
Azure Activity Log missing legacy auth failed attempts or account lockouts for AAD Powershell
- Update 12/11/2017 - Microsoft Premier Support said this is working "by design" and will either provide a public facing article that states this and/or will open a "Design Change Request" to log these legacy authentication failure events.
interesting so far in two separate tenants we are not seeing v1 module legacy authentication attempts.
To confirm we are looking in the same place as you, are you going into Azure Active Directory > Activity > SIgn-Ins ?
When filtering on "Office 365" as the application and sign-in status Failure for the past 24 hours we don't see any events. And when we broaden the filter for all failures, we don't see any of the legacy auth failures. Again, we are seeing this auditing gap exist in two separate Azure AD tenants. I'm about to check a 3rd.
The UI is pretty crappy if you ask me, simply download the report and work with it. Then again, I might simply be wrong and the "Office 365" app logins I'm seeing might correspond to something else.
The downloaded report is also missing legacy authentication from Azure AD Powershell.
After simulating brute force against three separate AAD tenants using legacy powershell and waiting more than 12 hours after each attempt, I have yet to find a case where it is a logged event. I'll open a ticket with MSFT Support to see if they are aware of this.
Looking at the tests I did, it definitely does not log every single failed attempt. I did get one additional entry from today, which seems to correspond to the dozen or so attempts I made. And I'm starting to think that you are correct here - I was expecting at least two different types of "applications" reported as I tried both the MSOnline module and (legacy auth) ExO PowerShell, but only one of them is visible - which I guess is the ExO failure, not the MSOnline one. Let us know if you get an official answer please.
- Update 12/11/2017 - Microsoft Premier Support said this is working "by design" and will either provide a public facing article that states this and/or will open a "Design Change Request" to log these legacy authentication failure events.