I am working on a flow in Logic Apps. Once a video has finished indexing, this flow is triggered. The flow is intended to save the outputs of the Get Prompt Content API ( https://api-portal.videoindexer.ai/api-details#api=Operations&operation=Create-Prompt-Content ) so that I can embed and use in some LLM activities. I have an ARM-managed Azure AI Video Indexer account I am generating an access token according to this documentation for ARM-managed accounts, my scope, permissions and video ID are all correct - https://learn.microsoft.com/en-us/rest/api/videoindexer/generate/access-token?view=rest-videoindexer-2024-01-01&tabs=HTTP#generate-accesstoken-for-account-contributor The access key is create successfully, and indeed works when using a different API (Get Video Index), but when trying the Create Prompt Content API I receive the following error message: "ErrorType": "USER_NOT_SIGNED_IN", "Message": "User not found in access token. I have checked all of my authorisations as far as I can tell. But If anyone can provided a list of specific things to check as part of a response to this question I would appreciate it. I have tried manually sending the API request from the documentation page using "Try It" and get a successful response, but cannot see the different between the two approaches. I am certain that the problem is caused by not correctly sending my API key with the URI. That is the only difference I can see.

Persistent error message when attempting to use Azure AI Video Indexer API (ARM-managed) - "USER_NOT_SIGNED_IN"

Ewan OToole 5

I am working on a flow in Logic Apps. Once a video has finished indexing, this flow is triggered. The flow is intended to save the outputs of the Get Prompt Content API (https://api-portal.videoindexer.ai/api-details#api=Operations&operation=Create-Prompt-Content) so that I can embed and use in some LLM activities.
I have an ARM-managed Azure AI Video Indexer account
I am generating an access token according to this documentation for ARM-managed accounts, my scope, permissions and video ID are all correct - https://learn.microsoft.com/en-us/rest/api/videoindexer/generate/access-token?view=rest-videoindexer-2024-01-01&tabs=HTTP#generate-accesstoken-for-account-contributor
The access key is create successfully, and indeed works when using a different API (Get Video Index), but when trying the Create Prompt Content API I receive the following error message:

"ErrorType": "USER_NOT_SIGNED_IN",  "Message": "User not found in access token.

I have checked all of my authorisations as far as I can tell. But If anyone can provided a list of specific things to check as part of a response to this question I would appreciate it.
I have tried manually sending the API request from the documentation page using "Try It" and get a successful response, but cannot see the different between the two approaches.
I am certain that the problem is caused by not correctly sending my API key with the URI. That is the only difference I can see.

romungi-MSFT 43,451 Reputation points Microsoft Employee

2024-05-13T07:46:15.3033333+00:00
@Ewan OToole Try this in the body of the request as mentioned in the reference. The scope is supposed to be Video instead of Project.

Ref: https://learn.microsoft.com/en-us/rest/api/videoindexer/generate/access-token?view=rest-videoindexer-2024-01-01&tabs=HTTP#generate-accesstoken-for-video-contributor

POST https://management.azure.com/subscriptions/b04775c3-63fa-40f3-9430-139d2e5522d3/resourceGroups/contosto-videoanalyzer-rg/providers/Microsoft.VideoIndexer/accounts/contosto-videoanalyzer/generateAccessToken?api-version=2024-01-01 { "permissionType": "Contributor", "scope": "Video", "videoId": "07ec9e38d4" }

I think you could also try this API for ARM based from API portal.

https://api-portal.videoindexer.ai/api-details#api=Operations&operation=Get-Video-Access-Token
Ewan OToole 5 Reputation points

2024-05-28T17:52:55.43+00:00

I have checked all the scopes and permissions against the API documentation, and only ARM-based APIs work. I'm so frustrated with this, I've tried everything I can think of :(
AS-8820 0 Reputation points

2024-06-06T17:22:05.33+00:00

Did you guys ever figure it out? I tried from both Logic Apps and PowerAutomate, unsurprisingly, both return the same response: "User not found in access token.".

If I take that same request URL and just paste it in Postman with no modification whatsoever, it works.