Forum Discussion
Title: Expose SHA-256 or SHA-1 for Mail Attachments in Microsoft Graph
Problem
Email attachments in Graph don’t include a content hash. To identify or match attachments, developers have to download the entire file first. That wastes bandwidth and time and increases exposure. OneDrive/SharePoint already return hashes, but mail does not, so experiences are inconsistent.
Request
Add a server-provided content hash to every mail attachment. Prefer SHA-256. If that’s not feasible initially, expose SHA-1 as a minimum to align with existing Drive item hashes.
Benefits
- Faster and cheaper: avoid downloading large files just to tell if you already have them.
- Deduplication: detect repeated attachments across threads and mailboxes.
- Security operations: correlate attachments with threat intel by hash and triage suspicious emails without fetching payloads.
- eDiscovery and compliance: confidently match the same document across mail and files.
- Consistency: a predictable, uniform approach across Mail and OneDrive/SharePoint.
3 Replies
- Paul_HK_de_JongIron Contributor
Would it be useful to capture the SHA-1 hash or SHA-256 hash of attachments into SharePoint columns when an email is stored in SharePoint?
Reason for asking: we develop solutions to extract properties (Subject, Sent date, attachment names, attachments, unique words in each attachment, message-id, references, ...) from emails in SharePoint and capture the values into SharePoint columns. It is possible to extend the functionality to also capture the SHA-1 or SHA-256 for each attachment. The values can then be consumed by graph api or rest api or using search. - Jaime_from_SynergyOSIron Contributor
Thanks VasilMichev I just posted there. I leave the link below to help other users find it and upvote it if they find it relevant:
https://feedbackportal.microsoft.com/feedback/idea/1460e093-ffbe-f011-aa43-7c1e526e4a18
Best post this over at the Feedback portal: https://feedbackportal.microsoft.com/feedback/forum/ebe2edae-97d1-ec11-a7b5-0022481f3c80