Forum Discussion
Solved
Azure Activity Log missing legacy auth failed attempts or account lockouts for AAD Powershell
In my testing, I am not seeing any logging of failed attempts or account lockouts in the Azure Active Directory Activity Sign-In Logs when the legacy module of Azure Active Directory is used.
Modern Authentication clients are logged for failed sign-ins and account lockouts, but not when legacy authentication is used in the Azure Active Directory powershell module.
The risk / concern here is that attackers can go undetected in their brute force attempts.
I realize the risk is small, since accounts are locked out after 10 invalid attempts, however, it would still be nice to have visibility.
According to the documentation, it can take up to 8 hours for legacy apps to show up in the logs, however, I have waited 12 hours and I still see no sign of my simulated brute force activity.
"For some sign-ins activity data coming from legacy office applications, it can take to 8 hours for the reporting data to show up"
The note above says "legacy office applications" so I assume that Azure AD Powershell would fit into that category rather than not logging any activity at all from it.
- 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.
I seem to have some in the logs, they are marked as "Office 365" for the application name though.
- Thanks. can you confirm your events are from Azure Active Directory Powershell Module version 1.0 using Legacy Authentication? How long is the delay before you see them in the logs? To be clear we are not referring to Exchange legacy authentication... it is speciic to Azure AD PowerShell using legacy auth.
So the V2 module should be "Azure Active Directory PowerShell", and it has the "MFA Required" set to true. Apart from that, I have been using the old MSOnline module, which gets reflected as just "Office 365" and as I'm using the -credentials parameter with it, it's definitely legacy auth ("MFA requires" says false).
Not sure about the delay, but I do have some logins from today, so should be relatively fast.
