Skip to content

Commit a113e6b

Browse files
authored
Update logic-apps-connector-arm-accounts.md
1 parent 85d96b4 commit a113e6b

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/azure-video-indexer/logic-apps-connector-arm-accounts.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -160,13 +160,15 @@ The following image shows the first flow:
160160
|----|----|
161161
|Location| Location of the associated the Azure Video Indexer account.|
162162
| Account ID| Account ID of the associated Azure Video Indexer account. You can find the **Account ID** in the **Overview** page of your account, in the Azure portal. Or, the **Account settings** tab, left of the [Azure Video Indexer website](https://www.videoindexer.ai/).|
163-
|Access Token| Use the `body('HTTP')['accessToken']` expression to extract the access token in the right format from the previous HTTP call.|
163+
|Access Token| Use the `body('HTTP')['accessToken']` expression to extract the access token in the right format from the previous HTTP call.|
164164
| Video Name| Select **List of Files Name** from the dynamic content of **When a blob is added or modified** action. |
165165
|Video URL|Select **Web Url** from the dynamic content of **Create SAS URI by path** action.|
166166
| Body| Can be left as default.|
167167
168168
![Screenshot of the upload and index action.](./media/logic-apps-connector-arm-accounts/upload-and-index.png)
169169

170+
Select **Save**.
171+
170172
The completion of the uploading and indexing from the first flow will send an HTTP request with the correct callback URL to trigger the second flow. Then, it will retrieve the insights generated by Azure Video Indexer. In this example, it will store the output of your indexing job in your Azure Storage. However, it's up to you what you do with the output.
171173

172174
## Create a second flow - JSON extraction

0 commit comments

Comments
 (0)