Note that the October 13 2020 deadline has been pushed back by Microsoft due to the COVID-19 situation:
"In response to the unprecedented situation we are in and knowing that priorities have changed for many of our customers we have decided to postpone retiring Basic Authentication in Exchange Online (MC204828) for those tenants still actively using it until the second half of 2021. We will provide a more precise date when we have a better understanding of the impact of the situation.
We will continue to disable Basic Authentication for newly created tenants by default and begin to disable Basic Authentication in tenants that have no recorded usage starting October 2020. And of course you can start blocking legacy authentication today, you don’t need us to do anything if you want to get started (and you should).
We will also continue to complete the roll-out of OAuth support for POP, IMAP, SMTP AUTH and Remote PowerShell and continue to improve our reporting capabilities. We will publish more details on these as we make progress."
... View more
I've had the same issue and ended up using a CloudWatch Event trigger -> Lambda -> HEC for config:notification events instead. This assumes you have HEC available and working. I'm not an AWS expert but this solution seem to work well.
Lambda blueprint used is splunk-logging and make sure you use only the Log event with user-specified request parameters section of the code (so comment out the 4 other options above that section) where you can specify sourcetype as aws:config:notification
The CloudWatch event pattern is:
"Config Configuration Item Change"
For CloudWatch event target, use the Lambda and under configure input choose "part of the matched event" and enter "$.detail"
In Config settings use the usual S3->SNS->SQS for Config history and Config snapshot logging but disable the Stream configuration changes and notifications to an Amazon SNS topic option or you'll get duplicate data.
... View more