"ErrorType":"ARM_ACCOUNT_MUST_BE_MANAGED_BY_ARM" while running API

Question

Hi,

I had created a trial account for Azure Video Indexer and then my manager created a paid Indexer account using the Azure portal(Non ARM based account only) and made me the contributor for that paid account.
Now I am trying to trigger the API using the API portal https://api-portal.videoindexer.ai/api-details#api=Operations&operation=Get-Account-Access-Token-With-Permission
However if I use the accountId of the paid account indexer and the subscription key from above portal I get the below error whereas using the accountId of trial account and same Subscription key as above successfully triggers the API.

I am confused here that if the Indexer account was not created using the ARM method then why is it showing such error.

Error details :

{
    "ErrorType": "ARM_ACCOUNT_MUST_BE_MANAGED_BY_ARM",
    "Message": "You can only use the ARM management API for management calls on accounts created on ARM. <a href=\"https://aka.ms/avam-arm-docs\">Learn more</a>. Trace id: '5e2801d9-9cb3-4f8e-9c33-5a525810341c'."
}

Answer 1

@Gambhir, Rishabh If you have followed the steps on this page to create a VI resource then the resource created is an ARM account and not a classic account. This is the reason the API you are using is throwing an error saying that the account is managed by ARM.

This article walks you through the steps of creating the Azure AI Video Indexer account and its accompanying resources. The account that gets created is Azure Resource Manager (ARM) account. For information about different account types, see Overview of account types.

A paid account is an ARM account and you need to use the correct API to generate the access token.

Azure AI Video Indexer paid accounts are Azure Resource Manager (ARM) based and unlike trial accounts, are created with your Azure subscription. ARM-based accounts give you access to security and management capabilities, such as Role Based Access Control (RBAC) user management, Azure Monitor integration, deployment through ARM templates, and more.

You can no longer create a classic account. Existing Classic accounts will be retired on June 30th, 2024. If you currently have a classic account, see the migration guide.

I hope this helps!!

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.