I have the same question, and think this could pose a real issue if there is no way to use OAuth 2.0 with the exchange server in FME Server. Does anyone have any advice on how to use OAuth 2 rather than basic IMAP Authentication?

https://docs.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/deprecation-of-basic-authentication-exchange-online

From what I understand, this is being turned off October 1st 2022, so active connections will cease at that date. I imagine this would impact a large amount of FME Server users making use of their exchange server and the IMAP trigger in FME Server Automations. (Or any notification services)

Cheers

Hi @sossie07​ & @kieran.odonnell​ ,

Our team is currently investigating the impact of the deprecation for basic authentication in both IMAP and SMTP protocols. Unfortunately, at this time we do not support the alternative authentication method.

Updates will be shared on this post when available.

Thanks,

Kezia

Just saw this: there is a patch in FME Server 2022.1 that addresses this. Might require some adjustment on the Azure/O365 end but it works.

Thanks for sharing this! More information on the patch can be found in this article. If anyone runs into the error below with Azure after applying the patch, please see this resource which provides some potential resolutions. 

The request body must contain the following parameter: 'client_secret' or 'client_assertion'

​@keziaatsafe we are getting the client_secret/client_assertion error message, but we haven’t been able to get it to work even when setting “Allow public client flows” to yes.  Is it possible that the “Web” vs “Mobile and Desktop Applications” for the redirect URI is a required fix?

https://stackoverflow.com/questions/45609432/how-do-i-resolve-the-error-aadsts7000218-the-request-body-must-contain-the-foll

Hello ,

Did you create a secret for the Azure app that is connecting to FME Flow? Adding a certificate, client secret or redirect URI during app registration is not required for setup with FME Flow Automations shttps://support.safe.com/hc/en-us/articles/25407404506253-How-to-use-Microsoft-Modern-Authentication-with-FME ]. It is required for Email transformer with Form though.
Please ensure that you create a separate Azure app for both Form and Flow . 
Please feel free to create a case in case the issue persists.