Hi @jnelson,

Being on the Enterprise tier does not by itself guarantee this will work if the workspace still has an AI Search endpoint quota of 1 or does not support the Direct Access index type for this path.

Those two errors usually point to AI Search/Vector Search limits in that workspace, not just the workspace tier itself.

For the Knowledge Assistant, there are two things to check:

• Vector index type DIRECT_ACCESS is not supported for this workspace, which typically means the workspace does not support using a Direct Access vector index for this flow. If you're selecting an existing AI Search index, make sure it's configured as a supported index rather than Direct Access. The public docs for Knowledge Assistant are here: Use Knowledge Assistant to create a high-quality chatbot from your documents, and the public community guidance specifically states that Knowledge Assistant does not support self-managed or Direct Access indexes for this scenario.
• Maximum number of AI Search endpoints per workspace exceeded quota of 1 means the workspace has already hit its AI Search endpoint quota. In another community thread, it is mentioned that Agent Bricks currently creates a new vector search endpoint as part of this flow rather than reusing an existing one, which is why this quota can block creation even if you already have AI Search set up.

A few practical things to try:

• If you're using an existing AI Search index, recreate or switch it to a supported setup and avoid Direct Access for this Knowledge Assistant workflow.
• Check whether there is already an AI Search endpoint in the workspace consuming the only allowed slot.
• Verify the rest of the documented prerequisites as well... serverless compute, Unity Catalog, Model Serving, a nonzero serverless budget policy, a supported region, and supported knowledge source types / embedding models.

Hope this helps.

If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.