Manage multiple tenants

Important

Due to the Azure Media Services retirement announcement, Azure AI Video Indexer announces Azure AI Video Indexer features adjustments. See Changes related to Azure Media Service (AMS) retirement to understand what this means for your Azure AI Video Indexer account. See the Preparing for AMS retirement: VI update and migration guide.

This article discusses different options for managing multiple tenants with Azure AI Video Indexer. Choose a method that is most suitable for your scenario:

• Azure AI Video Indexer account per tenant
• Single Azure AI Video Indexer account for all tenants
• Azure subscription per tenant

Azure AI Video Indexer account per tenant

When using this architecture, an Azure AI Video Indexer account is created for each tenant. The tenants have full isolation in the persistent and compute layer.

Considerations

• Customers don't share storage accounts (unless manually configured by the customer).

• Customers don't share compute (reserved units) and don't impact processing jobs times of one another.

• You can easily remove a tenant from the system by deleting the Azure AI Video Indexer account.

• There's no ability to share custom models between tenants.

  Make sure there's no business requirement to share custom models.

• Harder to manage due to multiple Azure AI Video Indexer accounts per tenant.

Tip

Create an admin user for your system in the Azure AI Video Indexer developer portal and use the Authorization API to provide your tenants the relevant account access token.

Single Azure AI Video Indexer account for all users

When using this architecture, the customer is responsible for tenants isolation. All tenants have to use a single Azure AI Video Indexer account. When uploading, searching, or deleting content, the customer will need to filter the proper results for that tenant.

With this option, customization models (Person, Language, and Brands) can be shared or isolated between tenants by filtering the models by tenant.

When uploading videos, you can specify a different partition attribute per tenant. This will allow isolation in the search API. By specifying the partition attribute in the search API you'll only get results of the specified partition.

Considerations

• Ability to share content and customization models between tenants.
• One tenant impacts the performance of other tenants.
• Customer needs to build a complex management layer on top of Azure AI Video Indexer.

Tip

You can use the priority attribute to prioritize tenants jobs.

Azure subscription per tenant

When using this architecture, each tenant will have their own Azure subscription. For each user, you'll create a new Azure AI Video Indexer account in the tenant subscription.

Considerations

• This is the only option that enables billing separation.
• This integration has more management overhead than Azure AI Video Indexer account per tenant. If billing isn't a requirement, it's recommended to use one of the other options described in this article.