I see it's possible to get the full, not truncated audit log string for 'updated user' events in the unified audit log via the azure portal, as detailed in a comment here
That thread is now inexplicably locked, and I've found that exporting the CSV from the Azure Portal provides a mal-formatted file; there are commas within some fields, so parsing it as a comma-separated CSV is impossible, and it would take some crazy regex to make it readable. Even after you've done that you'd have to write some customer parser for the actual data, since it's not in any standard format.
I'm guessing there are some 3rd party solutions out there for £££?
I just posted a more specific feature request on this given recent developments. See also: https://office365.uservoice.com/forums/289138-office-365-security-compliance/suggestions/32878246-add-ability-to-deny-ews-and-mapi-clients-using-bas
Client Access Rules feature promised to resolve this, but now it's released it seems that it does not, as it is impossible to block EWS and MAPI (OutlookAnywhere) clients from using Basic Authentication.
390 votes12 comments · Office 365 Security & Compliance » Advanced Security Management · Flag idea as inappropriate… · Admin →
Thanks for taking the time to provide this feedback. We’ve updated the TechNet documentation (https://technet.microsoft.com/library/mt842508(v=exchg.150).aspx) to clear up confusion around which authentication type and protocol combinations are supported in CARs. Expanding support for more combinations could prevent bad actors with valid credentials from accessing mailbox content, but it wouldn’t help with scenarios like password spray attacks or malicious lockout attempts because CARs are evaluated post-authentication. There’s work underway on a solution that covers a broader array of basic authentication scenarios – we’ll share more details as soon as possible. In the interim, this blogpost (https://cloudblogs.microsoft.com/enterprisemobility/2018/03/05/azure-ad-and-adfs-best-practices-defending-against-password-spray-attacks/) outlines the recommended approach for forcing multi-factor authentication when using AAD and ADFS.Sam Buccieri-Gillett shared this idea ·