Update: The full timeline for retirement of Basic Authentication in Exchange Online is now published in Basic Authentication Deprecation in Exchange Online – September 2022 Update.
It’s been a few ...
Updated Sep 01, 2022
Version 7.0
Blog Post
Greg Taylor - EXCHANGE Looks like the client app filter has been updated to be clearer - thanks. Could there be a 'select all' tickbox for toggling all the Legacy Auth clients?
Secondly, it looks like sign-in log changes on 10/11 March have broken the Identity Protection Legacy authentication report.
It now reports even fewer Legacy Authentications (it never picked up ActiveSync anyway). I thought there were fewer items in the report due to our working as home directive, however it looks like client apps have been re-classified and thus not picked up in the report.
The example below is from the same account. The entry on 10 March is listed in the Identity Protection Legacy authentication report, 11 March is not.
Date: 3/10/2020, 2:25:41 PM
Client app: Other clients
User agent: Fantastical/692 CFNetwork/978.0.7 Darwin/18.7.0 (x86_64)
User agent: Fantastical/692 CFNetwork/978.0.7 Darwin/18.7.0 (x86_64)
now comes up as
Date: 3/11/2020, 7:55:30 PM
Client app: Exchange Web Services
User agent: Fantastical/692 CFNetwork/978.0.7 Darwin/18.7.0 (x86_64)
Whilst we currently have 45 accounts in the last week recorded in the Identity Protection Legacy authentication report, if I reproduce the report with all Legacy Auth, the real number of accounts is 463 (plus 2,500 ActiveSync if that is also added).
As Identity Protection is a premium service, how do we get quick fix pushed through, letting admin's know the reason for the increase?
As Identity Protection is a premium service, how do we get quick fix pushed through, letting admin's know the reason for the increase?