Abstract: A file disposition review system analyzes multiple productivity platforms to generate an upcoming disposition report identifying data files that have reached a disposition review age associated with a file management label. A cross-platform manual review (CPMR) portal enables concurrent examination of file property data for data files identified in the upcoming disposition report. The CPMR portal further enables the disposition manager to simultaneously examine file property data corresponding to the data files identified in the upcoming disposition report and to issue disposition instructions. Exemplary disposition instructions may cause the multiple productivity platforms to permanently delete the identified data files without their underlying file content ever being transferred and/or copied from the particular productivity platforms that individual ones of the identified data files correspond to.

Abstract: Techniques to isolating a portion of an online computing service are described. The following description may refer to the isolated portion as a deployment unit configured with a complete build of the online computing service. In one embodiment, after applying one or more changes to the complete build, the deployment unit may be used for testing these changes using end-to-end tests. In another embodiment, the deployment unit may be dedicated to a specific group of tenants that require at least some isolation from other tenants. Other embodiments are described and claimed.

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: Techniques to isolating a portion of an online computing service are described. The following description may refer to the isolated portion as a deployment unit configured with a complete build of the online computing service. In one embodiment, after applying one or more changes to the complete build, the deployment unit may be used for testing these changes using end-to-end tests. In another embodiment, the deployment unit may be dedicated to a specific group of tenants that require at least some isolation from other tenants. Other embodiments are described and claimed.

Abstract: Representative embodiments disclose mechanisms to route electronic communications for supervisory review. Users of a messaging system are assigned appropriate permissions to create and manage supervisory review policies, access supervisory review mailboxes to perform supervisory review actions, run reports and other activities associated with supervisory review. Supervisory review policies are pushed out to a supervisory review agent through a policy sync service and the supervisory review agent tests incoming and outgoing messages against the policy. Each policy selects electronic communications and routes the communication to an associated supervisory review mailbox or folder. Additional assistants can receive other electronic communications (social media, chat, voicemail, etc.) and route them to the supervisory review mailbox if the communication meets one or more policies.

Abstract: Techniques to isolating a portion of an online computing service are described. The following description may refer to the isolated portion as a deployment unit configured with a complete build of the online computing service. In one embodiment, after applying one or more changes to the complete build, the deployment unit may be used for testing these changes using end-to-end tests. In another embodiment, the deployment unit may be dedicated to a specific group of tenants that require at least some isolation from other tenants. Other embodiments are described and claimed.

Abstract: A certificate management system provides automated management of certificate lifecycles and certificate distribution. Rather than depend upon an administrator to manually distribute and manage certificates, the system self-generates certificates, distributes the certificates to appropriate servers or other parties, and transitions from old certificates to new certificates in a well-defined manner that avoids breaking functionality. After generating one or more certificates, the system securely shares certificates in a way that parties that use them can find the new certificates without an administrator manually distributing the certificates. When it is time to update certificates, the system generates new certificates and shares the new certificates in a similar way. During a transition period, the system provides a protocol by which both old and new certificates can be used to perform authenticated access to resources, so that the transition from an old to a new certificate does not break services.

Abstract: A certificate management system provides automated management of certificate lifecycles and certificate distribution. Rather than depend upon an administrator to manually distribute and manage certificates, the system self-generates certificates, distributes the certificates to appropriate servers or other parties, and transitions from old certificates to new certificates in a well-defined manner that avoids breaking functionality. After generating one or more certificates, the system securely shares certificates in a way that parties that use them can find the new certificates without an administrator manually distributing the certificates. When it is time to update certificates, the system generates new certificates and shares the new certificates in a similar way. During a transition period, the system provides a protocol by which both old and new certificates can be used to perform authenticated access to resources, so that the transition from an old to a new certificate does not break services.