I suggest you ...

← Microsoft Graph Feature Requests

Send message with a larger than ~3 MB file attachment

Through Graph, there is NO way to compose or quick send a message having, let's say, a 6 MB PDF brochure. I'm not asking for attachments of hundreds of MB, but the current limitation is a huge bug.
UploadSessions in the context of Messages could be a solution path to the inherent limitation of embedding base64 file content in a Json.
A

94 votes
Sign in
(thinking…)
Sign in with: Microsoft
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

lvrmsc shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

32 comments

Sign in
(thinking…)
Sign in with: Microsoft
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Praveen commented  ·   ·  Flag as inappropriate

    Its a little heavy implementation I feel using session route. As a workaround we have given access to outlook API (Exchange -> Mail.Send) permissions to our app registration. Outlook API able to send around 25MB we tested very fine. If that helps!

  • ahmed elmoden commented  ·   ·  Flag as inappropriate

    As a workaround, you can use SMTP for sending the mail, which doesn't have this restriction. That's what we do for sending mails.

  • Tomasz commented  ·   ·  Flag as inappropriate

    @Sivaprakash Saripalli any news about the issues everyone are reporting?
    I found another one - https://github.com/microsoftgraph/msgraph-sdk-dotnet/issues/603.
    Try sending an email with five 1MB attachments. The current workaround is to ZIP them, but I can't imagine getting an email from the bank of other institutions with documents in ZIP - not very professional.

  • Christophe L. commented  ·   ·  Flag as inappropriate

    Hello,

    I have the same issue than Pieter Nys. I am not able to upload attachments of 3.1MB.

    When using the old way of sending a post-request to '/v1.0/me/messages/ID/attachments', I get an http-response with statuscode 500. I guess because my total request size is around 4.1MB and the maximum is 4MB.

    When using the new way of creating an upload-session, I get an error-response with the message 'ErrorAttachmentSizeShouldNotBeLessThanMinimumSize'.

    This leaves me with no way of attaching an file with size 3.1MB.

    Thanks for looking @Sivaprakash Saripalli, @vsaripal

    Christophe L.

  • lvrmsc commented  ·   ·  Flag as inappropriate

    Thanks for this addition. It mostly works. Though three secondary issues arise.

    1. Why don't you require a "@odata.type": "#microsoft.graph.fileAttachment" as the content for /attachments/createUploadSession, instead of this "AttachmentItem" coming from nowhere? For one thing, it would allow setting the content-type.

    2. Are you aware that the HTTP servers referenced in the uploadUrl (https://outlook.office.com/api/beta/...) do not accept content-encoding chunked?

    3. Weren't the https://outlook.office.com/api somehow deprecated in favour of graph.microsoft.com? Does it make sense to host the upload sessions over there, instead of on graph.microsoft.com?

  • Pieter Nys commented  ·   ·  Flag as inappropriate

    Hey @Sivaprakash Saripalli, @vsaripal,

    Thanks for getting back to me about the configurable upper limit of message-size. I still need to test this out with my exchange administrator to test this further.

    I've ran in another issue with this. I am not able to upload attachments of 3.1MB.

    When using the old way of sending a post-request to '/v1.0/me/messages/ID/attachments', I get an http-response with statuscode 500. I guess because my total request size is around 4.1MB and the maximum is 4MB.

    When using the new way of creating an upload-session, I get an error-response with the message 'ErrorAttachmentSizeShouldNotBeLessThanMinimumSize'.

    This leaves me with no way of attaching an file with size 3.1MB.

    I uploaded a log of my requests and the attachment-file used to https://we.tl/t-w5ujFLARdR .

    Could you take a look?

  • AdminSivaprakash Saripalli (Senior Program Manager, Microsoft Graph) commented  ·   ·  Flag as inappropriate

    Hey Pieter,

    I'm so happy to have you try this out and share feedback. By default, Exchange Online mailboxes have a send/receive limit of 35MB per message. These limits are configurable by the Exchange administrator.

    Please work with your organization's Exchange administrator to change this limit to 150MB. Instructions for changing this config can be found at, https://www.mailsdaddy.com/blogs/increase-mail-attachment-size-office-365/

    Thanks,
    Sivaprakash

  • Pieter Nys commented  ·   ·  Flag as inappropriate

    As I was very excited to try out this new feature, I immediately started working on it this morning.

    I was able to upload larger files using this new method, however I was absolutely not able to attach an attachment of 150 MB.

    When trying to upload an attachment of 30+ MB or a set of attachments totalling more than 30MB, I received a response with header 400, code "ErrorMessageSizeExceeded" and message "The message exceeds the maximum supported size.".

    I'm still very pleased with the possibility of adding larger attachments, however saying the new limit is 150MB is not correct.

    @Sivaprakash Saripalli, @vsaripal, is there anything we need to change on the configuration of our mailbox/office 365 so we can send larger emails?

  • Aidrich Dean Frazier commented  ·   ·  Flag as inappropriate

    Any update here? Our organization has devoted a lot of time and effort to utilize Graph as was recommended by Microsoft only to discover this terrible limitation.

  • Jeremy commented  ·   ·  Flag as inappropriate

    If anyone is interested, if you cannot wait for this and need an alternative, i used the outlook rest api to achieve this rather than using graph
    https://docs.microsoft.com/en-us/outlook/rest/compare-graph
    You need to get a token from v1 of the azure identity service
    eg. https://login.microsoftonline.com/{{tenant_id}}/oauth2/token

    i used client credentials as im doing a daemon service. You also need to add the Exchange Mail.ReadWrite api permission rather than the graph permission. Hope this helps anyone who need this functionality urgently

← Previous 1

Microsoft Graph Feature Requests: Mail (Outlook)

Categories

Feedback and Knowledge Base

(thinking…)