Skip to content

Commit ef578ed

Browse files
PatrickFarleyPatrickFarley
committed
formatting
1 parent 37eb9e4 commit ef578ed

File tree

1 file changed

+78
-71
lines changed

1 file changed

+78
-71
lines changed

‎articles/ai-services/openai/how-to/gpt-with-vision.md

Lines changed: 78 additions & 71 deletions
Original file line numberDiff line numberDiff line change
@@ -450,38 +450,45 @@ Follow these steps to set up a video retrieval system and integrate it with your
450450
> [!CAUTION]
451451
> Azure AI enhancements for GPT-4 Turbo with Vision will be billed separately from the core functionalities. Each specific Azure AI enhancement for GPT-4 Turbo with Vision has its own distinct charges. For details, see the [special pricing information](../concepts/gpt-with-vision.md#special-pricing-information).
452452
453-
>[!IMPORTANT]
454-
>Vision enhancement for Video requires access to an Azure Blob storage container containing the video files to analyze. Access to the Videos can be provided either by a SAS Url, or by configuring a Managed Identity on the Azure AIServices resource and granting read access to the blob storage.
455-
456-
### Configure Managed Identity on Azure AIService resource and grant access to Azure Blob storage
457-
#### using System Assigned Identities
458-
Enable System Assigned Identities on your Azure AIServices resource following these steps:
459-
1. From your AIServices resource in Azure Portal select Resource Management ==> Identity and toggle the status to ON
460-
2. Assign Storage Blob Data Read access to the AIServices resource: From the Identity page, select 'Azure role assignments', and then 'Add role assignment' with the following settings:
461-
- scope: storage
462-
- subscription: your subscription
463-
- Resource: the Azure Blob Storage resource
464-
- Role: Storage Blob Data Reader
465-
3. Save your settings.
466-
467-
#### using User Assigned Identities
468-
To use a User Assigned Identity follow these steps:
469-
1. Create a new Managed Identity resource in Azure Portal
470-
2. Navigate to the new resource, then to 'Azure Role Assignments'
471-
3. Add a 'New Role Assignment' with the following settings:
472-
- scope: storage
473-
- subscription: your subscription
474-
- Resource: the Azure Blob Storage resource
475-
- Role: Storage Blob Data Reader
476-
477-
4. Save your new configuration
478-
5. Navigate to your AIServices resurcce "Identity" page,
479-
6. Select the User Assigned Tab, then click "+Add" to select the newly created Managed Identity.
480-
7. Save your configuration.
481-
482453
> [!TIP]
483454
> If you prefer, you can carry out the below steps using a Jupyter notebook instead: [Video chat completions notebook](https://github.com/Azure-Samples/azureai-samples/blob/main/scenarios/GPT-4V/video/video_chatcompletions_example_restapi.ipynb).
484455
456+
### Upload videos to Azure Blob Storage
457+
458+
You need to upload your videos to an Azure Blob Storage container. [Create a new storage account](https://ms.portal.azure.com/#create/Microsoft.StorageAccount) if you don't have one already.
459+
460+
Once your videos are uploaded, you can get their SAS URLs, which you use to access them in later steps.
461+
462+
Depending on your authentication method, you may need to do some extra steps to grant access to the Azure Blob Storage container. If you're using an Azure AI Services resource instead of an Azure OpenAI resource, you need to use Managed Identities to grant it **read** access to Azure Blob Storage:
463+
464+
#### [using System assigned identities](#tab/system-assigned)
465+
466+
Enable System assigned identities on your Azure AI Services resource by following these steps:
467+
1. From your AI Services resource in Azure portal select **Resource Management** -> **Identity** and toggle the status to **ON**.
468+
1. Assign **Storage Blob Data Read** access to the AI Services resource: From the **Identity** page, select **Azure role assignments**, and then **Add role assignment** with the following settings:
469+
- scope: storage
470+
- subscription: {your subscription}
471+
- Resource: {select the Azure Blob Storage resource}
472+
- Role: Storage Blob Data Reader
473+
1. Save your settings.
474+
475+
#### [using User assigned identities](#tab/user-assigned)
476+
477+
To use a User assigned identity on your Azure AI Services resource, follow these steps:
478+
1. Create a new Managed Identity resource in the Azure portal.
479+
1. Navigate to the new resource, then to **Azure Role Assignments**.
480+
1. Add a **New Role Assignment** with the following settings:
481+
- scope: storage
482+
- subscription: {your subscription}
483+
- Resource: {select the Azure Blob Storage resource}
484+
- Role: Storage Blob Data Reader
485+
1. Save your new configuration.
486+
1. Navigate to your AI Services resource's **Identity** page.
487+
1. Select the **User Assigned** Tab, then click **+Add** to select the newly created Managed Identity.
488+
1. Save your configuration.
489+
490+
---
491+
485492
### Create a video retrieval index
486493

487494
1. Get an Azure AI Vision resource in the same region as the Azure OpenAI resource you're using.
@@ -664,48 +671,48 @@ print(response)
664671
665672
> [!IMPORTANT]
666673
> The `"dataSources"` object's content varies depending on which Azure resource type and authentication method you're using. See the following reference:
667-
668-
#### [Azure OpenAI resource](#tab/resource)
669-
670-
```json
671-
"dataSources": [
672-
{
673-
"type": "AzureComputerVisionVideoIndex",
674-
"parameters": {
675-
"endpoint": "<your_computer_vision_endpoint>",
676-
"computerVisionApiKey": "<your_computer_vision_key>",
677-
"indexName": "<name_of_your_index>",
678-
"videoUrls": ["<your_video_SAS_URL>"]
679-
}
680-
}],
681-
```
682-
683-
#### [Azure AIServices resource + SAS authentication](#tab/resource-sas)
684-
685-
```json
686-
"dataSources": [
687-
{
688-
"type": "AzureComputerVisionVideoIndex",
689-
"parameters": {
690-
"indexName": "<name_of_your_index>",
691-
"videoUrls": ["<your_video_SAS_URL>"]
692-
}
693-
}],
694-
```
695-
696-
#### [Azure AIServices resource + Managed Identities](#tab/resource-mi)
697-
698-
```json
699-
"dataSources": [
700-
{
701-
"type": "AzureComputerVisionVideoIndex",
702-
"parameters": {
703-
"indexName": "<name_of_your_index>",
704-
"documentAuthenticationKind": "managedidentity",
705-
}
706-
}],
707-
```
708-
---
674+
>
675+
> #### [Azure OpenAI resource](#tab/resource)
676+
>
677+
> ```json
678+
> "dataSources": [
679+
> {
680+
> "type": "AzureComputerVisionVideoIndex",
681+
> "parameters": {
682+
> "endpoint": "<your_computer_vision_endpoint>",
683+
> "computerVisionApiKey": "<your_computer_vision_key>",
684+
> "indexName": "<name_of_your_index>",
685+
> "videoUrls": ["<your_video_SAS_URL>"]
686+
> }
687+
> }],
688+
> ```
689+
>
690+
> #### [Azure AIServices resource + SAS authentication](#tab/resource-sas)
691+
>
692+
> ```json
693+
> "dataSources": [
694+
> {
695+
> "type": "AzureComputerVisionVideoIndex",
696+
> "parameters": {
697+
> "indexName": "<name_of_your_index>",
698+
> "videoUrls": ["<your_video_SAS_URL>"]
699+
> }
700+
> }],
701+
> ```
702+
>
703+
> #### [Azure AIServices resource + Managed Identities](#tab/resource-mi)
704+
>
705+
> ```json
706+
> "dataSources": [
707+
> {
708+
> "type": "AzureComputerVisionVideoIndex",
709+
> "parameters": {
710+
> "indexName": "<name_of_your_index>",
711+
> "documentAuthenticationKind": "managedidentity",
712+
> }
713+
> }],
714+
> ```
715+
> ---
709716
710717
### Output
711718

0 commit comments

Comments
 (0)