MFA/modern auth being depricated by MS, any replacement?

We do have an open feature request for it, but it's unfortunately still in our backlog as other topics have a higher priority. We'll update this post once it's implemented.

Hello,

This looks urgent for me. Microsoft is currently (since 11 january 2021 i think) disabling legacy auth and a lot of people are using free and pro version of PRTG to monitor backup via emails in MS365 mailbox. We'll need an alternative for either checking emails via modern auth + IMAP, or using exchange protocol or ... I don't know.

Thank you

Hi there,

we are currently working on this case and also test a workaround for this change. However, I cannot say when this will be released at the moment.

any update on this, since we are also looking now to get this working again. MS is already disabling the authentication, so we had to create ticket with MS to allow it again...

Hi there,

we are currently working on the issue. We estimate to publish the fix in 2-3 releases. I would recommend to check our release notes after each release: https://www.paessler.com/prtg/history/stable

Hi all, we are currently facing also issues with IMAP on outlook.office365.com

We suddenly get the error:

Failed to establish secure connection [Step 0] Socket Error # 10054 Connection reset by peer. [Step 1] Socket Error # 10054 Connection reset by peer. [Step 2] Socket Error # 10054 Connection reset by peer. [Step 3] Socket Error # 10054 Connection reset by peer. [Step 4] Error connecting with SSL. EOF was observed that violates the protocol [Step 5] Error connecting with SSL. EOF was observed that violates the protocol [Unsecure] Read timed out.

Is it the same issue? Any fixes or workarounds? Thank you! Michael

Hi there,

This error occurs not due to Microsoft deprecated basic authentication since this is planned until 1st October 2022. Please check whether a firewall blocks the connection and whether you can ping the target device from the corresponding Probe.

We're not going to wait until October 2022 to find another solution now are we? :D

The exchange portion will be deprecated before that date.

Hi there,

We are currently working on an alternative. Therefore we ware quite confident that this will released before October 2022.

In addition, do you correspond to the following:

"Beginning early 2022, we will selectively pick tenants and disable Basic Auth for all affected protocols except SMTP AUTH for a period of 12-48 hours. After this time, Basic Auth for these protocols will be re-enabled, if the tenant admin has not already re-enabled them using our self-service tools."

If so please note that this is only a temporary action from Microsoft.

Any Updates? Time is ticking down ....

I'm still confident that we will release the change until October, it's still 5 months to go

Most company already switched to modern authentication. If someone is waiting until October to do so they will have a bad surprise.

Thank you for the feedback, I will forward it accordingly.

Best Regards, Moritz Heller

Any updates? We have been already hitten by a temporary shutdown of basic auth for some hours... (Microsoft announced that earlier that they turn off the feature randomly for some customers before October)

It's really urgent to get that authentication. Please do not wait until October! We rely on that feature!

Hi there, I have the update that we are currently working on this. We have a estimated release version of 22.x.79. However, please note that this can change anytime.

So roughly end of July if we are on 22.x.76 now.

At the moment, we plan with the version around September

We've got the same problem, using MFA invalidate every IMAP sensors. We'll wait september's release of PRTG then.

It's now September - So any update on this? we had basic authentication turned off and lost all notifications for our PRTG sensors! checked the release notes and still no mention of a fix.

We have already released a new Sensor in BETA status. It's the Microsoft 365 Mailbox (BETA) Sensor.

Thanks. When trying to add the new BETA sensor, I click to add the new sensor button, and a new browser window with PRTG error appears. With following url below. https://[redacted.example.com]/error.htm?errormsg=The%20request%20cannot%20be%20processed%20because%20the%20object%20ID%20is%20missing.&errorurl=%2Faddsensor.htm%3Fclient_id%3D15a5bca5-04a3-4dc9-8abf-985f1109544c%26scope%3Doffline_access%20user.read%20mail.read%26response_type%3Dcode%26%26response_mode%3Dquery%26redirect_uri%3Dhttp%3A%2F%2F[redacted.example.com]%3A8080%2Fms365.htm%26state%3D4654_%7B15C742F1-1997-4AFE-B2A5-7E21879054D4%7D-991229000000_paessler.microsoft365.mailbox_sensor.26%26prompt%3Dselect_account%26

Hi there,

I think it would be the best to open a support ticket to work on this issue. Please login to our support portal or write an email to "Support@paessler.com"

But the new "Microsoft 365 Mailbox (BETA) Sensor" does not support monitoring the mails. Like the IMAP Sensor. what is the best way to monitor email content (for exampe a Backup mail)? Or when is a "modern authenification" IMAP Sensor available?

There will be no "modern authentication" IMAP Sensor at the moment and is also not planned. Which certain feature is missing? If you want to monitor a backup, you can filter for the body or subject of the email. Then you have a backup monitoring again.

our usecase for backup monitoring is: check inbox for recent emails having specific from/subject/body. If no such emails found, trigger alert. This was a huge help.

We use a Veeam for backup (solution #1 according to Gartner) and after every backup, the "success" email is automatically sent. With PRTG we monitored not only the successfulnes but also the very operational status of backup solution (any problem or outage meant no email is sent = and PRTG wakes us up). This important process is unreliable to do with humans now.

The backup infrastructure also cannot be monitored by PRTG directly as it would break security best practices (i.e. these of completely isolating backup infra from production infra). PRTG cannot connect to backups, but backups can sent emails and PRTG can (at least was able to) check their content.

Hi there,

Please let me know which certain feature you are missing in the new Microsoft Mailbox Sensor?

new Microsoft Mailbox Sensor might solve our usecase, will check it. Thanks for the tip