Create a Video Indexer account connected to Azure
When creating a Video Indexer account, you can choose a free trial account (where you get a certain number of free indexing minutes) or a paid option (where you're not limited by the quota). With a free trial, Video Indexer provides up to 600 minutes of free indexing to website users and up to 2400 minutes of free indexing to API users. With the paid option, you create a Video Indexer account that's connected to your Azure subscription and an Azure Media Services account. You pay for minutes indexed as well as the media account related charges.
This article shows how to create a Video Indexer account that's linked to an Azure subscription and an Azure Media Services account. The topic provides steps for connecting to Azure using the automatic (default) flow. It also shows how to connect to Azure manually (advanced).
An Azure subscription.
If you don't have an Azure subscription yet, sign up for Azure Free Trial.
An Azure Active Directory (Azure AD) domain.
If you don't have an Azure AD domain, create this domain with your Azure subscription. For more information, see Managing custom domain names in your Azure AD
A user in your Azure AD domain with an Application administrator role. You'll use this member when connecting your Video Indexer account to Azure.
This user should be an Azure AD user with a work or school account. Don't use a personal account, such as outlook.com, live.com, or hotmail.com.
Additional prerequisites for automatic flow
A user and member in your Azure AD domain.
You'll use this member when connecting your Video Indexer account to Azure.
This user should be a member in your Azure subscription with either an Owner role, or both Contributor and User Access Administrator roles. A user can be added twice, with two roles. Once with Contributor and once with user Access Administrator.
Additional prerequisites for manual flow
Register the EventGrid resource provider using the Azure portal.
In the Azure portal, go to Subscriptions->[subscription]->ResourceProviders.
Search for Microsoft.Media and Microsoft.EventGrid. If not in the "Registered" state, click Register. It takes a couple of minutes to register.
Connect to Azure
If your Azure subscription uses certificate-based multi-factor authentication, it's crucial that you perform the following steps on a device that has the required certificates installed.
Browse to the Video Indexer website and sign in.
Select the Create new account button:
When the subscriptions list appears, select the subscription you want to use.
Select an Azure region from the supported locations: West US 2, North Europe, or East Asia.
Under Azure Media Services account, choose one of these options:
To create a new Media Services account, select Create new resource group. Provide a name for your resource group.
Azure will create your new account in your subscription, including a new Azure Storage account. Your new Media Services account has a default initial configuration with a streaming endpoint and 10 S3 reserved units.
To use an existing Media Services account, select Use existing resource. From the accounts list, select your account.
Your Media Services account must have the same region as your Video Indexer account.
To manually configure your connection, select the Switch to manual configuration link.
For detailed information, see the Connect to Azure manually (advanced option) section that follows.
When you're done, choose Connect. This operation might take up to a few minutes.
After you're connected to Azure, your new Video Indexer account appears in the account list:
Browse to your new account.
Connect to Azure manually (advanced option)
If the connection to Azure failed, you can attempt to troubleshoot the problem by connecting manually.
It's highly recommended to have the following three accounts in the same region: the Video Indexer account that you're connecting with the Media Services account, as well as the Azure storage account connected to the same Media Services account.
Create and configure a Media Services account
When creating a storage account for your Media Services account, select StorageV2 for account kind and Geo-redundant (GRS) for replication fields.
Make sure to write down the Media Services resource and account names. You'll need them for the steps in the next section.
Before you can play your videos in the Video Indexer web app, you must start the default Streaming Endpoint of the new Media Services account.
In the new Media Services account, select Streaming endpoints. Then select the streaming endpoint and press start.
For Video Indexer to authenticate with Media Services API, an AD app needs to be created. The following steps guide you through the Azure AD authentication process described in Get started with Azure AD authentication by using the Azure portal:
In the new Media Services account, select API access.
Get the client ID and client secret
After you select Settings->Keys, add Description, press Save, and the key value gets populated.
If the key expires, the account owner will have to contact Video Indexer support to renew the key.
Make sure to write down the key value and the Application ID. You'll need it for the steps in the next section.
In the Connect Video Indexer to an Azure subscription dialog of your Video Indexer page, select the Switch to manual configuration link.
In the dialog, provide the following information:
|Video Indexer account region||The name of the Video Indexer account region. For better performance and lower costs, it's highly recommended to specify the name of the region where the Azure Media Services resource and Azure Storage account are located.|
|Azure AD tenant||The name of the Azure AD tenant, for example "contoso.onmicrosoft.com". The tenant information can be retrieved from the Azure portal. Place your cursor over the name of the signed-in user in the top-right corner. Find the name to the right of Domain.|
|Subscription ID||The Azure subscription under which this connection should be created. The subscription ID can be retrieved from the Azure portal. Select All services in the left panel, and search for "subscriptions". Select Subscriptions and choose the desired ID from the list of your subscriptions.|
|Azure Media Services resource group name||The name for the resource group in which you created the Media Services account.|
|Media service resource name||The name of the Azure Media Services account that you created in the previous section.|
|Application ID||The Azure AD application ID (with permissions for the specified Media Services account) that you created in the previous section.|
|Application key||The Azure AD application key that you created in the previous section.|
The following Azure Media Services related considerations apply:
If you connect automatically, you see a new Resource Group, Media Services account, and a Storage account in your Azure subscription.
If you connect automatically, Video Indexer sets the media Reserved Units to 10 S3 units:
If you connect to an existing Media Services account, Video Indexer doesn't change the existing media Reserved Units configuration.
You might need to adjust the type and number of Media Reserved Units according to your planned load. Keep in mind that if your load is high and you don't have enough units or speed, videos processing can result in timeout failures.
If you connect to a new Media Services account, Video Indexer automatically starts the default Streaming Endpoint in it:
Streaming endpoints have a considerable startup time. Therefore, it may take several minutes from the time you connected your account to Azure until your videos can be streamed and watched in the Video Indexer web app.
If you connect to an existing Media Services account, Video Indexer doesn't change the default Streaming Endpoint configuration. If there's no running Streaming Endpoint, you can't watch videos from this Media Services account or in Video Indexer.
You can programmatically interact with your trial account and/or with your Video Indexer accounts that are connected to Azure by following the instructions in: Use APIs.
You should use the same Azure AD user you used when connecting to Azure.
Laster inn tilbakemelding ...