An Azure search service with built-in artificial intelligence capabilities that enrich information to help identify and explore relevant content at scale.
Thanks for sharing the details. When a vector index is created, Azure AI Search must allocate dedicated compute capacity to support vector storage and similarity search. On the Free tier, Azure AI Search runs on shared, multitenant infrastructure with very limited compute and storage, and scale‑up is not supported.
Because of these limitations, vector index provisioning can remain stuck at “Step 1 of 3: Allocating compute resource” and may never complete on a Free service. This behavior is expected on the Free tier and is not a configuration issue on your side.
Recommended solution
To successfully create a vector index, please use a paid Azure AI Search tier (Basic or Standard S1 or higher), which provides dedicated compute resources required for vector workloads.
Steps:
- Create a new Azure AI Search service using Basic or Standard (S1+) tier
- Recreate the vector index in the new service.
- Retry the Microsoft Learn RAG module using this paid Search service.
Once dedicated compute is available, the vector index creation should complete successfully.
Reference :
https://learn.microsoft.com/en-us/azure/search/search-limits-quotas-capacity
https://learn.microsoft.com/en-us/azure/search/search-sku-tier
If the answer is helpful, Please do click "Accept the answer” and Yes, this can be beneficial to other community members.
If you have any other questions, let me know in the "comments" and I would be happy to help you