Microsoft Technology Licensing, LLC

Aaron Stolarz

George Arthur Herbert, Iii

Misbah Uraizee

Rebecca Jean Lawler

Steven Lepofsky

Christopher Walker

William Baughman

George Arthur Herbert

George Arthur Iii Herbert

Technologies are presented directed to smart attachment of cloud-based files to communications such as email. A communication service may determine and select automatically between local and cloud versions of synchronized files allowing the recipient of the message to receive a version of the file regardless of whether the sender is offline or online when the attachment was made and in a user-friendly manner to the sender through a single representation.

Smart attachment of cloud-based files to communications

Technologies are presented directed to uploading of attachments to a relevant group cloud storage at send time. A communication application and/or service may suggest to a user to upload an attachment of an outgoing communication to a group cloud storage upon generation of the communication. Suggestion of group may be based on last use, document type, content, user(s), which account the user is in, and comparable factors. The user (or sender) may also be provided with options to set permissions for the attachment based on the upload destination selection. In some examples, upload of work documents to personal cloud storage may be prevented and suitable groups may be selected for user that are part of multiple groups.

Automatic uploading of attachments to group cloud storage at send time

Rich attachments in emails (or other modes of communication) may be regenerated when an email with a rich attachment is sent to an application incapable of handling the rich attachment and then returned or forwarded to an application capable of handling the rich attachments. In some examples, the rich attachment may be along with a link (e.g., a hypertext markup language 'HTML' link) or similar construct by the application capable of handling the rich attachment. A receiving/forwarding (or replying) application that is incapable of handling the rich attachment features, may simply keep the link in the email without processing the rich features. When the email comes back or is forwarded to the application capable of handling the rich attachment, the HTML link may be recognized, the attachment and associated metadata extracted, and presented to the recipient as rich attachment (e.g., in an attachment well).

Rich attachment regeneration

Growing community of inventors

Redmond, WA, United States of America

Aaron Stolarz