You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/ai-services/openai/how-to/use-your-data-securely.md
-39Lines changed: 0 additions & 39 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -334,47 +334,8 @@ Make sure your sign-in credential has `Cognitive Services OpenAI Contributor` ro
334
334
335
335
### Ingestion API
336
336
337
-
338
337
See the [ingestion API reference article](/rest/api/azureopenai/ingestion-jobs?context=/azure/ai-services/openai/context/context) for details on the request and response objects used by the ingestion API.
339
338
340
-
More notes:
341
-
342
-
*`JOB_NAME` in the API path will be used as the index name in Azure AI Search.
343
-
* Use the `Authorization` header rather than api-key.
344
-
* Explicitly set `storageEndpoint` header.
345
-
* Use `ResourceId=` format for `storageConnectionString` header, so Azure OpenAI and Azure AI Search use managed identity to authenticate the storage account, which is required to bypass network restrictions.
346
-
***Do not** set the `searchServiceAdminKey` header. The system-assigned identity of the Azure OpenAI resource is used to authenticate Azure AI Search.
347
-
***Do not** set `embeddingEndpoint` or `embeddingKey`. Instead, use the `embeddingDeploymentName` header to enable text vectorization.
0 commit comments