Abstract: Customers in regulated industries face demanding compliance regulations, including content immutability. While broadened to allow software-based solutions, the regulations for immutability require content preservation to prevent overwriting, erasure or alteration of the content, where the preservation must be implemented through irrevocable features. Embodiments are directed to provision of an administrative user experience to enable customers to create a preservation policy that defines item(s) to be preserved. After detecting enablement of the policy, the item(s) may be preserved, a preservation lock on the policy may be initiated by disabling controls associated with the policy, and an attribute may be set to the policy to identify the policy as locked.

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 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: 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 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 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: Customers in regulated industries face demanding compliance regulations, including content immutability. While broadened to allow software-based solutions, the regulations for immutability require content preservation to prevent overwriting, erasure or alteration of the content, where the preservation must be implemented through irrevocable features. Embodiments are directed to provision of an administrative user experience to enable customers to create a preservation policy that defines item(s) to be preserved. After detecting enablement of the policy, the item(s) may be preserved, a preservation lock on the policy may be initiated by disabling controls associated with the policy, and an attribute may be set to the policy to identify the policy as locked.

Abstract: Customers in regulated industries face demanding compliance regulations, including content immutability. While broadened to allow software-based solutions, the regulations for immutability require content preservation to prevent overwriting, erasure or alteration of the content, where the preservation must be implemented through irrevocable features. Embodiments are directed to provision of an administrative user experience to enable customers to create a preservation policy that defines item(s) to be preserved. After detecting enablement of the policy, the item(s) may be preserved, a preservation lock on the policy may be initiated by disabling controls associated with the policy, and an attribute may be set to the policy to identify the policy as locked.

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: Customers in regulated industries face demanding compliance regulations, including content immutability. While broadened to allow software-based solutions, the regulations for immutability require content preservation to prevent overwriting, erasure or alteration of the content, where the preservation must be implemented through irrevocable features. Embodiments are directed to provision of an administrative user experience to enable customers to create a preservation policy that defines item(s) to be preserved. After detecting enablement of the policy, the item(s) may be preserved, a preservation lock on the policy may be initiated by disabling controls associated with the policy, and an attribute may be set to the policy to identify the policy as locked.

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.