Microsoft Technology Licensing, LLC

Adam Christopher Czeisler

Steven James Bailey

John David Rodrigues

Michael John Novak

Chris J Guzak

Cesare John Saretto

Tyler Kien Beam

Marcus Eduardo Markiewicz

Christian Fortini

Ranjib Singh Badh

Jack Allen Nichols

Filip Chelarescu

Jonathan Alexander Bockelman

Juan-Lee Pang

Amnon Itamar Govrin

Eyal Schwartz

Michal Krzysztof Piaseczny

Ryan M Hurst

Daniel Vincent Fiordalis

Jose J Figueroa-Morales

Marcelo Albuquerque Fernandes Mas

Benjamin M Yim

Paul M Paradise

Walter V Von Koch

Steven Abrahams

Alton Kwok

Carmen Zlateff

Tatjana Fournier

Keith Arthur Fournier, Ii

Yuval Gross

Walter Von Koch

Stephen Sisk

A computing system includes at least one processor and memory storing instructions executable by the at least one processor, wherein the instructions, when executed, cause the computing system to instruct a synchronization engine to synchronize first and second versions of a file, the first version being stored on a first storage system and the second version being stored on a second storage system, receive a backoff indicator corresponding to the file, based on the backoff indicator, instruct the synchronization engine to backoff synchronizing changes to the file, and allow the changes to the file to be synchronized by a co-authoring application, maintain a first set of collaborative metadata indicative of content of the first version of the file, and maintain a second set of collaborative metadata indicative of content of the second version of the file.

Coordinating file synchronization between a sync engine and another application that supports document collaboration

Identification of an entity performing a deletion or modification action on locally stored files and notification to mitigate risks to cloud stored files is provided. A local or remote file watcher may monitor locally stored files and detect a deletion or modification action. The file watcher may also identify an entity performing the deletion or modification action. The entity may be an application, a process, a user other than the user that is the owner of the files, or the user himself/herself. The file watcher may further determine one or more alert conditions or rules associated with the affected file(s) and/or the entity, that is under which circumstances an alert is to be issued. The alert notification(s) may be issued to the user, an administrator, a cloud storage service, and/or a data protection service such that protective measures can be taken if necessary.

Identification of entity performing operation on local file(s) and notification to reduce misuse risk

Cloud-based storage services are provided for storing and/or sharing content across multiple devices, where the content is periodically synchronized between the devices and the storage service. Conventionally, if locally stored content is deleted from a device, the delete would be propagated to the storage service causing the content to not only be deleted from the storage service but from any other devices where the content was locally stored and synchronized with the storage service. Embodiments are directed to retainment of locally deleted content at the storage service to prevent accidental or nefarious deletions of locally stored content on a device from further causing the content to be deleted universally from the storage service and/or multiple other devices. For example, the storage service may be configured to receive content stored locally on the device, detect a deletion of the content on the device, and retain the content at the storage service.

Retain locally deleted content at storage service

Cloud-based storage services are provided for storing and/or sharing content across multiple devices, where the content is periodically synchronized between the devices and the storage service. Embodiments are directed to retainment of locally deleted content at the storage service to prevent accidental or nefarious deletions of locally stored content on a device from being propagated to the storage service. For example, a selectable feature to retain locally deleted content, at the storage service may be presented through a display of a client device. A deletion of the content from the client device may be detected. The retained content may be prevented from being downloaded and stored locally on the client device when content at the storage service and the client device are synchronized if the feature was selected. If the feature was not selected, deletion options for the content may be presented through the display.

Retainment of locally deleted content at storage service by client device

A synchronization engine detects a notification of a change to a file. It determines whether an application associated with the file has indicated that the file is to be synchronized by the application. If so, the changes to the file are synchronized between a cloud-based storage system and a local disk by the application. Collaborative metadata, associated with the synchronized file, is updated to indicate a state of a copy of the file on the local disk and a copy of the file in the cloud-based storage system. The collaborative metadata is stored by the synchronization engine.

Techniques described herein allow for suggesting creation of distribution lists and suggesting use of distribution lists once they have been created. For instance, these techniques may track a frequency with which contacts (e.g., email addresses, phone numbers, screen names, etc.) are used with one another. The techniques may then suggest that a user create a distribution list that includes those contacts. Furthermore, once a contact has been associated with a particular distribution list, these techniques may suggest that a user send a message to this distribution list in response to the user selecting the contact (rather than the list) as a destination of the message.

Creation and suggestion of contact distribution lists

Content formatting and installation techniques are described. In an implementation, a method includes receiving one or more inputs for initiating an installation process of one or more content items and performing the installation process without user intervention. The performing of the installation process includes obtaining a content package, from over a network, which includes a manifest which describes a content type for each of the content items. Each of the content items is installed for use by an application module based on a respective content type.

Content formatting and installation techniques

Context-sensitive content may be created that may be recognized by a particular program but ignored by other programs. For example, in an e-mail message or other type of message, content could be created that advises the user to download a particular client for an enhanced content-viewing experience, along with a link pointing to a site where the client may be downloaded. This content and link could be surrounded by tags that would not be recognized by most clients, but that would be recognized by the client that provides the enhanced experience. Thus, most clients would render the advice and link, but the client that provides the enhanced experience could be configured to omit the link when it recognizes the surrounding tags, since a recipient who is viewing the e-mail with that client already has access to the enhanced experience.

Program-sensitive link in content

Strategies are described for validating content transferred over a communication channel using a more effective approach than heretofore provided in the art. A content registration authority is provided which registers the content disseminated by one or more content providers to one or more client devices. A client device which receives content that has been registered can securely consume the content, based on an assumption that a content provider which furnishes the content is entrusted by the content registration authority to provide the content, and without prompting a user of the client device to expressly approve the content provider. In a first solution, the content registration authority registers the content by issuing a certification stamp; in a second solution, the content registration authority registers the content by storing registration information in a central repository. The content may contain instructions which perform operations in the context of an instant messenger application.

Provisions for validating content using a content registration authority

Growing community of inventors

Seattle, WA, United States of America

Adam Christopher Czeisler