An Apache Spark-based analytics platform optimized for Azure.
Hello @Alejandro Morillo ,
Welcome to the Microsoft Q&A and thank you for posting your questions here.
I understand that your Azure Databricks Claude Fable 5 endpoint shows Ready but returns Endpoint not found.
Your scenario cannot be solved by recreating or linking the model. The best practice is to check model availability, cross-Geo processing, UC permissions, and the actual serving endpoint route. databricks-claude-fable-5 is a Databricks Foundation Model APIs pay-per-token endpoint, so it should be consumed through the preconfigured model serving route, not by creating or linking a custom/provisioned endpoint. - https://learn.microsoft.com/en-us/azure/databricks/machine-learning/foundation-model-apis/supported-models
What you need to do is to:
- Confirm the workspace is in a supported region such as
eastus2, wheredatabricks-claude-fable-5is listed under pay-per-token Foundation Model APIs. - https://learn.microsoft.com/en-us/azure/databricks/machine-learning/model-serving/foundation-model-overview - Enable cross-Geo processing if the workspace is enforcing in-Geo processing, because Claude Fable 5 availability in
eastus2is marked with the cross-Geo indicator. - https://learn.microsoft.com/en-us/azure/databricks/resources/databricks-geos - Verify that the calling user, group, or service principal has
EXECUTEpermission onsystem.ai.databricks-claude-fable-5or on thesystem.aischema. - https://learn.microsoft.com/en-us/azure/databricks/machine-learning/foundation-model-apis/model-uc-permissions - Invoke the pay-per-token endpoint directly using the Model Serving invocation API or Anthropic Messages API. [learn.microsoft.com], [docs.databricks.com]
- If the endpoint still returns “not found” after those validations, escalate to Azure Databricks support because the remaining cause is backend endpoint registration or entitlement synchronization, not a customer-side deployment issue. - https://learn.microsoft.com/en-us/azure/databricks/machine-learning/model-serving/model-serving-limits, https://docs.databricks.com/api/azure/workspace/servingendpoints/
After cross-Geo processing, Unity Catalog permissions, and the correct pay-per-token invocation route are validated, the endpoint should work. If it does not, then you cannot reliably fix it from the workspace UI or API. Azure Databricks support must verify and synchronize the Foundation Model APIs entitlement and serving route for databricks-claude-fable-5.
I hope this is helpful. Please! Do not hesitate to let me know if you have any other questions, steps or clarifications.
Please do not close the thread by upvoting and accepting the answer if any part of it is helpful.