Abstract: Techniques are described herein for normalizing the recipient style of electronic messages while preserving the discernible intent of the sender. Given an electronic message or series of messages with varying visual styles applied to message text and other content, the electronic message may be transformed with a normalized and consistent formatting style that is more pleasing to the recipient, while preserving the sender's discernible intent in stylizing the message.

Abstract: A cloud service stores and aggregates content that is obtained from different content sources using different protocols. For example, the content may include electronic messages, calendar information, contacts, social network content, feed data, search results, and the like. The cloud service aggregates content for each user based on the user's configuration settings. The cloud service may perform processing on the aggregated content before it is delivered and displayed to the user on the client device. For example, one or more views may be generated and stored by the cloud service before the view is requested from the client. Changes made to the aggregated content on the client may be synchronized with the content source. Searches may be made across all or a portion of the different content sources that are aggregated for a user.

Abstract: Technologies are described for chronological re-ordering of transmitted conversation components. A message transmitting a message chain in the conversation through a forward or reply action, or addition of a new participant may be kept at the top and the remainder of messages may be re-ordered in chronological order. In some examples, the displayed properties (metadata) or header information may be normalized, that is displayed in a consistent manner. In other examples, flat header information (textual data) may be analyzed and enriched. Thus, the header information may be presented with interactive features such as presence information, calendar presentation, and comparable ones.

Abstract: Technologies are described for rich visualization of embedded objects, attachments, and links within emails and similar forms of online conversations. In some examples, the embedded objects, attachments, and links may be analyzed and parsed to generate teasers, which may include enhanced images, summary information, and comparable features. The teasers may be presented within a body of an email or in a dedicated area of a conversation user interface and include interactive features such as presentation of detailed information upon selection without opening and processing individual emails.

Abstract: Policies are applied to specific data rather than to an entire computing device that contains the specific data. Access to the specific data is controlled by the policies utilizing various password or other authentication credential requirements, selective data caching, data transmission, temporary data storage, and/or pre-defined conditions under which the specific data is to be erased or rendered inaccessible. Policies may be defined by an administrator and pushed to a mobile computing device, whereat the policies are enforced.

Abstract: Technologies are described for chronological re-ordering of transmitted conversation components. A message transmitting a message chain in the conversation through a forward or reply action, or addition of a new participant may be kept at the top and the remainder of messages may be re-ordered in chronological order. In some examples, the displayed properties (metadata) or header information may be normalized, that is displayed in a consistent manner. In other examples, flat header information (textual data) may be analyzed and enriched. Thus, the header information may be presented with interactive features such as presence information, calendar presentation, and comparable ones.

Abstract: Technologies are described for chronological re-ordering of transmitted conversation components. A message transmitting a message chain in the conversation through a forward or reply action, or addition of a new participant may be kept at the top and the remainder of messages may be re-ordered in chronological order. In some examples, the displayed properties (metadata) or header information may be normalized, that is displayed in a consistent manner. In other examples, flat header information (textual data) may be analyzed and enriched. Thus, the header information may be presented with interactive features such as presence information, calendar presentation, and comparable ones.

Abstract: A cloud service stores and aggregates content that is obtained from different content sources using different protocols. For example, the content may include electronic messages, calendar information, contacts, social network content, feed data, search results, and the like. The cloud service aggregates content for each user based on the user's configuration settings. The cloud service may perform processing on the aggregated content before it is delivered and displayed to the user on the client device. For example, one or more views may be generated and stored by the cloud service before the view is requested from the client. Changes made to the aggregated content on the client may be synchronized with the content source. Searches may be made across all or a portion of the different content sources that are aggregated for a user.

Abstract: Technologies are described for chronological re-ordering of transmitted conversation components. A message transmitting a message chain in the conversation through a forward or reply action, or addition of a new participant may be kept at the top and the remainder of messages may be re-ordered in chronological order. In some examples, the displayed properties (metadata) or header information may be normalized, that is displayed in a consistent manner. In other examples, flat header information (textual data) may be analyzed and enriched. Thus, the header information may be presented with interactive features such as presence information, calendar presentation, and comparable ones.

Abstract: A cloud service stores and aggregates content that is obtained from different content sources using different protocols. For example, the content may include electronic messages, calendar information, contacts, social network content, feed data, search results, and the like. The cloud service aggregates content for each user based on the user's configuration settings. The cloud service may perform processing on the aggregated content before it is delivered and displayed to the user on the client device. For example, one or more views may be generated and stored by the cloud service before the view is requested from the client. Changes made to the aggregated content on the client may be synchronized with the content source. Searches may be made across all or a portion of the different content sources that are aggregated for a user.

Abstract: Technologies are described for rich visualization of embedded objects, attachments, and links within emails and similar forms of online conversations. In some examples, the embedded objects, attachments, and links may be analyzed and parsed to generate teasers, which may include enhanced images, summary information, and comparable features. The teasers may be presented within a body of an email or in a dedicated area of a conversation user interface and include interactive features such as presentation of detailed information upon selection without opening and processing individual emails.

Abstract: A cloud service stores and aggregates content that is obtained from different content sources using different protocols. For example, the content may include electronic messages, calendar information, contacts, social network content, feed data, search results, and the like. The cloud service aggregates content for each user based on the user's configuration settings. The cloud service may perform processing on the aggregated content before it is delivered and displayed to the user on the client device. For example, one or more views may be generated and stored by the cloud service before the view is requested from the client. Changes made to the aggregated content on the client may be synchronized with the content source. Searches may be made across all or a portion of the different content sources that are aggregated for a user.

Abstract: A cloud service stores and aggregates content that is obtained from different content sources using different protocols. For example, the content may include electronic messages, calendar information, contacts, social network content, feed data, search results, and the like. The cloud service aggregates content for each user based on the user's configuration settings. The cloud service may perform processing on the aggregated content before it is delivered and displayed to the user on the client device. For example, one or more views may be generated and stored by the cloud service before the view is requested from the client. Changes made to the aggregated content on the client may be synchronized with the content source. Searches may be made across all or a portion of the different content sources that are aggregated for a user.

Abstract: Techniques are described herein for normalizing the recipient style of electronic messages while preserving the discernible intent of the sender. Given an electronic message or series of messages with varying visual styles applied to message text and other content, the electronic message may be transformed with a normalized and consistent formatting style that is more pleasing to the recipient, while preserving the sender's discernible intent in stylizing the message.

Abstract: A cloud service stores and aggregates content that is obtained from different content sources using different protocols. For example, the content may include electronic messages, calendar information, contacts, social network content, feed data, search results, and the like. The cloud service aggregates content for each user based on the user's configuration settings. The cloud service may perform processing on the aggregated content before it is delivered and displayed to the user on the client device. For example, one or more views may be generated and stored by the cloud service before the view is requested from the client. Changes made to the aggregated content on the client may be synchronized with the content source. Searches may be made across all or a portion of the different content sources that are aggregated for a user.

Abstract: Policies are applied to specific data rather than to an entire computing device that contains the specific data. Access to the specific data is controlled by the policies utilizing various password or other authentication credential requirements, selective data caching, data transmission, temporary data storage, and/or pre-defined conditions under which the specific data is to be erased or rendered inaccessible. Policies may be defined by an administrator and pushed to a mobile computing device, whereat the policies are enforced.