Cannot create vector index in Microsoft Foundry – On Your Data Ingestion API retired

Question

I am unable to update an existing vector index in Microsoft Foundry.

I am using the built-in functionality in Microsoft Foundry to update an existing data source and its vector index. This workflow previously worked, but now fails with the following error:

404 NotFound

"The Azure OpenAI - On Your Data Ingestion APIs have been retired. This endpoint is no longer available. For migration guidance, see aka.ms/oyd-migration"

The provided migration URL redirects to Bing instead of providing migration instructions.

This error occurs directly within Microsoft's own Foundry interface, not through custom code.

I have been using this functionality for an existing solution and was not aware of any retirement announcement or required migration.

Could you please clarify:

Is this a known issue with the Microsoft Foundry interface?

How can I continue updating my existing vector index?

Is there a supported replacement workflow that preserves my existing configuration?

Was this retirement communicated to existing users, and if so, where?

I need to keep my existing solution operational and update its data without rebuilding everything.

Thank you for your assistance.

Answer 1

Hi @Nienke

This is not a transient vector-index failure. Microsoft retired Azure OpenAI On Your Data on October 14, 2026, including its ingestion APIs and the former Foundry portal workflow. A request to that endpoint now returning 404 NotFound is therefore expected.

The incorrect aka.ms/oyd-migration redirect appears to be a documentation-link issue. You can report it through Microsoft Learn feedback.

You don’t necessarily need to rebuild the existing vector index. A compatible Azure AI Search index created by file upload, Blob Storage, or web ingestion can be reused. However, migration isn’t automatic: field mappings, connectors, access-control behavior, embeddings, citations, and application calls must be reviewed or reconfigured.

For an existing Azure AI Search-backed solution:

1. Check the Azure AI Search resource for the existing index, data source, indexer, and skillset.
2. If a scheduled indexer exists, update the underlying Blob data and run or retain that indexer to refresh the current index.
3. If no indexer exists, create and manage an Azure AI Search ingestion pipeline separately. The former On Your Data ingestion service can no longer update it.
4. Connect the existing index to either:

• A Foundry IQ knowledge base for managed retrieval and grounded answers; or
• The Azure AI Search tool in Foundry Agent Service if the solution requires an agent, tools, or workflow orchestration.

The Agent Service Azure AI Search tool can connect to an existing vector index.

For production workloads, note that Microsoft’s migration sample uses preview capabilities for automatic retrieval and answer synthesis. Microsoft recommends either the generally available Foundry IQ retrieval API with application-managed answer generation or a classic RAG implementation when preview features aren’t acceptable.

Regarding notification, the retirement is now documented on the On Your Data concept, configuration, best-practices, and API-reference pages.

References:

• Azure OpenAI On Your Data retirement and migration planning
• Connect Azure AI Search to Foundry Agent Service
• Azure OpenAI On Your Data API reference

---

Help make this community better for everyone: If this answer helped or resolved your issue, please accept it or upvote it. If not, share more details in a comment so we can continue the discussion and find the right solution. Thank you.