Microsoft Technology Licensing, LLC

Sowmy Srinivasan

Sanjay H Ramaswamy

Dheepak Ramaswamy

Julian Alexander Zbogar-Smith

Le-Wu Tung

Kamal Janardhan

Gagandeep S Kohli

Song Yang

Stefan Harrington Pharies

Douglas M Purdy

Natasha Harish Jethanandani

Krishna Kumar Parthasarathy

Hao Zhang

Neelamadhaba Mahapatro

Yann Christensen

Anatoly Victor Koretsky

Mashuri R Libman

Lucy Chao

Jack Kabat

Sridharan Ramanathan

Elena A Kharitidi

Øystein Torbjørnsen

Ryan Wilhelm

Christopher Heino, Jr

Technologies are described to increase a data limit for a user of a communication application by introducing additional archive mailboxes as the original archive fills up or subsequently added archive mailboxes fill up. Thus, a user's data limit may be effectively removed through the use of N additional archive mailboxes. The additional mailboxes may be integrated into the architecture of the communication application such that their use is transparent to the user and/or an administrator of the communication application or associated service. In other examples, additional mailboxes may be used to add to the capacity of the primary mailbox (cached) as well.

Large data management in communication applications through multiple mailboxes

Technologies are described to increase a data limit for a user by introducing additional archive mailboxes as the original archive fills up or subsequently added archive mailboxes fill up. Thus, a user's data limit may be effectively removed through the use of additional archive mailboxes. In some examples, the additional mailboxes may be integrated into the architecture of the communication application such that their use is transparent to the user and/or an administrator of the communication application or associated service through the use of an application programming interface (API) that exposes a single multivalued strongly typed collection instead of dealing with multiple attributes and extending the schema every time a new type needs to be added. A mailbox locations attribute may act as the main storage of serialized mailbox locations and a mailbox identifier attribute may be used for indexing.

Architecture for large data management in communication applications through multiple mailboxes

User input mechanisms are displayed for defining a compliance policy update. A unified compliance policy update is generated according to a unified schema that is consistent across different workloads. The unified compliance policy update is sent to a workload where it is deployed.

Unified generation of policy updates

Sparse data may be stored in a search index such that one or more data points related to a number of entities may be queriable. Upon detection of a data point related to an entity, an integer array may be created for the data point to store within a single column of the search index, the integer array including an identifier of the entity and a value associated with the data point. In response to receiving a request from a user to perform a query on the search index that includes the data point, the query may be transformed to a corresponding range based on the identifier of the entity. Upon execution of the query, the identifier may be removed and query results may be provided to the user as another array with a user-compatible identifier for the entity such that the results may be understood by the user.

Efficient storage of related sparse data in a search index

Methods, systems, and computer program products for converting an object of one type to an object of another type that allow for the runtime operation of the conversion process to be altered or customized. The conversion may occur within an extensible serialization engine that serializes, deserializes, and transforms objects of various types. The runtime operation of the serialization engine is altered by one or more extension routines that implement the desired customizations or extensions, without requiring replacement of other existing routines. Based on type information, identified for an initial object, the object is converted to an intermediate representation which permits runtime modification, including modification of object names, object types, and object data. The intermediate representation of the initial object is modified in accordance with extension routines that alter the runtime operation of the serialization engine, and the intermediate representation is converted to a final object and type.

Type bridges

A versionable schema is both backward-compatible and forward-compatible. Such a schema is able to receive data expected by multiple versions of the schema; tolerates the absence of optional data, in accordance with other versions, and accept wildcard data in accordance with still further versions. Thus, a message or message may be validated by the versionable schema.

Type evolution

Growing community of inventors

Redmond, WA, United States of America

Sowmy Srinivasan