I have the same question.

Best Regards,

Rusiru

Hi, on the IFS Support Portal, IFS informed that this functionality will be available in IFS 10 UPD29

regards

Daniel

Hi ​@Daniel 

It's UPD 19 right?

Thanks for the update.

is there any guide?

Best Regards,

Rusiru

No, Oauth 2 related changes will be included in UPD29. UPD29 for IFS10 is to be released in late August 2025.

Hi ​@Daniel 

According to this KB IFS Product - OAuth 2.0 Support for POP and IMAP in For IFS Mail Connector in IFS Application its included in UPD 19

Best Regards,

Rusiru

I checked this topic. The changes regarding OAUTH are already in version 19 but on the READER side, SENDER there are no such changes (I checked also on version UPD24)). That's why I asked IFS directly and got this answer.

I reported this to IFS a few months ago and got R&D to work and implement a patch.

That patch is indeed going to be rolled out in UPD29, although a single issue patch might be possible based on your set up.

It was possible for us and we’re on UPD23.

This is extremely important for any of you guys that use MAIL_SENDER capabilities where you connect directly through an O365 corporate account using client submission, as this is going to go bye bye with Microsoft in September.

What that means is that if you’re still in Apps 10 and you don’t update your MAIL_SENDER, and it still attempts to connect to O365 to send emails, your email sending will abruptly stop as soon as Microsoft kills the service.

I highly recommend anyone making critical use of email sending (such as sending POs, Invoices, etc.) with their MAIL_SENDER ensure that their Apps 10 instance is patched to allow oAuth Authentication for their senders, and fairly quickly at that as you only got 3 months until Microsoft disables it.

Does anyone know the patch / bug /fix ID. It may help is when requesting as a single fix...

Microsoft pushed disabling Basic auth for Client Submission (SMTP AUTH) out from Sept. 2025 to April 2026

https://techcommunity.microsoft.com/blog/exchange/exchange-online-to-retire-basic-auth-for-client-submission-smtp-auth/4114750

Still anyone relying on it should get updated several months before then so that it can be tested in your IFS Test environment before being set up in your Production environment.  

Setting up 0Auth is a little tricky and cumbersome to set up in Entra ID(Azure), so also give yourself a few months to figure that all out, especially since MS is known to change processes and locations of settings without updating their documentation, which on a good day makes my head hurt trying to follow 

Do you have any extra information on that ?

My IT department is currently struggling with this. They have registered the Application, Generated the Secret, set the APIs and (supposedly) done the Powershell equivalent to generate the Service Principal and attach it to the mailbox I use to send mail, but It still doesn’t work.

I know the App is properly registered and the App ID and Client secret value is correct because if I try to change either one of these in the Mail Sender config, I get a specific error message when trying to send mail.

If I do set the proper App ID and client secret value though I keep getting this error:

Again, it says “Client not Authenticated to send mail” but I know for a fact the App ID and Client Secret is valid because if I change them I get relevant errors (like App can’t be found or Can’t retrieve token if the client secret value is incorrect)

We have ANOTHER mail sender that was set up in Azure before the microsoft changes to Entra/Graph, following the steps highlighted in the guide (Azure App, Secret, API Perms (Graph Mail.Send, and the SMTP ones),  Powershell) and that one works perfectly fine.

But we’re trying to set a NEW one now (with a different App/Email Address), and my IT can’t seem to figure out how to properly set it up.

Is there any current up to date documentation of every step that needs to be taken in a Azure/Entra/Graph to ensure Client Credentials oAuth works ?

Thank you.

I have not set 0Auth in IFS, only in other applications.  I just followed the directions from Microsoft.  Just took me a while to “decipher” them.   If you do a Google search for that error message there are list of things your IT Dept. can check.