Matis Kofoed Petersen, lakshmi, Following-up on this, we have transitioned our back-end ingestion service to utilize integrated vectorization. With this new approach, chunking and embedding are handled by Azure AI Search prebuilt skills, eliminating the need for custom skills. Consequently, you will now see a single index and a single indexer.
Our content team is working on updating the documentation integratedvectorization to reflect the switch to integrated vectorization.
Our product engineering team is working on a UI bug that causes the indexer schedule to be set as one-off, regardless of the selection made in the corresponding drop-down menu. In a one-off ingestion, the indexer is deleted after the index is created.
Currently, our team is working on a fix (no ETA to share) as soon as I have more updates I’ll share it with you.
As a workaround, I would recommend that you use our ingestion REST Apis directly as per documentation.
If the answer helped (pointed, you in the right direction) > please click Accept Answer to benefit the community find answers quickly to similar question_._