Multi-tenancy is an architecture where multiple tenants share the same instance of a service. This model is common for organizations that subscribe to a shared services model for the provisioning of their IT services. Azure Active Directory (AAD) is an example of a shared IT service.
Organizations may also utilize a multi-tenant model when a single AAD instance is used for both Production and Test environments.
Records365 integrates with AAD as an Enterprise Application to manage user sign-ins. The following page provides an introduction to app objects and service principals: https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals#service-principal-object
Records365 supports both single or multi-tenant AAD models. This allows customers to use the same AAD for authorization for test and production environments and also allows customers who have shared services arrangements to have multiple production environments, separated by the secondary nominated AAD field.
When configuring Records365 to be multi-tenant, a secondary AAD field must be nominated. This allows the organisation to differentiate between users, such that at time of user login they are directed to the correct Records365 tenant.
- The secondary nominated AAD field must be the same across all tenants sharing the one subscription, for example CompanyName. All supported secondary fields are listed below.
- All users must have the nominated AAD field populated according to their relevant tenant
- If a user logging into a multi-tenant Records365 does not have the nominated AAD field set to match that of a single Records365 tenant, access to Records365 will not be granted
When using a Records365 multi-tenant environment, the SharePoint Online and OneDrive for Business connectors only support the whitelisting of sites, and will not allow the utilization of the All option for managed site configuration.
Supported Secondary Fields
Supported Custom Fields