Records365 consists of four major components, namely:
The processing engine sits at the heart of Records365. It is responsible for processing ingested objects from different content sources and the categorisation of items using a powerful rules engine. Only the metadata of an object is required to be ingested into Records365 the file or document remains in place in the content source and can be edited by users in the content source.
The rules engine uses a single unified set of policy across all content sources. This significantly simplifies the task of managing rules in the records management lifecycle.
The connector framework allows Records365 to easily manage content in multiple, disparate content sources. A rich set of APIs allow for management of bespoke content sources.
The search component provides record managers with the ability to search through vast amounts of unstructured data under management in Records365. As with the other Records365 components, search can index metadata from many different content sources.
Microsoft Azure Active Directory (AAD) is leveraged by Records365 to seamlessly integrate the various content sources that can be managed. Furthermore, end-users needing access to the Records365 portal can use their corporate credentials providing a federated sign-on experience.
All components are hosted entirely within Microsoft Azure using a cloud scale processing platform based on distributed microservices and replicated storage.