Azure AI Search returning "Could not complete vectorization action. The vectorization endpoint returned status code '400' (BadRequest)."

Hi, it seems this issue is intermittent only for the US region, I created a new one in the Central India region, and it works fine now

The 400 “Could not complete vectorization action” error is returned by the embedding endpoint that Azure AI Search is calling through the vectorizer. Troubleshooting needs to focus on the vectorizer configuration and the embedding model, not the replicas or indexer schedule.

Use these steps:

1. Check common vectorizer errors
   • In the index definition, confirm that the vectorizer referenced in vectorSearch.profiles exactly matches a vectorizer entry in vectorizers.
   • Verify that the vector field’s dimensions property matches the output dimension of the text-embedding-3-large deployment. A dimension mismatch will cause a 400 from the embedding endpoint.
   • Ensure the fields parameter in the vector query targets a searchable vector field; otherwise queries can return empty results even if vectorization succeeded.
2. Validate authentication and roles
   • If using API keys, confirm the key is valid for the Azure OpenAI / Foundry resource.
   • If using managed identity, the search service’s identity must have the Cognitive Services OpenAI User role on the Azure OpenAI resource so the vectorizer can call the model.
   • A 401/403 from the model will surface as a vectorizer error; correct roles or keys and retry.
3. Check for quota and rate‑limit issues
   • Intermittent failures can be caused by Azure OpenAI quota or rate limits. Review the Azure OpenAI quotas and limits for embedding models and ensure the deployment has sufficient tokens‑per‑minute (TPM) for both indexing and query workloads.
   • If the same embedding deployment is used for both indexing and queries, consider creating separate deployments (one for indexing, one for queries) so each has its own TPM allocation.
4. Review diagnostic logs
   • Enable diagnostic logging on the search service and run a query that reproduces the error.
   • Use the provided Kusto query to confirm vector queries and inspect AdditionalInfo for details about the vectorization call:

          OperationEvent
          | where TIMESTAMP > ago(30m)
          | where Name == "Query.Search" and AdditionalInfo["QueryMetadata"]["Vectors"] has "TextLength"
     

   • Use the correlation data to cross‑check with Azure OpenAI metrics (requests, errors, throttling) on the model deployment.
5. Apply best practices to stabilize vectorization
   • Prefer managed identity over API keys in production once the identity and roles are correctly configured.
   • Deploy the embedding model in the same region as the search service to reduce latency and lower the chance of transient failures.
   • Monitor TPM usage and, if necessary, request higher limits or reduce batch sizes.

If, after aligning dimensions, fixing any auth issues, and confirming quota is not exceeded, the 400 errors persist, capture the failing request’s timestamp and correlation IDs from logs and open a support case so the backend vectorization and model calls can be inspected.

References:

• Configure a vectorizer in a search index
• Vector search in Azure AI Search
• Integrated vector embedding in Azure AI Search
• Set up integrated vectorization in Azure AI Search using REST