Unanswered

Office 365 Outlook connector: How are you dealing with large emails with new change to limit to less than 4MB attachment size (including attachment)

(0) Share

Report

Posted on by NeilG

Question: How are you planning on dealing with attachments larger than 4MB with the Office 365 Outlook connector?

I am surprised that I have not found a bunch of posts of people screaming about the changes documented here:blog/office-365-outlook-connector-important-upcoming-changes/

Specifically the following: "There is currently a limit of 4MB on the total size of each Graph API REST request, this limits the size of the attachment to under 4MB." which is documented here: connectors/office365/#known-issues-and-limitations

To me attachment size limit of less than 24MB seems unworkable.

What is the expected behavior if a message arrives with a 25MB file? What about a message with 32MB file (33MB is max attachment size on iOS/Android Outlook client), which is the "smallest" limit per Message limits across Office 365 options

Categories:

Using flows

I have the same question (0)

All responses (3)

Answers (0)

NeilG 4 on at

Like (0)

Report

Please vote for this uservoice. We need the new API calls in Office 365 connector to support attachments larger than 3MB. (Remeber the 4MB limit is 4MB of JSON encoded.. so attachments greater than 3MB but less than 3.9MB might work or might expand to bigger and thus... not send -- and sometimes not even fail at the connector level.)

https://microsoftgraph.uservoice.com/forums/920506-microsoft-graph-feature-requests/suggestions/37353598-send-message-with-a-larger-than-3-mb-file-attachm

Was this reply helpful? Yes No
v-litu-msft on at

Like (0)

Report

Hi @NeilG,

Could you please share the run result of your Flow? There did has 4 MB attachment file size limit in the API call, how about using the Send email action instead of API call?

Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Was this reply helpful? Yes No
NeilG 4 on at

Like (0)

Report

@v-litu-msft,

This post was for asking how others are dealing with the limitation - the bug report for the problem is in the bug section of the community forums here:
Flow Bug - SendAsSharedMailbox(V2) with large attachments reports success when it should report 413 failure.

In additional I opened a formal support ticket through the admin portal and that bug is getting escalated to a priority A (When the action fails, it should report failure, not success as it currently does.).

The limitation applies to sending AND Recieving and the 4MB is 4MB JSOS base65 encoded - which mean for non- text/XML files closer to 3.1MB

-Neil

Was this reply helpful? Yes No