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: An abstraction layer communicates with a plurality of applications executing on a multi-application platform. The abstraction exposes a standard interface for the plurality of applications to communicate content status information. An indication is received that a new content item will be generated. A record is generated that is immutably associated with the new content item. The record is updated with information received from the application associated with the content item, the information pertaining to a changed status of the content item. In response to a command to delete the content item, it is determined whether to confirm deletion of the content item based on one or more data retention policies. The record is updated to indicate a reason for granting or denying the deletion and a source of the delete command.

Abstract: A query scoping service enables administrators to scope a directory attribute bound query to an organizational boundary within an organizational structure. The directory attribute bound query may be scoped to a subset of users that have specific value(s) for specific user attributes. The directory attribute bound query includes a search string. Data that is analyzed with respect to the search string is limited to data that is stored in association with users that have specific value(s) for specific user attributes. In this way, data files that are stored in association with users that do not have the specific values for the specific directory attributes will be omitted from query results. The directory attribute bound query may be tied to data retention rules. Since the scope of the directory attribute bound query is defined based on the organizational structure, the query scope remains accurate notwithstanding changes occurring in the organizational structure.

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: Aspects of the present disclosure relate to systems and methods for creating compliance boundaries. In one example, compliance boundaries may be implemented via a compliance tool. Data associated with a tenant may be segregated using a plurality of layers defining one or more compliance boundaries. In response to an action initiated by a compliance administrator using the compliance tool for accessing the data, it may be determined which data is within the one or more compliance boundaries associated with the compliance administrator. Access to the data determined to be within the one or more compliance boundaries associated with the compliance administrator may be authorized.

Abstract: An abstraction layer communicates with a plurality of applications executing on a multi-application platform. The abstraction exposes a standard interface for the plurality of applications to communicate content status information. An indication is received that a new content item will be generated. A record is generated that is immutably associated with the new content item. The record is updated with information received from the application associated with the content item, the information pertaining to a changed status of the content item. In response to a command to delete the content item, it is determined whether to confirm deletion of the content item based on one or more data retention policies.

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: An abstraction layer communicates with a plurality of applications executing on a multi-application platform. The abstraction exposes a standard interface for the plurality of applications to communicate content status information. An indication is received that a new content item will be generated. A record is generated that is immutably associated with the new content item. The record is updated with information received from the application associated with the content item, the information pertaining to a changed status of the content item. In response to a command to delete the content item, it is determined whether to confirm deletion of the content item based on one or more data retention policies. The record is updated to indicate a reason for granting or denying the deletion and a source of the delete command.

Abstract: Aspects of the present disclosure relate to systems and methods for creating compliance boundaries. In one example, compliance boundaries may be implemented via a compliance tool. Data associated with a tenant may be segregated using a plurality of layers defining one or more compliance boundaries. In response to an action initiated by a compliance administrator using the compliance tool for accessing the data, it may be determined which data is within the one or more compliance boundaries associated with the compliance administrator. Access to the data determined to be within the one or more compliance boundaries associated with the compliance administrator may be authorized.

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: 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: Computer systems, devices, and associated methods of content pattern based automatic document classification are disclosed herein. In one embodiment, a method includes receiving a document and a sequence of words corresponding to a document class having a class label from a network storage. The method also includes determining a longest common subsequence of words between the words in the document and the sequence of words and calculating a similarity percentage between the document and the sequence of words based on the determined longest common subsequence. When the calculated similarity percentage is above a threshold, the class label corresponding to the document class is automatically applied to the received document in the network storage.

Abstract: Techniques for isolating a portion of an online computing service referred to as a deployment unit and configured with a complete build of the online computing service may include routing production traffic away from the deployment unit, applying one or more changes to the complete build, and after applying one or more changes to the complete build, using the deployment unit for testing these changes using end-to-end tests. In one embodiment, the deployment unit may be dedicated to a specific group of tenants that require at least some isolation from other tenants.

Abstract: A query scoping service enables administrators to scope a directory attribute bound query to an organizational boundary within an organizational structure. The directory attribute bound query may be scoped to a subset of users that have specific value(s) for specific user attributes. The directory attribute bound query includes a search string. Data that is analyzed with respect to the search string is limited to data that is stored in association with users that have specific value(s) for specific user attributes. In this way, data files that are stored in association with users that do not have the specific values for the specific directory attributes will be omitted from query results. The directory attribute bound query may be tied to data retention rules. Since the scope of the directory attribute bound query is defined based on the organizational structure, the query scope remains accurate notwithstanding changes occurring in the organizational structure.

Abstract: An abstraction layer communicates with a plurality of applications executing on a multi-application platform. The abstraction exposes a standard interface for the plurality of applications to communicate content status information. An indication is received that a new content item will be generated. A record is generated that is immutably associated with the new content item. The record is updated with information received from the application associated with the content item, the information pertaining to a changed status of the content item. In response to a command to delete the content item, it is determined whether to confirm deletion of the content item based on one or more data retention policies. The record is updated to indicate a reason for granting or denying the deletion and a source of the delete command.

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: Computer systems, devices, and associated methods of content pattern based automatic document classification are disclosed herein. In one embodiment, a method includes receiving a document and a sequence of words corresponding to a document class having a class label from a network storage. The method also includes determining a longest common subsequence of words between the words in the document and the sequence of words and calculating a similarity percentage between the document and the sequence of words based on the determined longest common subsequence. When the calculated similarity percentage is above a threshold, the class label corresponding to the document class is automatically applied to the received document in the network storage.

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: Aspects of the present disclosure relate to systems and methods for creating compliance boundaries. In one example, compliance boundaries may be implemented via a compliance tool. Data associated with a tenant may be segregated using a plurality of layers defining one or more compliance boundaries. In response to an action initiated by a compliance administrator using the compliance tool for accessing the data, it may be determined which data is within the one or more compliance boundaries associated with the compliance administrator. Access to the data determined to be within the one or more compliance boundaries associated with the compliance administrator may be authorized.

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.