Share via

HNSW index is not supported for M30 cluster tier

Anonymous
2025-06-13T10:40:40.14+00:00

Hi everyone,

We have a Cosmos DB MongoDB (vcore) M30 instance running for over a year. We were using the HNSW indexes for vector searches. However, recently vector search queries started failing without any change on our side, causing our product feature to fail. Additionally, when I try to create a new HNSW index, I get the error "hnsw index is not supported for this cluster tier". According to Microsofts Azures own documentation, HNSW indexes should be available for M30 clusters and higher (https://learn.microsoft.com/en-us/azure/cosmos-db/mongodb/vcore/vector-search?tabs=hnsw).

Does anybody have a similar issue or know what may have caused this behavior to occur?

Thanks in advance,

Pascal

Azure Cosmos DB
Azure Cosmos DB

An Azure NoSQL database service for app development.


Answer accepted by question author

  1. Mahesh Kurva 10,520 Reputation points Microsoft External Staff Moderator
    2025-06-13T11:03:47.5433333+00:00

    Hi Pascal Pieters,

    Greetings!!

    HNSW indexes are not supported on M30 cluster tiers.

    According to the updated service limits documentation, HNSW and DiskANN indexes are now only supported on M40 and higher cluster tiers. This appears to be a recent change.

    User's image

    If vector search is critical to your product, consider upgrading your cluster tier to M40 or above to restore HNSW support.

    Hope this helps. Do let us know if you any further queries.

    If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.