Records365 consists of four major components, namely:

  1. Intelligent Policy Engine
  2. Connector Framework
  3. Search
  4. Secure Storage

The Intelligent Policy Engine sits at the heart of Records365. It is responsible for processing ingested objects from different content sources and the categorization 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 Intelligent Policy Engine allows customers to create a unified set of rules for applying information governance policies across all connected content sources.

The Connector Framework allows Records365 to easily manage content in multiple, heterogeneous content sources. A rich REST based API surface allows for content sources & types not natively supported to be rapidly integrated.

The Search component provides record managers with the ability to search through vast amounts of structured, semi-structured and unstructured data that is being managed by Records365.

Records365 federates with customer’s Azure Active Directory (AAD) to provide a seamless single sign-on (SSO) experience for users needing to access the Records365 web portal. As a result, users can use their corporate credentials to sign-in. In addition, any authentication policies such as multi-factor authentication are respected as well.

All service components are hosted on Microsoft Azure using a mix of virtualized compute resources as well as platform-as-a-service (PaaS) offerings.

All service components are built to be fault tolerant with multiple levels of redundancy. Processing tasks carried out by the service are spread across a cluster of compute nodes. Compute clusters are resilient to single and multi-node failures. Furthermore, compute clusters can be rapidly scaled to provide additional throughput when processing demand peaks. Storage & backup components of the service are geographically redundant.