Content Stays in Your Azure Subscription

What you can do together

• Run the portal on a storage account in your own subscription, commercial or government cloud, through Nexus.
• Pull a container you already fill into the library on a schedule, limited to the folders and file types you choose.
• Give each file a transcript, a place in search, a SHA-384 integrity hash, a custody record and a retention schedule, with Nexus.
• Move aging content to cool and archive tiers by policy, previewed before it runs, so the library costs less to hold as it grows.
• Ask AI Intelligence Hub, included in both Digital Evidence Management and Enterprise Video Platform, a question across the library and get a cited answer limited to what you may see.

How it connects

As a storage provider, Azure Storage is chosen per portal, and a customer's own storage account is usable, so the library lives in an account you own. Content sits on hot, cool or archive tiers, moved by policy or in bulk from the library, and archived content is rehydrated before it is opened. Where the storage provider supports object-level holds, a legal hold placed in the portal is enforced at the storage layer as well.

As an ingestion connector, a container the organization already fills is pulled on a schedule. Files and their metadata come inbound, scoped by an extension allowlist and excluded folders, with the source hierarchy preserved or flattened. After a file lands, the source is left, moved or deleted, as configured. Ingestion runs on the connector's schedule rather than on storage events.

As a migration target, a library moves between storage providers without leaving the platform, so a deployment changes provider or region without re-uploading. Nothing else flows. Account keys, access policies and networking stay in Azure, and who may open an item is decided by the portal's roles, not by container permissions.