*Microsoft have announced that they’re retiring basic auth for SMTP early next year (starting 1st March 2026 and completing by 30th April 2026). Once this change is made, the current SMTP connection to QuickFile will stop working and we’ll be unable to send emails out via M365.
This feature request is for QF to provide support for modern auth options to allow continued use of M365 for email services with QF once this change is implemented.*
Use a 3rd party outgoing SMTP service like https://www.smtp2go.com/ to send emails. You can configure these to be coming from your existing M365 domain. Extra steps are required to verify and validate the domain to ensure reliability of outbound emails using such services.
We use this service for many others like email from scanners, website contact forms, including QuickFile
We’ve looked at this before but found the reputation of their IPs just causes deliverability issues. Plus in the eyes of a lot of customers, it’s just another service to have to sign up for/administer/pay for. Ideally it’d be great if QF supported modern auth natively in the same way other SaaS providers do, such as Atlassian.
We use Gmail atm… however, I suspect they will go the same way, so I agree it would be good if QF was on top of this one.