2020.2

Microsoft 365 Email Output
The Microsoft 365 Email Output task can send emails on behalf of any user in an
organization's Microsoft 365 accounts, without having to specify that user's credentials. This
way privacy is maintained while allowing a process to send email messages and attachments
on behalf of any user. The task communicates through HTTPS. However, the real protection
scheme (like certificates) is configured in Azure Active Directory by the IT administrators.
Note that this task doesn't merge data records with a PReS Connect template, like the "Create
Email Content" on page600 task does.
This task uses the Microsoft Graph API.
For this task to function correctly, Workflow needs to be granted application permissions for
Microsoft Graph in the organization’s Azure instance.
It needs read access to the Users category (User.Read.All) so that the task can identify the
users in the organization.
In addition, to send emails on any user’s behalf, the Mail.Send permission is required.
For more information on setting application permissions for Microsoft Graph, see
https://docs.microsoft.com/en-us/graph/auth-v2-service.
Input
Any data file.
Processing
The task uses the Microsoft Graph API to access accounts in the organization (subject to that
organization's IT policies).
While an email is always sent by this task (or at least attempted to be sent), the contents of the
email and presence of attachments depends on the selected options.
Once the contents of the email and attachments are determined, the email (including any
attachments) is sent directly to the selected mail server.
Note that the Windows instance's language setting may affect the output of this plugin. For
example, a Workflow setup configured on a Windows-1252 machine will not be able to write
Japanese strings. It won't affect the contents of attachments, since they are loaded as binary
streams.
Page 656