#PowerPlatformTip 192: 'Send an Email with Options Reliably - Skip the Attachment'

Power Automate’s Send an email with options action (approve/reject-style response buttons baked into the email) is a convenient way to get a yes/no decision without a full Approvals flow. Attach a file to it, though, and delivery gets unreliable.

Quick answer: Don’t attach the file directly to a “Send an email with options” action. Link to it instead (a SharePoint or OneDrive URL), and send from a functional/service account rather than a personal mailbox. Both changes are simple, and together they make the notification reliably deliverable.

The problem

Attaching a file directly to Send an email with options can lead to emails that don’t arrive, or arrive with broken response buttons - inconsistently enough that it can pass a quick manual test and then fail intermittently in production. The response-button mechanism and a raw attachment don’t reliably coexist across every mail transport and security-scanning path an email might travel through.

The fix

1. Replace the attachment with a link.

🔸 If the file is already in SharePoint or OneDrive, use its sharing/view URL instead of attaching the file itself. Add the link to the email body text, right next to the decision buttons.

🔸 If the file doesn’t have a home yet, upload it to a document library first (as part of the same flow, before the email step), then link to that location.

2. Send from a functional account, not a personal mailbox.

🔸 Use a dedicated service/functional mailbox (e.g. notifications@yourcompany.com) as the connection for the email action, instead of whoever happens to own the flow.

🔸 This is good practice independent of the attachment issue: an automated notification tied to one employee’s personal account breaks when that person is on leave, changes role, or leaves - a functional account keeps working regardless, and reads more clearly as “this is a system message” to recipients.

Result

The notification arrives reliably, with working response buttons, and doesn’t depend on any one person’s mailbox staying active.

🛠️ FAQ

Why does Send an email with options fail to deliver with an attachment?

The action’s response-button mechanism and a directly attached file can interact badly with some mail transport/security scanning paths, leading to emails that silently never arrive or arrive without the options working. It’s inconsistent enough that it’s easy to miss in testing but shows up in production.

What should I send instead of an attachment?

A link to the document (in SharePoint, OneDrive, or wherever it’s stored) rather than the raw file bytes. The recipient clicks through to view or download it, and the response-options email itself stays lightweight and reliable.

Why use a functional account instead of a personal mailbox to send these emails?

A personal mailbox ties the automation to one person’s account, license, and employment status. A functional/service account keeps the flow working when that person is on leave, changes role, or leaves the company, and makes it clear to recipients the message is from a system, not an individual.

🔗 Related Tips

🔸 #PowerPlatformTip 144: ‘Infinite Approvals’ - another approval-flow reliability pattern, this time working around the 30-day timeout.

🔸 #PowerPlatformTip 114: ‘Send Approvals to External Recipients’ - extending response-based emails beyond your own tenant.