Human Tasks
Human Tasks send emails to the person a task is assigned to: the task request, a reminder if the task is still waiting, and the one-time verification code the person uses to open the task. Tenant Admins choose who these emails come from under Tenant Admin > Human Tasks.
Recipients such as vendors or approvers outside your organization are more likely to trust a request that comes from an address they recognize. Sending from a mailbox in your own Microsoft 365 also means the emails are authenticated by your own domain.
Choose the Email Sender
- Studio default sends from Studio's own notification address, shown under the option. No setup is needed.
- Microsoft Exchange App sends from a mailbox in your Microsoft 365 through one of the tenant's Microsoft Exchange Apps.
To send from your own mailbox:
- Create a Microsoft Exchange App under Tenant Admin > Apps if the tenant does not have one, and configure its credentials. See Set Up Exchange for the permission the App needs.
- Open Tenant Admin > Human Tasks and select Microsoft Exchange App.
- Choose the App, and enter the Sender mailbox. Leave the mailbox empty to use the App's own mailbox.
- Select Send test email. Studio sends a test email from that mailbox to your own address and shows either a confirmation or the error Microsoft returned. Nothing is saved yet.
- Select Save (Ctrl+S also saves).
The setting applies to every Human Task email in the tenant: requests, reminders and verification codes. Other Studio emails, such as notifications and low-credit alerts, always come from Studio's own address.
Set Up Exchange
The Microsoft Exchange App sends with the Microsoft Graph Mail.Send application permission.
On its own, that permission lets the App send as any mailbox in your organization, so limit it
to the sender mailbox:
- In Microsoft Entra ID, note the App registration's client (application) ID and its service principal's object ID.
- In Exchange Online, give the service principal the Application Mail.Send role, scoped to the sender mailbox, with Role Based Access Control (RBAC) for Applications. Application Access Policies are the older way to do the same and are being replaced.
- Wait for the change to take effect. Exchange can take from 30 minutes to 2 hours to apply new App permissions.
- Use Send test email to confirm that Studio can send from the mailbox.
Ask your Microsoft 365 administrator to make these changes; they need Exchange administrator rights.
What recipients see:
- The sender name is the display name of the mailbox in Microsoft 365.
- Replies go to the sender mailbox, so make sure someone reads it or set up an automatic reply.
- Studio does not keep a copy of the emails in the mailbox's Sent Items, because they contain task links.
Exchange Online limits how much a single mailbox can send: 30 messages a minute and 10,000 recipients a day, plus a daily limit on external recipients for your whole organization. Messages over the per-minute limit are delayed, not lost. If your Action Flows create many Human Tasks at once, keep these limits in mind.
When an Email Cannot Be Sent
Studio never falls back to its own address when your mailbox cannot be used. Instead:
- Task request: the step that creates the task fails with the error from Microsoft (for example a missing permission), and the run fails. No task is left waiting. If notifications are on, the recipients receive the usual run failure email.
- Reminder: the task keeps waiting and its original link keeps working. The notification recipients receive an email saying the reminder could not be sent.
- Verification code: the person opening the task sees a message asking them to contact whoever sent the task.
The Sender App Is Protected
While a Microsoft Exchange App sends Human Task emails, Studio refuses changes that would stop it from sending: you cannot delete it, disable it, or remove its credentials. Choose another sender first. You can still update its credentials, for example to replace an expiring client secret; Studio uses the new secret for the next email.
Changes to the sender are recorded in the Audit Log.
Related Pages
- Human Tasks — how Human Tasks pause and resume runs.
- Apps — creating a Microsoft Exchange App.
- Notifications — who is told about failures.