Azure OpenAI - Vector Stores - Attempts to upload files to a Vector Store in Region Germany West Central randomly throws 'Indexing Failed' / 'An internal error occurred'

Question

Azure OpenAI - Vector Stores - Attempts to upload files to a Vector Store in Region Germany West Central randomly throws 'Indexing Failed' / 'An internal error occurred'

David Captur 175

Attempts to upload any file to any vector store in an OpenAI Resource in Germany West Central Region often result in an internal server error and leaving status "Indexing Failed".

This problem is occurring for all files, of different formats, in all vector stores and both when trying via screens OR via the API. Any attempt to upload results in this:

User's image

This is not a temporary / new issue, it has been going on for several months (since around May / June 2026). The same identical approach on a different region for the same files, same setup works without problems. It seems to be something region specific as other non-prod resources on the same region have the same problem.

A staff member from Azure support has stated this is due to a design flaw on their end. The flaw basically allows other customers in the same region to vectorise more than they should be allowed to at a given time. This results in a general performance degradation in the region in general for anyone uploading files to a vector store. Azure Support has also admitted that this issue is affecting other customers on the same region, and there is currently not ETA for a solution or simple work-around.

Azure Support seem to be utterly incapable or unwilling to address the issue.

Sai Kiran Mudavath 180 Reputation points Microsoft External Staff Moderator

2026-10-02T06:10:01.3533333+00:00

Hi @David Captur

Thank you for providing the detailed reproduction steps and additional information.

I reviewed the current Microsoft Foundry documentation and the behavior you described.

File Search and vector stores are supported in Germany West Central, and files added to a vector store are processed asynchronously through parsing, chunking, embedding, and indexing. (Microsoft Learn)

Based on your reproduction, the issue is occurring across multiple supported file formats and vector stores, through both the Foundry portal and API, while the same workflow succeeds in another region. This makes a file-format or client-side configuration issue less likely and is consistent with a service-side issue affecting the vector-store indexing path in Germany West Central.

There is also a July 2026 Microsoft Q&A report describing the same Indexing failed / An internal error occurred behavior for vector stores in Germany West Central. In that case, the reported pattern was considered indicative of a region-specific backend indexing issue and was escalated for further investigation. (Microsoft Q&A)

The public documentation does not confirm the specific underlying cause or provide an ETA for a fix, so I would not want to speculate on those details.

We have reached out to you via private message for further assistance and to collect the details required to investigate the affected resource and failed indexing operations.

Thank you.
Sai Kiran Mudavath 180 Reputation points Microsoft External Staff Moderator

2026-10-07T08:47:30.5933333+00:00

Hi @David Captur

Did you get any chance to review the above response. Do let me know if you have any further queries.

Thank you!
Sai Kiran Mudavath 180 Reputation points Microsoft External Staff Moderator

2026-10-08T01:43:08.28+00:00

Hi @David Captur

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Thank You!

Your answer

Sai Kiran Mudavath 180 Reputation points Microsoft External Staff Moderator

2026-10-02T06:10:01.3533333+00:00

Hi @David Captur

Thank you for providing the detailed reproduction steps and additional information.

I reviewed the current Microsoft Foundry documentation and the behavior you described.

File Search and vector stores are supported in Germany West Central, and files added to a vector store are processed asynchronously through parsing, chunking, embedding, and indexing. (Microsoft Learn)

Based on your reproduction, the issue is occurring across multiple supported file formats and vector stores, through both the Foundry portal and API, while the same workflow succeeds in another region. This makes a file-format or client-side configuration issue less likely and is consistent with a service-side issue affecting the vector-store indexing path in Germany West Central.

There is also a July 2026 Microsoft Q&A report describing the same Indexing failed / An internal error occurred behavior for vector stores in Germany West Central. In that case, the reported pattern was considered indicative of a region-specific backend indexing issue and was escalated for further investigation. (Microsoft Q&A)

The public documentation does not confirm the specific underlying cause or provide an ETA for a fix, so I would not want to speculate on those details.

We have reached out to you via private message for further assistance and to collect the details required to investigate the affected resource and failed indexing operations.

Thank you.
Sai Kiran Mudavath 180 Reputation points Microsoft External Staff Moderator

2026-10-07T08:47:30.5933333+00:00

Hi @David Captur

Did you get any chance to review the above response. Do let me know if you have any further queries.

Thank you!
Sai Kiran Mudavath 180 Reputation points Microsoft External Staff Moderator

2026-10-08T01:43:08.28+00:00

Hi @David Captur

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Thank You!