You are correct that Outlook through Office 365 is not supported at this time. There are ways to work around this limitation.
First of all, instead of using Outlook you can still capture emails using POP3.
If that’s not an option for you, then it’s possible to configure Outlook to drop files in folders when certain emailing conditions are met. You’d then configure your processes to have “Folder Capture” inputs instead of “Email Input” inputs. We have an internal guide prepared on this, if you’re interested.
The plugin that produces email output through Connect is called the “Create Email Content” plugin. The “Send Email” plugin is a legacy plugin that is included in Connect’s Workflow because Connect’s Workflow it is designed to be backwards-compatible when upgrading from Suite to Connect.
The Create Email Content plugin sends emails over SMTP, and it supports TLS encryption. If what you’re looking for out of sending through Outlook is to verify sent items, what you could do instead is have the sender also be a bcc recipient. So instead of checking the sent items, those emails would appear in the inbox. The bcc recipient of course doesn’t have to be the sender and you can easily set up rules in Outlook to filter those emails into a specific folder, instead of cluttering the main inbox.
The Send Email plugin supports SMTP emailing, but does not support TLS encryption.
If you want to send an email without going through the Connect plugins, and your email server requires TLS encryption, then your last option would be to send the email through a script using the “Run Script” task. We have script examples that we could provide, if you’re interested.