Power Platform Community Forum Thread Details

Hi,

I have identified a limitation in the Send an email (V2) connector in Power Automate.

When sending an email with attachments that include IsInline: true and a valid ContentId, the connector does not respect these properties. All attachments are treated as regular file attachments regardless of the IsInline flag, causing inline images (such as email signature logos) to appear as separate downloadable attachments instead of rendering inline in the email body via cid: references.

Expected behavior:

Attachments with IsInline: true and a matching ContentId should render inline in the HTML body, consistent with how the Microsoft Graph API handles inline attachments.

Actual behavior:

All attachments are rendered as separate file attachments, ignoring IsInline and ContentId.

Workaround used:

Filtering out inline attachments entirely using a Filter array action, which resolves the duplicate attachment issue but removes inline images from the email thread history.

This limitation makes it difficult to forward or reply to emails with inline images while preserving their correct placement in the HTML body.

Categories:

Building flows

I do not believe IsInline and ContentId are actual configurable fields in the standard Send an email (V2) action. In Power Automate, the attachment object for that action appears to support the standard Name and ContentBytes structure, not the full Microsoft Graph fileAttachment schema. If you manually added IsInline and ContentId to the attachment array, that would explain why the connector ignored them and treated the files as normal attachments. If you want inline CID-based images, you may need to use Microsoft Graph instead of the Outlook connector.

Can you show how you configured the send e-mail action. It sounds like you're inserting extra JSON code into the attachments array and expecting it to work. You'll probably need to use an Http request with a Graph API call to do what you want since that offers more features than the pre-configured actions expose.

Is this the action you are using? If so, you can see that the action supports the filename and content bytes. It is likely ignoring anything else you may be adding if you switch the attachment to array view,