
The link to my HTTP Server Flow is: to the ID of the image you want to serve, your private SharePoint Image will be accessible to the public. The picID in the URL refers to the ID of the image in the SharePoint document library: This flow responds to a HTTP request with a reference to the Image in the URL. Its quite easily achieved by creating a flow which will serve image content via HTTP. But if you really want to use SharePoint as your source, it can be done.

Uploading the image to a web server or CDN is best. The most compatible way of embedding images in an email is to a publicly available image on the internet. So be mindful of the size of the image that you are sending. For example, gmail does not show any base64 encoded images.Īnother disadvantage of using this method is that the if the image is large, the email will large also. This method works really well, however some mail clients do not support base64 encoded images within the email body.

Then injected into the email as base64, with these expressions: outputs('Get_file_content_using_path')? The file content is retrieved with the “Get file content using path” step. So there is no need for the receiver to retrieve the image from SharePoint. This method is much more reliable as the actual content from the image is sent within the email. Embed the image content directly into the email with Base64 So unless all of your clients are using Outlook on the Web, I do not recommend this method. This works well in the Outlook Web client, but not in other clients as the file is not reachable. On a client that is signed in to Office 365, you can specify the URL of the image in SharePoint and it should show in the email client:

Attach pictures to gif full#
The full link to the file is: Provide a simple link to the file in your email
