Abstract: A computer implemented method includes collecting collaboration information containing data representative of collaborations between at least two individuals, applying time allocation heuristics to the collected collaboration data to extract respective collaborations times for the at least two individuals, storing the extracted collaborations times on a storage device, and accessing the storage device to process queries regarding collaboration between the at least two individuals.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: A meeting insight computing system includes a meeting evaluation machine configured to collect quality parameters from meeting quality monitoring devices. The quality parameters each quantify meeting conditions during one or more previously-elapsed meetings and are usable to determine an overall quality score for each of the one or more previously-elapsed meetings. A graphical scheduling interface is configured to facilitate scheduling of an upcoming meeting at a designated meeting time, in a meeting location, and with one or more meeting participants. An insight generation machine is configured to report a meeting insight via the graphical scheduling interface. The meeting insight is based on the meeting time, the meeting location, the one or more meeting participants, and the quality parameters, and includes a recommendation to change one or more of the meeting time, meeting location, and meeting participants to improve a quality score of the upcoming meeting.

Abstract: Techniques for labeling data files that enable a file management label to persist on a data file. Variations disclosed herein enable a file management label to be embedded within a data file so that the file management label propagates with the data file when the data file is copied and/or moved between systems and/or workloads. In some embodiments, an application may be configured to write the file management label directly into a stream of the data file. For example, an application client that is run locally on a client device may open the data file by accessing its corresponding stream. While the data file is open within the application client such that a user may edit content of the data file, the application client may be caused to associate the file management label with the data file. Ultimately, the application client may write this association directly into the stream.

Abstract: Systems and methods that enable implementation of content aware file management labeling. Techniques disclosed enable real-time analysis of a data file so that associations between the data file and applicable file management label(s) can be automatically suggested and/or made while a user is working in the data file. A user may deploy an application on a client device to edit a data file. While the user is actively editing the data file, the application may transmit modification data to a content analysis service which analyzes the modification data to determine whether the modifications result in a file management label becoming applicable to the data file. Ultimately, the content analysis service may transmit a verdict to the client device to cause the application to display a labeling suggestion to the user and/or to automatically apply a label to the data file while it is being worked on by the user.

Abstract: Information technology use policies based on classification of groups, teams, and sites is provided. Example systems may enable information technology administrators to specify which policies may apply based on manual or automatic classification of groups, teams and sites. This may include the ability to specify associated membership, sharing, and access policies, data storage and sharing locations, retention policies for different types of content, and application of various information governance and protection options/requirements. Information technology administrators, who inherently understand the data and information management needs of organizations and members, may define a reasonable set of simplified classification options that information workers can use. Thus, information workers may no longer need to learn the details of data policies.

Abstract: A lifecycle of an item is controlled based on a type of the item. Particular item types may be required by law, industry, or organizational policies and procedures to be retained for a defined time period. Often these required retention policies are triggered by events, and thus embodiments are directed to providing event triggered data retention. Items stored in a hosted service environment may each be associated with a label that defines an item category, a retention type, a retention period, and/or a retention trigger for the item. In response to detecting an occurrence of a retention trigger event associated with a person or a project, the items may be queried to determine each item associated with an asset identifier identifying the person or the project. The retention period and type for each item may be updated or set based on a retention policy associated with each item.

Abstract: A unified document retention management system exposes a retention policy management portal to enable a user to selectively prescribe a unified retention policy to multiple productivity platforms to deploy the unified retention policy across the user selected productivity platforms. Data retention rules of the unified retention policy may define actions to be performed with respect to files that satisfy certain predefined conditions. An exemplary data retention rule prescribes a retention age threshold to files that have been tagged with a particular label. Files may be manually labeled by users and/or may be automatically labeled by the system in accordance with one or more smart label rules. The retention age threshold may be enforced for such tagged files by preventing the files from being deleted and/or modified prior to them reaching the retention age threshold. Then the files may automatically be purged from system storage upon reaching the retention age threshold.

Abstract: Enhanced administrative tools for a unified file retention management system to enable selective activation of a data retention policy with respect to subsets of files across multiple productivity platforms. The system enables a user to selectively activate file management labels and/or file retention rules of a unified retention policy with respect to files that correspond to user defined filter parameters indicating subsets of files across user selected productivity platforms. Exemplary file management labels may prescribe a file retention period and a file purge age to files that have been tagged with a label. Files may be manually labeled by users and/or automatically labeled in accordance with smart label rules. The retention age threshold may be enforced for such tagged files by preventing the files from being deleted and/or modified during the file retention period. The files may automatically be purged from system storage upon reaching the file purge age.

Abstract: 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.

Abstract: 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.